Quick answer
First separate server or network behavior from local frame pacing. If FPS stays stable while characters snap or movement rubberbands, record the server region, approximate UTC time, map, and network-warning state before changing graphics settings. For local stutter or FPS drops, test ray tracing off, fullscreen versus borderless, a stable FPS cap, VSync on and off, frame generation off, and one upscaler mode at a time. For a freeze while returning to the lobby, first record whether Windows still responds, then repeat only once with frame generation off before changing another variable.
If your PC is near the official minimum spec, start with the system requirements page and treat stable frame pacing as the first goal.
What to share with other players
A useful performance report includes server region, approximate UTC time, map or route, network-warning state, whether positions snapped while FPS stayed stable, display mode, FPS cap, VSync state, frame generation state, upscaler mode, and whether the issue repeats. The copy button above gives a compact checklist that can be pasted into a thread.
Related guides
FAQ
Is this a final settings guide?
No. It is a repeatable test tool for live-build troubleshooting. Recommended settings should be rechecked after game patches and graphics driver updates.
Should I copy the checklist into a support thread?
Yes, if the thread asks for performance details. A checked test list is more useful than only saying that the game stutters.
What should I record after a post-match lobby freeze?
Record whether Windows remained responsive, the exact transition that froze, solo or trio, frame-generation state, driver version, approximate UTC time, and whether one controlled repeat reproduced it. This does not identify the cause by itself, but it gives support a much cleaner report.