Ideas
MRASPZX I wrote an explanation of what Time Nudge (TN) is.
High TN/slowmo/skating inconsistency issue on official servers | EA Forums - 12740587
A post with CPU performance troubleshooting tips.
Severe Time Nudge / Rubberbanding in most modes — Still Unresolved | EA Forums - 12761674
Hey everyone,
After quite a bit of testing (both on my own system and through customer feedback), I think we’ve found one more piece of the puzzle regarding the TN value spikes / Time Smoothing instability many players have noticed.
🔍 What We Found
On lower-end CPUs (typically under 64 cores), the game runs smoothly — no TN spikes or timing issues.
On high-end CPUs, especially AMD systems or Intel CPUs with Turbo Boost enabled, the problem appears much more often.
When Turbo Boost (Intel) or Precision Boost / PBO (AMD) is disabled, the issue completely disappears.
I’ve confirmed this on several partner systems as well. We originally encountered similar timing problems during engineering simulations in ANSYS, and the same fix worked there too — disabling CPU boost features stabilized everything.
⚙️ Possible Cause
It looks like Battlefield 6’s engine is very sensitive to CPU frequency fluctuations.
When Turbo Boost rapidly changes the clock speed, it can throw off the game’s internal timing or thread synchronization, which leads to the abnormal TN readings and stuttering.
✅ Workaround
If you notice the TN value climbing very high (100–1000 ms) while CPU and memory usage look normal:
Try disabling Turbo Boost (Intel) or Precision Boost / PBO (AMD) in your BIOS.
Restart the game and monitor the TN value again.
For me, and for several others I’ve spoken with, the TN value dropped to around 8–30 ms, and the stuttering was completely gone.
💬 Summary
Battlefield 6 seems stable on lower-core CPUs, but high-end processors may experience timing issues caused by Turbo Boost / Precision Boost.
If your TN values are spiking even with stable FPS and ping, try turning off CPU boost features — it might completely fix the problem.
- Throttled_Up2 months agoSeasoned Novice
This is the answer! If I hadn't hit my head on all of the silly assumptions the internet is making, I would have breezed right past your solution. But it did, in fact, completely fix the problem.