Can you do the same csp render stats screenshot with 1080p, fps limiter off (or raised to 100 or so) and also vsync disabled?
Would be interesting to see how the frame times change then.
What's clear though: 4k with csp, pure, simhub etc is pretty heavy on the hardware. It's an "old" game but with all the additional stuff is easily more demanding than ACC, which is way newer.
What car and track are you using in the screenshots? Depending on their polygon, LOD and feature counts, the performance can be very different compared to a stock Kunos car on a Kunos track.
I have no idea why it should feel like slow motion though. It might be the input lag from vsync but that should've been there before.
Do the test for the render stats without vsync and without the limiter and while doing that, check if the "slow motion" feel is gone too.
It will probably stutter and show tearing, that's another topic though.
My question with the Intel was about the ambient occlusion setting in extra FX (ASSAO by Intel), sorry.
But that's disabled.
I didn't see this "AABB prep" in my render stats app, but I'll have a look when I'll get home!
Your xeon is very good for games that can use a lot of cores.
Sadly simracing only needs 4 cores but the highest single core performance you can get
Have a look here:
https://www.cpubenchmark.net/compar...-7600K-vs-Intel-i5-9600K-vs-AMD-Ryzen-5-5600X
I've added a few "budget simracing CPUs" for comparison. The xeon's multicore performance is pretty good, but the single core rating isn't great.
But we got the cpu frame time to be shorter than the gpu frame time, which is good!
The gpu frame time is still very high though...
Next:
I never used the dxgi extension since my monitor isn't hdr and I'm using fullscreen, not windowed.
But simhub overlays are only working in windowed mode (borderless).
I guess your 4k monitor is an hdr and TV?
However you have fullscreen activated in the graphics settings. So are you even using simhub overlays or how is that used?
It takes 0.60ms in the python app section of the csp render stats app.
Sorry, your settings don't really make much sense overall.
You have fullscreen + vsync checked but then set a fps limiter to 50 fps, which normally gives really bad stuttering since vsync will alternate between 30 and 60 fps.
Then you have the dxgi windowed mode optimization active, although you're using fullscreen.
Explanation for vsync with too low limiter below:
The monitor, with vsync active, always waits for a complete frame before putting it on screen.
60 Hz means 16.67ms between frames.
50 fps means 20ms between frames.
So the first frame will get displayed, then there's a 3.33ms seconds gap before the next fps is ready.
So the monitor will display the first frame a second time while waiting.
While that frame is displayed a second time, the gpu will have completed the second frame.
So as the 3rd round of the monitor, the 2nd fps will get displayed for 16.67ms.
Now the gpu had enough time to complete the next frame and will display the 3rd fps in the 4th round of the monitor.
Yes, this is quite complicated but in short:
Monitor rounds & fps:
1st round = frame/fps 1
2nd round = frame 1 again
3rd round = frame 2
4th round = frame 3
5th round = frame 3 again
6th round = frame 4
7th round = frame 5
Sorry that there's no quick help!
A quick fix would be to disable everything in csp apart from:
- General
- ffb tweaks
- grass fx
- reflections FX
- smart shadows
But it would also kill night lights/weather transitions/rain etc.