What official updates say
Official- The July 24 developer note said loading stutters caused by shader precompilation were resolved and combat micro-stutters were reduced.
- The August 6 client update shipped several crash and stability fixes, but it did not claim that all stuttering or latency problems were resolved.
- The August 7 server update said Bellring Games was still investigating intermittent server lag and expected problems to taper off through successive updates rather than one universal fix.
- The August 12 update fixed client hitching, stuttering, and crashes in specific scenarios; it also optimized server performance and deployed fixes for select server-side lag issues.
- Bellring Games says remaining network hiccups are still under investigation and that the new ping display should more accurately reflect in-match input latency.
- The latest official notice says cloud-server CPU hyper-threading was identified as one contributor to intermittent stutter, lag, and teleporting. Configuration adjustments were deployed across all servers on August 13–14, and monitoring showed fewer incidents.
- Bellring Games says performance optimization is still ongoing, so the August 13–14 server changes are not a universal fix for every local frame-time or network problem.
What players report
Community Report- After launch, multiple players on high-end PCs still reported severe hitching during camera turns, combat, and first entry into new areas.
- Reports also exist on PS5 Pro, so the current evidence is not limited to one PC configuration.
- Some players report that first-run hitches ease after repeating an area, but that pattern does not explain every performance problem and is not a verified universal fix.
Identify the symptom
| Symptom | What you see | Next comparison |
|---|---|---|
| Shader hitch | A sharp pause the first time an effect or area appears | Repeat the same route once |
| Sustained FPS loss | Frame rate stays low in the same scene | Lower one GPU-heavy setting |
| Frame pacing | Average FPS looks acceptable but motion feels uneven | Compare a stable cap with frame generation off |
| Network latency | Teleporting, rubber-banding or delayed confirmations | Compare server ping and local animation |
| Crash | The game closes or presents an error | Capture the exact module or message |
Controlled test
- Use the same location, route, resolution, and preset for each comparison.
- Change one setting at a time and record average FPS plus visible hitching.
- Test frame generation separately from upscaling; it can improve displayed FPS without reducing input latency.
- Repeat a route once to distinguish first-seen shader work from a persistent problem.
- If ray tracing is enabled, test it off as one controlled comparison before making deeper system changes.
Before changing settings or drivers
Community ReportPlayers report mixed results with DLSS, FSR, TSR, frame generation, FPS caps, NVIDIA Reflex, ray tracing, and Global Illumination. Compare advice against your GPU, resolution, base frame rate, and the same test route.
Evidence register
Sources and limits
- Verified
- Applies to
- Launch build — public number not confirmed
- No graphics setting or driver change is confirmed as a universal fix.
- Server latency evidence does not prove a local rendering problem, and local FPS evidence does not prove an outage.
- This site has not completed a controlled hardware test for the listed community workarounds.