Topic: Bugs
GunChleoc |
Posted at: 2017-08-16, 11:25
We need to retest this one we get https://code.launchpad.net/~widelands-dev/widelands/savegame-menu/+merge/322924 in trunk.
Thanks, I'll mark the bug as resolved Busy indexing nil values Top Quote |
Nordfriese |
Posted at: 2017-08-16, 15:46
Bad news: The bug isn´t solved after all, it´s just that it is triggered less easily now, but it´s still there Top Quote |
kaputtnik |
Posted at: 2017-08-16, 16:17
I think you meant this bug?
Could you explain a bit? Does this happen when placing resources? Fight simulator for Widelands: |
Nordfriese |
Posted at: 2017-08-16, 16:49
Yes, I mean the resource bug. What happens is this. I was designing a map with the editor; first the terrain, then I placed resources, animals, immovables and port spaces (in this order). Then I switched on the player position tool and looked for the perfect starting places. In doing so I toggled buildhelp and resource visibility several times. After I placed the players, I closed the player tool and switched on the info tool – and the resources are suddenly no longer visible, even when the resource view button is toggled on. The info tool shows that the resources are still there, they only aren´t visible. Changing the tool or toggling resource view can´t make them visible again, only restarting the editor does. This used to be triggered sometimes (but not always) by switching from the resource tool to the immovable tool. Now, this happens sometimes (still not always) by activating the player tool. I never saw a system under which circumstances exactly this bug is triggered. Top Quote |
GunChleoc |
Posted at: 2017-08-16, 21:07
Thanks - I have added this information to the bug report. Busy indexing nil values Top Quote |
GunChleoc |
Posted at: 2017-08-29, 07:38
I have tried this about 20 times now without triggering a crash. Are you able to run a debug build with gdb from a terminal/command line? Busy indexing nil values Top Quote |
Nordfriese |
Posted at: 2017-08-29, 13:19
I tried about 50 times now and I could not reproduce this with current trunk. Instead of crashing, the game is saved several times (one after the other), once for every Enter press until the save dialog closes, which it does when the last save is done. The savegame is not damaged in any way. If there was a change recently that affected the save window or file output, it seems to have fixed the crash. If not, the crash I reported was probably caused by button presses that happen in an extremely short interval, shorter than can be actively reproduced. Top Quote |
GunChleoc |
Posted at: 2017-08-30, 08:50
Thanks, I'll mark this one as fixed then. Busy indexing nil values Top Quote |
WorldSavior Topic Opener |
Posted at: 2017-12-14, 22:23
I've found a bug. Maybe someone wants to copy the (short) text into a bug report in Launchpad (or link it)? Collectors single player replays breakIf you play collectors in single player mode (b19), it happens often that the replay will be damaged: It that case, it always stops after a certain time and cannot run again. Maybe this bug is similar to the bug that collectors matches crash in multiplayer? It is also possible that this bug exists if you play alone in the multiplayer mode, I don't know. Wanted to save the world, then I got widetracked Top Quote |
GunChleoc |
Posted at: 2017-12-15, 19:03
I had tons of crashed with Hasi with Collectors during the tournament, but the recent fixes seem to have solved those. So I don't believe that testing old replays will be helpful any more. Thanks for reporting though Busy indexing nil values Top Quote |