Skip to main content
Version: bleeding-edge 🩸

πŸ’₯ Troubleshooting

How to fix the most common issues and crashes in nanos world.

note

If you are creating an asset and facing issues or crashes, please refer to our Troubleshooting Assets Creation page for more specific cooking-related solutions.

Welcome to the general troubleshooting guide. If you are experiencing crashes or stability issues while playing nanos world, please follow the steps below to resolve common problems.

If you have already tried these solutions and are still encountering issues, please jump to the Still Crashing? section.

Common Fixes for Client Crashes​

1. Verify Game Files​

Corrupted or missing files are the most common cause of sudden crashes.

  • On Steam: Right-click nanos world in your Steam Library > Properties > Installed Files > Verify integrity of game files.

2. Update Your Video Drivers​

Ensure your graphics card drivers are up to date. Outdated drivers frequently conflict with modern Unreal Engine rendering features.

  • Check NVIDIA, AMD, or Intel for the latest stable releases.
  • Tip: If you recently updated and the crashes started, try rolling back to a previous stable driver.

3. Clear Local App Data Cache​

Sometimes, cached configuration files get corrupted. Deleting them forces the game to generate fresh ones.

  1. Press Win + R, type %LocalAppData%, and hit Enter.
  2. Find and delete the NanosWorld folder.
  3. Optional but recommended: Delete the NVIDIA folder in the same directory to clear your shader cache.

4) Switch DirectX Versions​

Depending on your hardware, toggling between DirectX 11 and DirectX 12 can resolve rendering crashes.

  • Open your in-game settings and switch from DX12 to DX11 (or vice versa), then restart the game.

5. Disable Overlays & Background Software​

Third-party overlays can hook into the game's rendering process and trigger crashes. Try temporarily disabling:

  • Rivatuner Statistics Server (RTSS)
  • GeForce Experience / ShadowPlay overlay
  • Discord in-game overlay
  • FPS counters or other screen capture software

6. Disable Hardware Overclocking​

If you have overclocked your CPU, GPU, or RAM (including XMP profiles), it might be causing instability when the engine is under heavy load. Try reverting your hardware to its stock clock speeds to see if the crashes stop.

7. Intel 13th & 14th Gen CPU Instability​

A very common issue with modern Unreal Engine games running on high-end Intel processors (like the i7/i9 13th and 14th gen) causes the game to crash during shader compilation, often throwing a misleading "Out of Video Memory" error.

  • Check your motherboard manufacturer's website and update your BIOS to the latest version to apply the official "Intel Default Settings" microcode.

8. Disable Ray Tracing​

If you are running older graphics cards (or even newer hardware under heavy server loads), some bugs in Unreal Engine may cause certain ray-tracing features to lead to sudden GPU driver crashes.

  • Go to your in-game settings under Video > Advanced Quality Settings > toggle Ray Tracing to Off.

Still Crashing?​

If you have tried all the solutions above and are still experiencing instability, we want to hear about it. To help us investigate and resolve the problem as quickly as possible, please submit a detailed report to our Bug Tracker.

Tip: The more information you provide, the faster we can identify the root cause!

When submitting your issue, please ensure you include the following details:

  • Crash Event ID: If the Unreal Engine crash reporter popup appeared, please copy and paste the Event ID. This allows us to track the exact error code and backend stack trace.
  • Reproduction Steps: Provide a step-by-step description of your actions immediately before the crash. Let us know if you can consistently reproduce the issue.
  • System Specifications: List your current CPU, GPU, and RAM.
  • Crash Context: Describe the environment. Were you in single-player, connected to a highly populated server, or interacting with a specific custom asset or script?
πŸ› Report a Bughttps://feedback.nanos-world.com/b/bugs