|
|
|
|
|
Here are some screenshots of it happening on the homeworld. Notice the shots at the top. 20180828210355_1.jpg (183,174 bytes) 20180828210357_1.jpg (183,170 bytes) 20180828210415_1.jpg (187,588 bytes) 20180828210354_1.jpg (183,459 bytes) |
|
|
Can confirm, had this myself with MLRS Corvettes. Constantly shooting at something also at the top part of the screen. It terminated just before the asteroid belt, almost exactly at a wormhole. Save is unusable from older version. |
|
|
Thank you so much for this!! * As sometimes happens with multithreading issues, we're not really sure WHY this was happening, but we know that it was and we're pretty positive we fixed it. ** Basically, ships could wind up being told to autotarget ships that were on the wrong planet, and then would shoot at them. This led to many odd behaviors, as well as a lot of wasted CPU. ** This may have mostly been from ships moving between planets, it's hard to say; in those instances, it now recognizes the disconnect and simply stops targeting the ship that's now on another planet. This is a valid case that gets done away with. ** The other issues may have been some cross-thread mixing of array data somehow, and we've simply rearranged the code some to try to prevent that sort of thing. That seems to have worked, although we weren't super successful actually catching it in the act anyway. At least it's easier to read, now, either way. ** We're also no longer persisting ship autotargeting data to disk, although we are still persisting it across network syncs (of course). This should make savegames a slight bit smaller in some cases. ** Anyhow, this may have been one performance issue in certain long-running savegames, we're not sure. It's an improvement, either way. |
- Anonymous
