Topic: Naval Tournament 2023

The newest version of the tag is up with commit ddfa8b6. We'll try to continue with this one. Installers are available in post #4.

A sizeable number of crashes both in the UI and the game logic was fixed since the last tag version. Naval battles involving many ships should also work fine now, so please do stress-test this as well. Existing savegames with ships that are already in a stalled battle may or may not be playable anymore.

There was one bug mention that could not be investigated due to lack of detail. On two occasions it was mentioned that a segfault (that's a total program crash with no error message and no emergency savegame, as opposed to an Error During The Game which gracefully crashes to the main menu with a useful error message and an emergency save) occurred while the player was building a road. UI segfaults (which only happen for one player, as opposed to game logic bugs which happen for all players and spectators at the same time) like that are down to raceconditions, which means that they are generally not reproducible and completely impossible to investigate without a backtrace. So it might be possible that one or more of those very rare bugs is still floating around.

I would therefore like to ask everyone who can run Widelands in a debugger (and/or compile with ASan enabled) to do so, and if you get a crash, post the full backtrace. You do not need to use a slow debug build, a release build will suffice as even then the trace still contains invaluable information for fixing the bug. But without a backtrace, non-reproducible crashes are literally impossible to troubleshoot.

Top

Quote

Got it: tournament % cat VERSION 1.2~git26360 (ddfa8b6@HEAD)%
lets continue tommorrow

Here are the widelands where people may dwell, walking around care that evrythings well.

Top

Quote

I just identified and patched another very new UI crash: Please do not resize the Widelands main window (this includes toggling fullscreen on/off) while a multiplayer game is running. Doing so will result in a crash (segfault).

This regression was introduced very recently. I would not consider it critical since you can just set the window size before launching the game and then keep it unchanged. Just keep it in mind please, and sorry for the inconvenience.

Top

Quote

tothxa wrote:

The newest version of the tag is up with commit ddfa8b6.

@stormax-e: This version now contains a fix that allows the flatpak build to work properly with the 23.08beta runtime. You can install the test build from here:

flatpak install --user https://dl.flathub.org/build-repo/41503/org.widelands.Widelands.flatpakref

This runtime is the beta version for this year's release, so it's only available from flathub-beta for now, but installing the test build should pull it in if you have the beta repo enabled. Please try the test build or let me know if you can't install it or the beta runtime. I'd like to commit this to flathub-beta with the new runtime, but as you're using it in the tournament, I don't want to break it for you.

Thanks. I installed it - except without user parameter as on this computer i don't use it. Installation went smoothly,

Top

Quote

Hi everybody,
thanks to Hasi50 and stormax-e for finding so much bugs.

Especially keep the following one in mind for this round (will be fixed in next rounds version) :

• Ports can now garrison soldiers (you click the third tab of a port showing a smal soldier icon like in the trainingsites)
• But as these soldiers are currently in a warehouse they count like stored soldiers not as staioned ones
• so to make the barracks work to produce lacking soldiers you need to either increase the target amount of soldiers by the value of all soldiers garrisoned in ports or set the baracks to produce indefinitly

Anybody who might be in doubt how a new feature works, please look at the brief quick start guide that Nordfriese provided in post #4 or just ask the question here in the forum.

Top

Quote