Topic: Game suddenly very slow
kaputtnik |
Posted at: 2020-04-25, 19:03
Your savegame works fine on my old 1core Intel Celeron 900 laptop, running shipping-tweaks-b21. However this was a release build. Just try a release build. Debug builds tends to get slow, especially on big maps. Just my observation.... As long release builds don't get slow, this isn't a real problem i think. Fight simulator for Widelands: |
Nordfriese |
Posted at: 2020-04-25, 19:08
The first one is in AI code (Beifang), the others are all in routing code. So this is not a bug, just the usual issue that ware/worker pathfinding can take pretty long on big maps. As kaputtnik said the only remedy against this is to use release builds where this is not as much of a problem. Top Quote |
PkK Topic Opener |
Posted at: 2020-04-25, 19:34
It then still is a real problem for debugging other issues on large maps. And it appeared surprisingly quickly (the game went from well-playable to unplayable-slow instantly) rather than gradually, so I suspected some real issue here. Top Quote |
niektory |
Posted at: 2020-04-25, 19:38
The RelWithDebInfo (release with debug info) configuration is often a good compromise. Top Quote |
PkK Topic Opener |
Posted at: 2020-04-26, 19:58
Indeed, a build with ./compile -r runs at good speed for me (on the same system, where the debug build got 0.3 fps). Top Quote |
dershrimp |
Posted at: 2020-07-02, 16:42
Hi. I just ran in a similar issue playing Tasmanian Black War with a ~1 month old dev version. The CPU goes quickly to 100% and I got 0.3 fps with 1x game speed making the map unplayable after 2-3 hours game time. I noticed that widelands is running on only one core. Is that supposed to be or is something not working for me? Just checking. System is Intel(R) Core(TM) i5-4310U CPU @ 2.00GHz with 8 GB RAM, but RAM doesn't go to its limit. Top Quote |
Nordfriese |
Posted at: 2020-07-02, 16:53
Multithreading is something we have had on our wishlist for years, but nobody ever implemented it Are you using a release or debug build? Debug builds are just not suited for playing larger games as they're very slow by nature. Top Quote |
dershrimp |
Posted at: 2020-07-02, 17:00
It is a debug build, version 5acb402 (so it is a few days older apparently). I compiled the version with ./compile.sh -a, i.e. in debug build. How do I switch to the release build? Can I just call ./compile.sh -r or do I have to remove the game completely, first? Top Quote |
Nordfriese |
Posted at: 2020-07-02, 17:09
Yes, it's enough to run Top Quote |
dershrimp |
Posted at: 2020-07-02, 17:50
Thanks. I did that, but it seems I cannot load the savegame with the new version. I get the following error message
Top Quote |