There is no single best preset
The game uses Unreal Engine 5 and presents a mixture of dense foliage, long views, lighting, effects, and large multiplayer spaces. A setting that helps one GPU at 1080p may reduce clarity or fail to improve a CPU-limited system at another resolution. Treat every recommendation as a test starting point.
The official Steam requirements target 1080p/60 fps with specific hardware and scaling notes, but those lines are not independent benchmarks. They describe developer requirements, not a promise for every map, server, driver, or background workload. Record the exact build, resolution, map, and hardware before comparing results.
Begin with a controlled baseline
Select an official preset near the expected capability of the machine, use the monitor’s native resolution, and turn off unrelated frame caps or overlays only if they prevent measurement. Test the same scene or training route for several minutes. Write down average behaviour and noticeable drops instead of relying on how one spawn screen feels.
Change one group at a time. If resolution scaling, lighting, foliage, and shadows are all changed together, a higher frame rate will not reveal which choice mattered or which one damaged image quality. Keep a screenshot of the baseline settings so they can be restored.
Resolution scaling and upscaling
The official performance update and developer Q&A specifically discuss resolution scaling and improvements made after beta video options behaved incorrectly. Scaling reduces the internal rendering workload, while an available technique such as DLSS or TSR reconstructs the final image. Lower internal resolution can improve GPU-limited performance but may soften distant detail and vegetation edges.
Use a moderate quality mode first rather than jumping to the most aggressive performance option. Compare motion, distant silhouettes, weapon edges, and foliage shimmer as well as the frame rate. If reducing render scale produces little improvement, the current bottleneck may not be the GPU rendering resolution.
Lumen and lighting cost
Collected settings research identifies Lumen and advanced lighting as important quality-versus-performance controls, while the official performance discussion confirms the broader UE5 trade-off. Lower lighting quality one step and repeat the same route. Look at interior-to-exterior transitions, shadowed jungle areas, and effects during combat.
Do not claim that disabling a feature always improves target visibility. Less complex lighting can increase frame rate while also changing contrast or environmental readability. The correct choice balances stability with the visual information the player needs.
Shadows and foliage
Shadow and foliage quality are logical test targets in a dense jungle game because they affect both scene complexity and visual detail. Reduce one level at a time and compare the same location. Watch for unstable edges, distracting pop-in, and whether distant movement becomes clearer or merely noisier.
Avoid advice that implies lower foliage removes legitimate cover. Settings should improve performance, not be sold as a competitive exploit. Use only the options exposed by the current game and keep the test tied to the release build.
Input latency and frame limits
A steadier frame rate can feel more responsive than an uncapped rate that swings widely. Choose a cap the system can maintain in the tested scenes, then compare input feel and frame pacing. The collected material does not provide verified latency measurements, so this site does not invent millisecond values.
Close unnecessary background workloads before blaming the graphics menu. If an overlay is used for measurement, record which one and confirm it is not causing instability. Use the same driver and power state for every comparison.
Suggested testing order
- Native output resolution and an appropriate official preset.
- Resolution scale or quality upscaling mode.
- Lumen or lighting quality.
- Shadow quality.
- Foliage and effects quality.
- A sustainable frame cap and final clarity check.
Retest after every change in the same location. If one option behaves unexpectedly, restore the baseline and check the current official known issues. The developer Q&A’s claim that performance improved substantially on a developer’s personal PC is evidence of development progress, not a benchmark that every user should reproduce.
Low-, mid-, and high-end starting logic
On a machine close to the published minimum, prioritize a stable baseline and moderate scaling before raising expensive lighting. On hardware near the recommended specification, begin with the recommended quality target and reduce the most expensive options only when the current scene demonstrates a problem. High-end hardware should still be tested in busy multiplayer conditions rather than judged from an empty menu.
These categories do not contain fabricated FPS numbers. Original low, mid, and high hardware benchmarks remain a future enhancement. Until those tests exist, the guide explains how to tune the official controls honestly and reproducibly.