I’ve done some additional testing on this issue — after disabling C-States and SpeedStep, the problem actually got worse.
Disabling Game Mode also made the issue even more noticeable.
At this point it’s pretty clear the problem isn’t related to power saving or Windows scheduling, but rather something deeper in the CPU-related code or timing logic of the engine.
The “Time Smoothing” value keeps rising whenever the CPU frame pacing fluctuates, even with a perfectly stable network.
So it looks like the interpolation delay system is reacting to CPU timing instability instead of network jitter — basically confirming it’s a CPU-side issue in the current build.
