im tried running 30 cars at night no rain, performance tanks. cpu usage is 13%. cpu usage is low too and so are the gpu frame times. like 1.2 however its a stuttery mess. exe has been patched and followed all the settings. surely something is a miss.
What you're missing is that your CPU has 6 Cores / 12 Threads but GTR2 can't use them.
What you're seeing in TaskManager etc. is the AVERAGE usage of the cores between a refresh cycle of the monitoring tool.
In reality though, a CPU core can only "DO" or "PAUSE" and GTR2 can only use 1-2 cores/threads.
At 4.8 GHz that's 4.800.000.000 CPU cycles per second averaged when you have TaskManager at the standard refresh tick.
The Windows scheduler shuffles the load around across more than 2 cores since it's more efficient in most situations. If you don't lock your CPU to the same clock speed on all cores, you would probably see the first CPU core being used up to 100%.
On AMD Ryzen CPUs you usually lose performance when manually overclocking all cores to the same clock speed and it's better to leave it alone, doing its thing with the cores boosting independently.
That's why you usually see 1-2 cores fully loaded on AMD system but not on manually OC'ed Intels.
To give a basic calculation of what overall CPU load to expect from a 1-2 cores game:
100% divided by the number of virtual threads (12 in your case) x 1.5 = (100%/12)*1.5 = 8.33% * 1.5 = ~13%, which is exactly what you're seeing.
Sadly almost all simracing titles can't use the amount of cores modern CPUs offer. It's pretty difficult to split a chained physics calculation to run in parallel. You can't calculate the aerodynamic before knowing the ride height. So you have to start each physics engine tick with the current speed, driver inputs and the contact points of the tyres with the surface.
Then calculate the whole car from there.
Big developer teams can achieve better CPU usage but smaller teams or teams without enough spare money can't. Sadly.