patroling slows down gameplay to 50 % #4548
Comments
krichter uploaded file replay of the skirmish game demonstrating the issue |
krichter uploaded file map used for the replay |
krichter uploaded file a replay with a defaut map |
krichter commented Just could reproduce the issue on a default map. There the issue isn't resolved by stopping the patroling which it is on the other map, so this might be two issues, but it also slows down the gameplay dramatically. |
Berserk Cyborg commented I get this issue too (3.2.1 does not have this problem). There is noticeable lag even in small maps. Not sure what causes it though. |
Berserk Cyborg commented Actually, the first save is probably because the the map you linked. Game play is more or less smooth unless you go with advanced bases (which probably creates ~1000 non droid objects with all eight players). At which point Warzone struggles to even move around the screen regardless of a specific AI. The second map acts as suspected. A small slowdown, but that is to suspected with nine AI. |
vexed changed status from |
vexed changed resolution from `` to |
vexed changed blocking which not transferred by tractive |
vexed changed blockedby which not transferred by tractive |
vexed commented Is this still an issue with master? |
resolution_Requesting more information about issue
type_bug
| by krichterI couldn't reproduce this issue on a map which is included in a standard source installation, however this might indicate an issue which can be fixed and prevent future issues.
In the attached gameplay you can see delay of frames which makes the gameplay appear flickering after making a lot of units patrol over long distance. Reasons might be the number units, the distance to patrol, the number builings or else. I couldn't isolate a reason so far. In order to get all suspected parameters to a high value fast, cheat mode with
research all
against 7 AI players has been used. Deactivating the patrol routes causes the gameplay to resume normally immediately.experienced with 3.2.2-6-ge315f08 on Ubuntu 16.10
Issue migrated from trac:4548 at 2022-04-16 12:39:49 -0700
The text was updated successfully, but these errors were encountered: