Quick answer
Use the current Steam requirements as the hardware baseline. In game, change one demanding group at a time, test in a representative area, and keep image clarity high enough to read terrain and movement. A “best settings” list cannot replace testing on your own CPU, GPU, memory, resolution, and server.
Step-by-step plan
- Compare your hardware and operating system with the current Steam listing.
- Update the graphics driver and close unnecessary background workloads.
- Record resolution and baseline frame behavior before changing settings.
- Lower the most expensive visual groups in small steps.
- Retest in a busy area and keep the version date with your preset.
Measure the real workload
An empty beach is not a useful worst case. Test near buildings, vegetation, monuments, and active players on the server type you actually use.
Protect readability
Very low settings can make distant movement, shadows, or object edges harder to interpret. Keep a stable frame rate without erasing information you need.
Troubleshoot before tuning
Crashes, corrupted files, overheating, or storage pressure are not ordinary graphics-quality problems. Use official support guidance before treating them as a preset issue.
Checklist
- Official requirements checked
- Driver current
- Baseline recorded
- One setting group changed at a time
- Busy-area retest
What to verify before acting
- Performance varies by update and server.
- Avoid promising a frame rate for a hardware name alone.