|
|
2022-02-23 04_24_56-AIWar2.png (137,764 bytes) |
|
|
After some extra time it spawned. Can it be related to a slower thread that ran a bit later than usual (even though it's weird after half a minute). |
|
|
Were you on an MP client? |
|
|
No, SP. I think it's a performance issue. The game was pretty slowed down, so something was behind |
|
|
Thanks! * In the event that a wave timer would be negative or zero (aka, it thinks the wave should already have landed, but it has not yet), it now says "SOON" on the notification, and "any second now... but the exact timing may be a surprise" in the tooltip for it. ** Usually waves will launch on time, but there are cases where the game is running the AI threads more slowly because of load, or the "only run every X seconds" logic is there anyway, and so the exact timing is just not actually exact in all cases. ** It doesn't really make any sense to try to make the timing more exact, since this flexibility is one of the things that helps performance, and not knowing down to the second when a wave is going to arrive is mildly interesting anyhow. So now it's simply handled in a way that makes it not look like a bug. |
- Anonymous
