- performance:
- Enable the GUI and Taskbar Extensions in CSP
- go on track
- the app should be called something with render stats
- it should show you the overall times for cpu and gpu in the upper part and in the lower part show the cpu and gpu times for every part of AC.
Compare practice alone with an AI race with a similar field as this race.
You should see a few of the times in that render stats app changing dramatically.
These are the settings we need to adjust.
Might be a single HUD app that kills your fps or might be reflections, shadows, anything really.
You don't need to look into this on your own though. Just open that render stats, try to unwrap the things that go up the most in frame time between practice alone and AI race and post the Screenshots in here.
I'll try to tell you what to adjust
A little bit extra information about this:
What CPU do you have? AC eats any CPU for breakfast if you have some settings slightly too far up.
To give a feeling for this:
AC uses two big "CPU threads", so you basically only need 3 cores for it.
One for each thread and a third core for Windows, discord etc.
You can't see this in Taskmanager or any other normal monitoring tool though, since Windows will seemingly randomly throw these threads around across all cores.
You're only seeing the average over the tick rate of the monitoring tool though.
In reality, if you'd freeze after just 5 clock cycles or so (4 GHz = 4.000.000.000 clock cycles per second), you would see 2 cores at 100% and the other cores doing everything else at a lower load.
It's more efficient to let one core do a few cycles and then let the next core do the next few cycles. Probably has something to do with internal latency, caching etc.
It's a mix of Windows' "scheduler" and cpu microcode.
There, my knowledge stops.
Anyway:
One of these CPU threads will always be "heavier" than the other, so it all comes down to that one single CPU thread on one single cpu core in a single "moment in time".
If you look into that csp app, you'll see the cpu frame time and that's directly your momentary fps.
One frame is always cached, so your overall frame time is almost identical to the higher frame time of either the cpu or gpu. Not both added together.
So at 10 ms, you have 1 second = 1000 ms. Divided by 10 ms = 100 fps
At 16.67 ms, it's 60 fps.
The issue is that any HUD app, additional car, shadows, track details, everything, adds up to that time.
So 6 ms are quickly gone if you add a few things here and there.
