Fast answer

Update the game, OS, and driver; verify current requirements; test without unsupported mods or overlays; then separate repeatable 0.5 regressions from general Early Access performance. The tracker still describes ongoing optimization.

Do this first

Save-safe order

  1. Record build, hardware, world, location, and whether the issue began in 0.5.
  2. Update OS and GPU driver, then restart.
  3. Verify files and test without unsupported mods/overlays.
  4. Compare a new world with the affected world without deleting either.
  5. Report a repeatable location or action.

01

Local checks first

Use the official checklist for requirements, display settings, drivers, file integrity, mods, thermals, and CPU/GPU conditions. Change one variable at a time.

02

Recognize a regression

A useful regression report has a before/after build boundary or a repeatable location/action. Large-file deletion, registry edits, and third-party optimizers are not official first-line steps.

  • Exact build before and after
  • Same save and location
  • Same settings
  • Solo versus co-op
  • Repeatable duration or trigger

Evidence ledger

Sources checked

Official supportImprove Game Performance

Official settings and system checklist.

OfficialGrounded 2 Issue Tracker

Authoritative issue IDs and current status. Recheck the tracker before acting on a status label.

Official supportGrounded 2 FAQ and Requirements

Official minimum and recommended PC requirements.

Editorial boundary

Official sources establish shipped features, issue status, and support steps. Cross-check and community sources are labeled and never treated as universal fixes.