Topic: Bugs

I´m not sure if this is known already: I have noticed a bug in the editor.

The map options window is almost unuseable. If I enter a few lines of text, the input becomes really slow (about 30 seconds per character), and eventually widelands doesn´t respond at all and I have to force-close it. The system monitor shows that widelands suddenly consumes all available RAM (2 GB) and the entire swap memory (before opening the map options it used ~20 MiB and no swap). The space isn´t freed when I close the map options dialogue, only when I exit widelands. I found this bug in current trunk (both debug and release) but not in build19.

Top

Quote

Some more bugs in current trunk (daily PPA for Ubuntu 17.04, latest update a few hours ago; I´m not sure whether these bugs are known already):

• Sometimes, when a buildings finishes constructions, its window appears although I did not click the building and the window was not open before. Sometimes, the building is not even visible on the screen. There seems to be no pattern whether a window opens or not.

• The game quite frequently crashes with a non-reproducable Speicherzugriffsfehler. The normal output does not provide any further information, and I did not yet get this while playing with the --verbose option.

• If I zoom out and then back in, the graphics of buildings, immovables etc. sometimes start looking a bit verwaschen (sorry, I don´t know the English word for this). This is unhealthy for the eyes and I cannot continue playing much longer.

• When saving over an old file, the confirmation dialog pops up. I usually press Ctrl-S, then twice Enter – Open Save Dialog, Save, Confirm. If I press Enter too fast the second time, Widelands crashes and the resulting savegame is broken ("Incompatible" according to the Load Game screen).

• In the editor, the Save Map window is not always closed after saving the map. The Enter button does not work for the OK button.

• In the editor, the placed resources sometimes are no longer visible and do not reappear without restarting the editor.

Top

Quote

The graphics problem: When zooming out (with the mousewheel), I only zoom out so far that the building names are still visible (until they disappear and then a bit in again). The automatic zoom jumping for animated movement on the map can also cause this. When zooming in, I use the Ctrl-0 hotkey to reset zoom.

I do not always get the bad graphics after resetting zoom, and never in the editor. The graphics start looking like, when you open a digital image and magnify it so you don´t see the whole picture but the single points. I think blurred or fuzzy is the word I´m looking for. (I just can´t express this in English, sorry! In German: Die Bilder sehen sehr verschwommen aus, man erkennt die einzelnen Pixel, und das verursacht Migräne.)

About the crash: Even with --verbose, there is no further information. I´ll try to run Widelands with gdb to get a backtrace for the crash.

Top

Quote

Nordfriese: Can you provide a screenshot of a fuzzy zoom? Shortcut: Strg + F11 grabs the entire screen as a picture in a 'screenshot' subdirectory under .widelands/ You can upload it to a filehoster like http://imgbb.com/ or similar.

Top

Quote

I´m not sure what you meant about Ctrl-0 in your previous post. The graphics are fuzzy even after resetting zoom to normal with Ctrl-0.

These screenshot show what it normally looks like and what is looks like after some zooming and then resetting to normal with Ctrl-0.

(Yes, not quite the same place on the map) Just compare the trees, workers or buildhelp icons. The wheat fields and the Reed Yard are particularly blurred. When Widelands starts looking like that, I get a headache within five minutes and have to stop playing.

Top

Quote