Keep the current target and wait for official settings names before changing hardware.
If your result is borderline
Try a lower target, then check whether GPU, CPU, RAM, or storage is the weak point.
If your result needs an upgrade
Use settings changes first when the weak point is the target itself, not a hardware component.
Evidence status
predicted: use this page as a current planning guide. If official PC specs or real benchmark data changes the answer, FrameReady should update the recommendation.
Start with resolution and FPS
Resolution and FPS target decide how hard the game is on your PC. Do not tune settings before choosing that target.
Use 1080p 60 FPS as the first planning target for midrange PCs.
Use 1440p only if your GPU has enough headroom.
Treat high refresh targets as CPU and GPU heavy until benchmarks prove otherwise.
Likely settings to check first
Exact setting names may differ at launch. The pattern is still useful: reduce the settings that usually hit GPU memory, GPU load, or CPU load first.
Lower heavy graphics options before lowering resolution.
Watch texture settings if your GPU has limited VRAM.
Reduce crowd, traffic, or simulation-heavy settings if the CPU is the weak point.
Save the result for later
Saved anonymous results become more useful after official specs, benchmark reports, and patch data arrive.
Save your target resolution and FPS.
Save the weak point shown by the readiness tool.
Check again after official PC information or real benchmark data changes the result.
Settings that usually matter most
FrameReady should avoid pretending to know the final GTA 6 settings menu. The useful planning layer is knowing which setting types usually hit which component.
Texture quality usually leans on VRAM.
Shadows, reflections, and heavy effects usually lean on GPU load.
Crowd, traffic, simulation, and background activity can lean on CPU load.
How to compare settings later
After launch, the best settings page should use saved presets and benchmark reports only when enough similar results exist.
Compare settings by resolution, FPS target, GPU class, CPU class, and patch.
Trust averages only when enough similar results exist.
Separate official patch notes from user-submitted benchmark data.