Ir para o conteúdo principal
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.

If your scripts aren't working as expected, or your server fails to load a Package, check the Debugging & Logging guide and the Server & Script Issues section below.

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.
  • Tip²: You can try a complete clean installation of your GPU drivers using tools like Display Driver Uninstaller (DDU) to remove all traces of old drivers before installing the latest version.

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.
caution

The NanosWorld folder also stores your game settings and keybindings, and they will be reset to default.

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.
  • If you can't open the game, try launching it with the -dx11 or -dx12 command line argument to force a specific DirectX version.

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.

9. Run Steam and nanos world With the Same Privileges​

If one of them runs as administrator and the other doesn't, they can't talk to each other and the game can't find Steam. This usually shows up as a Steam not found. popup saying Please launch Steam first. even though Steam is already open, or as Steam authentication errors when connecting to a server.

  • Run both normally (recommended), or both as administrator.
  • Check that Run this program as an administrator isn't ticked under Properties > Compatibility of either executable (Steam or nanos world).

DLSS or Frame Generation Shows as Not Supported​

The game asks the NVIDIA driver whether DLSS is available, so it can show as not supported even on an RTX card when something between the game and the card is off. When DLSS is selected but unavailable, the game falls back to TSR and writes the reason in the client log (see Where are the logs?), for example DLSS requires an NVIDIA RTX GPU. or The driver is outdated.

Check the requirements first:

  • DLSS Super Resolution and Ray Reconstruction need a GeForce RTX graphics card (GTX cards are not supported).
  • DLSS Frame Generation 2X needs an RTX 40 Series card or newer, and 3X or higher needs an RTX 50 Series card.

If your card meets them, try the following:

  • Update your graphics driver, ideally with a clean installation (see Update Your Video Drivers). New DLSS versions and Frame Generation modes need recent drivers.
  • Make sure the game is running on your NVIDIA card. On laptops, and on desktops with integrated graphics, Windows may run the game on the integrated GPU. Go to Windows Settings > System > Display > Graphics, add the game executable (in NanosWorld\Binaries\Win64\ inside the game folder) and set it to High performance.
  • Plug your monitor into the graphics card, not into the motherboard's video output.
  • Use DirectX 12 for Frame Generation. DLSS Frame Generation doesn't work on DirectX 11, so remove the -dx11 launch argument if you added it, or switch to DX12 in the settings.
  • Enable Hardware-accelerated GPU scheduling (required by DLSS Frame Generation) in Windows Settings > System > Display > Graphics, then restart your computer.
  • Restart the game after changing the frame generation method. Frame generation is set up when the game starts, so switching between AMD FSR and NVIDIA DLSS Frame Generation only takes effect after a restart.
  • Close capture and debugging tools such as RenderDoc, PIX or Nsight, as DLSS is disabled while an API capture tool is attached.
  • Verify your game files (see Verify Game Files) in case the DLSS libraries are missing or damaged.

Server & Script Issues​

Where are the logs?​

  • Server: in the .logs/ folder, next to the server executable (NanosWorldCore.log is the latest one).
  • Client: in %LocalAppData%\NanosWorld\Saved\Logs\.

Lua errors are printed in red with the file and line which caused them. Start from the first error, as the next ones are usually consequences of it.

My Package is not loading​

  • Make sure the Package folder name is listed in your Config.toml, under the [game] section (packages, game_mode, map or loading_screen, depending on its type).
  • Folder names must be lowercase and use only letters, numbers and -.
  • Check the server console for Package.toml errors, a missing or invalid setting stops the Package from loading.
  • If it depends on other Packages or Asset Packs, check they are listed in packages_requirements or assets_requirements and are installed.

I can't connect to my server​

  • Make sure the server and the game are using the same Steam App (Playtest or full game), see the --steam_app parameter in Server Configuration.
  • If other players can't join, check that the ports 7777 (TCP and UDP) and 7778 (UDP) are open and forwarded in your router or firewall.

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.

Look Up Your Crash​

Every crash is reported automatically and gets an Event ID, a code of 32 letters and digits:

  • Game: a crash popup appears showing the Event ID. Click View Crash to open its crash page directly, or Copy Event ID to copy it.
  • Server: the server log prints the Event ID together with a direct link to its crash page.

Paste the Event ID in the Crash Lookup page (or open https://nanos-world.com/crash/YOUR_EVENT_ID) to see the stack trace. For known kinds of crashes, such as a corrupted asset, running out of memory or a graphics driver crash, the page also tells you the likely cause and how to fix it.

From there, click report as a bug to open a bug report that already links to the crash, so we get the stack trace without you having to copy anything.

tip

If the page says the crash wasn't found, wait a few minutes and try again: game crashes can take a little while to be processed.

💥 Crash Lookuphttps://nanos-world.com/crash

What to Include in Your Report​

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: Report it from the Crash Lookup page, or paste the Event ID (or the crash page link) in your report. This allows us to track the exact error and 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://nanos-world.com/feedback/bugs