The only official over the hill pc performance guidance is a Next Fest update that acknowledged performance concerns and advised keeping your GPU driver current. It did not promise that a driver update fixes every case, and no official frame rate target, graphics preset or benchmark exists. Measured full-game performance is 待确认 — everything available comes from the demo.
The controller advice is more concrete: a Windows demo player reported severe input lag on a Bluetooth Xbox One controller after roughly 15–20 minutes, with keyboard input unaffected and USB improving things, and a developer reply endorsed switching to wired as a workaround.
The official guidance, and its limit
The Next Fest update accepted that performance was a concern and advised keeping drivers up to date. That is the whole of it, and the limit is as important as the statement.
Keep your GPU driver current. — official Next Fest guidance, with no promise that it resolves every case
Drivers should come from your GPU vendor's own software or website. Third-party "FPS booster" utilities are not part of this recommendation and are not something this page endorses. A driver update is a reasonable first move, not a diagnosis.
Vegetation density: one report, not a verdict
In a Reddit performance discussion thread, the original poster reported that lowering vegetation density helped on a machine running an RX 9070 XT / Ryzen 7 9800X3D at 3440×1440. Replies were mixed, including from people on similar hardware.
That makes vegetation density a setting worth comparing, which is a much weaker claim than "turn this down to fix performance". It is not evidence of a general GPU defect, and it is not a guaranteed target frame rate. One machine's working setting is one machine's working setting.
A comparison method, not a preset
The following five steps are an editorial procedure designed for this page — not a tested preset or a measured configuration. They are a way to find out what affects your own machine.
| Step | What to do | Why it matters |
|---|---|---|
| 1. Record your setup | Build, GPU driver, resolution, graphics options, input device, single-player or multiplayer | A comparison without these is not comparable |
| 2. Pick a repeatable view | One repeatable viewpoint or short route; note FPS if you have a counter and whether motion looks uneven | Different weather or locations are not the same test |
| 3. Change one setting | Lower vegetation density by one step, retest the same view, change nothing else | Isolates the variable you are actually testing |
| 4. Revert if unhelpful | Restore the setting if nothing changed; a lower resolution is a separate diagnostic, not a cause | Tells rendering load from something more specific |
| 5. Keep only what repeats | Keep changes with repeatable benefit and acceptable image quality | Stops a settings list becoming superstition |
Step four is the one people skip. A resolution change tests whether rendering load is involved at all; it does not tell you what, and treating it as an answer sends you down the wrong path.
Controller lag after 15–20 minutes
This is the most specific performance-adjacent report available, and it comes from a Windows demo player.
A Bluetooth Xbox One controller developed severe lag after about 15–20 minutes of play. Keyboard input stayed normal, and switching to USB improved it. — community report from the Windows demo
A developer reply endorsed switching to wired as a workaround. That endorsement is real, and it does not prove every case of lag or stutter shares this cause. Wireless interference, Bluetooth power management and driver conflicts produce similar symptoms by entirely different routes.
To isolate it: when the problem appears, stop safely, then compare keyboard and mouse in the same scene, then compare a USB controller in the same scene, and leave graphics settings untouched throughout. Do not disable Windows services, uninstall system components or edit the registry on the strength of this report.
The demo beta is history, not an option
The Next Fest announcement did offer experimental performance changes through a demo beta. The August update then explained that maintaining a demo before release was not feasible, while describing continued optimisation work.
So the beta is not a current option. This does not establish that an accessible performance beta, an access code, or any guaranteed improvement exists now, and you should not download unofficial builds to follow advice written for an old branch.
Confounders that ruin comparisons
The game's own features make naive performance comparisons unreliable. It has dynamic weather and a full day/night cycle, so the same viewpoint under clear sky and under rain is not the same test. Realistic terrain deformation means the ground you drove over yesterday has changed shape since. Up to 4 players online co-op adds a variable that no single-player test will ever reproduce.
There are also published feature toggles that will change your numbers: DLSS 4 and FSR 3 upscaling, HDR, anti-aliasing, and an adjustable frame rate cap from 30 to 240 FPS. Those are confirmed feature-list entries, not benchmark results, and a cap you have set will flatter any measurement taken without it recorded.
Specs tested on Full HD resolution. — note on the Steam page's minimum requirement
The Steam minimum requirements — Windows 10, an Intel Core i5-7400 / AMD Ryzen 5 2600, 8 GB RAM, an Nvidia GTX 1070 or AMD Vega-56, DirectX 11 and 4 GB of space — describe a floor, not an expected frame rate.
Reporting a problem
The official Steam discussion area is the right channel. A report becomes useful when it includes the build and your machine, the display and scene involved, when it happens, an input comparison, and what changed before and after.
Keep account tokens, private save files and personal information out of any public report. That is both a privacy matter and a practical one — a report that carries a token gets ignored or closed.
What remains unknown before release
Measured full-game frame rates, recommended graphics presets, and how vegetation density behaves in the release build are all 待确认. So is any Steam Deck data, which is covered on the Steam Deck page instead.
This page establishes no conclusion about stable 60 FPS or full-game performance. What it offers is one official driver recommendation, one community setting worth comparing, and a repeatable way to test both against your own hardware.