|
perperson -> Game Performance Issues on High Resolution Displays (12/2/2017 6:10:25 PM)
|
Hello -
I've newly purchased CMANO, and I'm really enjoying it! But I'm being plagued by a near show-stopper performance issue that I'm hoping someone may be able to help with.
I'm playing Command on a Windows 10 system with an i7-7700K, GTX 1070, and a 2560x1440 monitor. I have read the sticky on running command on 4K/UHD monitor. I am using the default performance options.
I am having performance issues when running almost any scenario in the game. For the purposes of this thread I'm talking about the performance in the air tutorial. I didn't include a game file since this occurs for basically any scenario, especially larger ones.
In real time mode the game seems to run in close to real time most of the time, but there are frequent (maybe 5 or so times every 15 seconds) pauses between updates, of maybe 100 to 1000ms. This gives a prominent stuttering effect. If I change the game to run at rates higher than real time, the game doesn't seem to be able to keep up. Most of the time the clock advances slower then 5x, then I will get periods where the game seems to "catch up", and the clock might advance 5 minutes in 1 second. This makes the game essentially unplayable for larger or longer scenarios.
If I make the game window smaller performance improves dramatically, so I was thinking it might be related to the screen resolution in some way. I also noted that CPU usage seems to be 100% on one core, which is probably the cause of the stuttering.
I didn't notice any UI scaling issues, but I did apply the fix as described in the high DPI display sticky - modifying the registry, deleting the ini file, and changing the compatibility settings on both the auto launcher and the game. If it made any improvement it was a small one.
I also tried lowering the resolution to 1920x1080, which performs much better. Even at that resolution though I still get stuttering, but less often and for a much shorter duration. Maybe that is normal for the game?
Is this a known issue or limitation? Is there any fix for this behavior?
|
|
|
|
