|
|
|
|
|
This section of the F3 menu would be useful for me to see in addition to what you provided there. Happily, it is also slow for me, but only 1 second, not multiple. image.png (73,502 bytes) |
|
|
Oh, also. If you turn on these two settings shown as gold in the settings menu: image-2.png (201,937 bytes) |
|
|
Then this will show up: image-3.png (137,140 bytes) |
|
|
Thanks! * Drastically improved the performance of several parts of the game, but most notably the turn-change when there were a lot of units. ** Essentially, there was one overarching bottleneck for checking if there were new units to collide against, and it was having a terrible impact on performance even when there were no units to check against. This has to do with the way that the ConcurrentDictionary class that is part of C# works. ** What I've done is made some alterations to that collection, and then also made a wrapper class, so that for my purposes in the majority-case situation (there is nothing in there) it is able to take a lot less time. On my machine, this drops something that took about 1200ms down to 50ms. On some other end-user machines, this was taking multiple seconds, and it's expected that their savings in time would be even greater. |
- Anonymous
