Fast answer

If actions respond late for distant players, check the official high-ping issue; if only one device renders slowly, use the local performance branch. Host/client role, distance, and hardware are separate variables.

Do this first

Save-safe order

  1. Ask whether input is delayed, frames are low, or both.
  2. Compare host and client in the same location.
  3. Test the strongest, best-connected machine as host.
  4. Apply graphics checks only to the device with low FPS.
  5. Record regions, platforms, session length, and affected actions.

01

Ping versus frame rate

Network latency delays interactions and state updates. Low frame rate reduces smoothness on one device. They can occur together, but changing graphics settings does not repair long-distance latency.

02

Build a useful comparison

Test solo performance, swap the host once, and note whether movement, combat, inventory, or building is affected. Do not modify a save for a network-performance issue.

  • Same world and location
  • Same build
  • Host/client role
  • Regions and connection type
  • Solo versus multiplayer result

Evidence ledger

Sources checked

OfficialDistance-Related High Ping / Low Framerate

Official issue describing distance and hardware context.

Official supportImprove Game Performance

Official local performance checklist.

Official supportHow to Report a Grounded 2 Issue

Official evidence and attachment requirements for useful support reports.

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.