14-09-2019, 02:12 AM -
Hi!
I've been looking forward to TCOS being playable again and I gave it a go yesterday and today.
I noticed immediately there were a lot of hickups in framerate, so I started to look into it today, just running around the forest outside of Hawksmouth.
As has been said in another post on framerate, the game is single-threaded.
So, using Process Lasso I've set affinity for the process to a single core or a couple of cores to see how it behaves.
When doing so I've also set affinity for all other processes to only use the remaining cores.
With my now pretty old i5 3570k overclocked to 4.3 GHz I still don't reach 100% when I've locked the process to one core, it's usually around 90% with some variance, and split between two cores I can see that even though the work is using both cores it is at least seemingly fully or close to fully single-threaded, as the two cores hover between 40% and 60%, rarely ever reaching a combined 100%.
With that said, frametimes and framerate are both fine so long as I stay in one area. But when I run into an area I haven't been in for a little while, the frametimes shoot up from ~17ms to spikes between 50-200ms. CPU usage stays the same throughout, so the issue seems to lie in loading in new resources into memory.
I'm not sure what kind of expertise is currently available from the dev team but in terms of user experience this issue is a major hurdle which I can't overcome, and I can't enjoy the game like this. Was it always like this?
OS: Windows 10 Pro
Processor: i5-3570K @ 3.40GHz (Boost OC to 4.30 GHz)
RAM: 8,00 GB DDR3 @ 1600 MHz
GPU: GTX 970
Game installed on drive: Samsung SSD 860 Evo
I've been looking forward to TCOS being playable again and I gave it a go yesterday and today.
I noticed immediately there were a lot of hickups in framerate, so I started to look into it today, just running around the forest outside of Hawksmouth.
As has been said in another post on framerate, the game is single-threaded.
So, using Process Lasso I've set affinity for the process to a single core or a couple of cores to see how it behaves.
When doing so I've also set affinity for all other processes to only use the remaining cores.
With my now pretty old i5 3570k overclocked to 4.3 GHz I still don't reach 100% when I've locked the process to one core, it's usually around 90% with some variance, and split between two cores I can see that even though the work is using both cores it is at least seemingly fully or close to fully single-threaded, as the two cores hover between 40% and 60%, rarely ever reaching a combined 100%.
With that said, frametimes and framerate are both fine so long as I stay in one area. But when I run into an area I haven't been in for a little while, the frametimes shoot up from ~17ms to spikes between 50-200ms. CPU usage stays the same throughout, so the issue seems to lie in loading in new resources into memory.
I'm not sure what kind of expertise is currently available from the dev team but in terms of user experience this issue is a major hurdle which I can't overcome, and I can't enjoy the game like this. Was it always like this?
OS: Windows 10 Pro
Processor: i5-3570K @ 3.40GHz (Boost OC to 4.30 GHz)
RAM: 8,00 GB DDR3 @ 1600 MHz
GPU: GTX 970
Game installed on drive: Samsung SSD 860 Evo
This post was last modified: 14-09-2019, 02:13 AM by Bjartvangr.