Compare the same workload
The October 30 0.1.3.1 patch reports more than 50% FPS improvement across various PC configurations and introduces more graphics controls. That is a developer-reported result across some tested configurations, not a minimum performance promise. A launch crash or dead menu is a different issue and belongs in our startup guide.
Establish a useful FPS baseline
- Check the current build before testing. Compare settings only once your game has updated to 0.1.3.1.
- Pick a reproducible scene or worksite. Write down whether the slowdown happens at a clean start, during terrain work, while using vehicles or in a multiplayer session.
- Note your display resolution, graphics preset and any newly offered graphics options. Change one option at a time and compare the same camera position and activity. The patch mentions additional settings but does not name an officially optimal preset.
- Compare single-player with multiplayer only if the same area can be reached safely. Network stalls and simulation frame drops may feel similar but require different evidence.
- If the slowdown occurs mainly while another player connects or terrain downloads, follow the multiplayer join diagnostic instead.
- If persistent, provide the developer with your version, hardware, scene, settings and a short recording or performance log where possible.
Common interpretations
FPS higher after the patch: the optimization may have helped your workload, but cannot be generalized to other hardware. FPS unchanged: not proof the patch failed globally; report the scene and configuration. New severe stutter: record whether it started after an update and whether it affects a clean single-player scene.
FAQ
Is 50% a guaranteed improvement?
No; it is a developer summary across various configurations.
Does the new mini-map cause slowdown?
The patch introduces an optional mini-map, but the checked notes do not establish it as a cause of FPS loss. Test independently before blaming it.
Source and verification
- Groundwork — developer-origin information, checked November 1, 2026.
Independent source-bounded guide, not a claim of first-hand gameplay testing. Version-specific fixes may not cover every remaining issue.
Measure the same scene before accepting an FPS-improvement claim
Developer update 0.1.3.1 describes major performance work and an over-50% FPS improvement in its own context, but that is not a guarantee that every PC, scene or machine will gain 50%. Identify whether slowdown happens in a fresh world, an established construction site or the same large equipment interaction; compare like-for-like resolution, display mode and graphics settings before attributing the result to this patch.
Success: your own stable frame rate and responsiveness improve in a repeated identical workload, without new graphical errors. If only the startup menu freezes or the process crashes before loading, follow the separate startup failure guide instead. Do not invent a mandatory graphics-driver version, magic launch parameter or specific minimum FPS based on the developer’s general performance report.