NX2navi black screen on launch
nx2 navi black screen is not one fault. Match the log line before you delete caches or swap cards.
Read logs\nx2navi.log before you change drivers. The six branches below come from separate issues. A black window can be an Intel driver crash, a missing mesh-shader extension, an AMD integrated GPU whose host heap is too small, a corrupt shader cache, one translated shader after a cutscene, or a Linux/Proton session the project does not support.
| Branch | Signal | What people did next | Status |
|---|---|---|---|
| Intel Arc driver | igvk64.dll offset and exit code 71, quit after a few seconds | Update the driver; back up and rebuild shader_cache; reopen an issue if it returns | 4 independent user reports · #141 #319 #345 #300 |
| No mesh shader | Log skips mesh draws; status 0xC0000409 | Use a GPU with VK_EXT_mesh_shader. There is no fallback pack | 3 independent user reports · #329 #222 #361 |
| AMD iGPU heap | Title screen fails on an integrated GPU with 16 GB | Use a discrete GPU. Integrated graphics are a known limit | 2 independent user reports · #317 #155 |
| Bad shader cache | Crash every launch; one launch works after the cache is removed | Back up shader_cache and pipeline-cache.bin, then let the launcher rebuild them | 1 source · #300 |
| Cutscene shader | HUD and title stay up; the world goes black after a cutscene | 0.6.x notes say part of shader 12096 was fixed; attach the log if it remains | 1 source · #208 |
| Proton or Wine | World black, HUD visible, on Deck or Linux | Return to the Windows build. Shadow env vars are not a fix | 2 independent user reports · #265 #267 |
A short decision order
- If code 71 appears on Intel Arc, compare the driver reports and the v0.6.1 RTSS fix; the code alone is not a diagnosis. Back up caches before rebuilding them.
- If the log names VK_EXT_mesh_shader, stop looking for a redistributable. The card cannot run this build.
- If the GPU is an AMD integrated part and the failure is the title screen, the readme already lists that limit.
- If deleting shader_cache lets you in once, stay on the cache branch.
- If only cutscenes go black, stay on the shader-translation branch and include the log when you report it.
- If you are on Proton, Wine, or SteamOS, the player packages are Windows builds. Deck reports are collected on the Steam Deck page.
I am not copying screenshots other people attached to issue 265. Those files stay on GitHub. Read the attachments in the linked issue in their original context. A text page cannot tell you which branch your PC is on without the log and the GPU name.
Vulkan requirements · All symptoms · Steam Deck
Questions
Which log line matters first?
Exit code 71 appears in Intel driver reports, but the v0.6.1 release also records a separate RTSS-related code-71 fix. 0xC0000409 shows up on the missing mesh-shader reports. Read the GPU name next to that code.
Should I set NX2NAVI_SHADOW?
Issue 265 tried NX2NAVI_SHADOW=1 on a Linux black world and it did not change the picture. Setting it to 0 was followed by a device loss. I do not list it as a fix.
Is a black screen after a cutscene the same as a black launch?
Issue 208 describes a world that goes black after a cutscene while the HUD stays up, tied to a shader translation. That is a different branch from a launch that never draws.
Sources
- Public user report #155 · checked 2026-11-10
- Public user report #222 · checked 2026-11-10
- Public user report #267 · checked 2026-11-10
- Public user report #300 · checked 2026-11-10
- Public user report #317 · checked 2026-11-10
- Public user report #319 · checked 2026-11-10
- Public user report #345 · checked 2026-11-10
- Public user report #361 · checked 2026-11-10
- Issue 141 · checked 2026-11-10
- Issue 329 · checked 2026-11-10
- Issue 265 · checked 2026-11-10
- Issue 208 · checked 2026-11-10
- Project readme · checked 2026-11-10