Checked 10 Nov 2026 · v0.6.1

Problemas comuns do NX2navi

Comece pelo arquivo logs\nx2navi.log. O código de saída e o nome da GPU separam as causas melhor do que um único conselho.

Quadro do vídeo em português, 7 nov 2026Quadro da RX 580, MODO XMP, 8 nov 2026

A tabela mantém os termos e relatos em inglês para acompanhar as fontes originais; os links abrem os relatos públicos.

A ordem que eu uso: log, overlay F10 se o jogo abrir, linha do dump 1.1.1 build e0f3ccfa, extensão VK_EXT_mesh_shader, e só então uma chave do nx2navi.ini. Placa sem mesh shader não tem modo alternativo. Gráficos integrados AMD podem falhar na tela de título, issues 155 e 317.

SymptomTriggerCauseWhat to tryReported versionsIssuesSource status
Black screen; HUD or title may remain visibleLaunch, cutscene, driver or unsupported-platform pathSeveral reported causes: Vulkan driver failures, missing mesh shaders, integrated-GPU memory limits or shader translation.Read the log and GPU name; compare the dedicated black-screen branches. Update drivers and back up caches before rebuilding them.0.5.0–0.6.1#46, #141, #155, #208, #265, #267, #300, #317, #329, #34510sources

Independent user report #46 · 2026-11-10

Independent user report #141 · 2026-11-10

Independent user report #155 · 2026-11-10

Independent user report #208 · 2026-11-10

Independent user report #265 · 2026-11-10

Independent user report #267 · 2026-11-10

Independent user report #300 · 2026-11-10

Independent user report #317 · 2026-11-10

Independent user report #329 · 2026-11-10

Independent user report #345 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Window closes at launchDriver, Vulkan, cache or game-inspection failuresThe exit code alone does not identify the cause.Read the final FATAL line; check the required Vulkan extensions and the launcher inspection result; attach logs to a matching issue.0.5.0–0.6.1#141, #208, #300, #319, #345, #347, #3957sources

Independent user report #141 · 2026-11-10

Independent user report #208 · 2026-11-10

Independent user report #300 · 2026-11-10

Independent user report #319 · 2026-11-10

Independent user report #345 · 2026-11-10

Independent user report #347 · 2026-11-10

Independent user report #395 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Short pauses on first visits or after updatesA new area, effect, install or graphics driverThe driver still builds some pipelines even though game shaders are prepared.Allow normal preparation to finish; retain the cache unless corruption is indicated; compare issue #32.0.4.0–0.6.1#32, #3232sources

Project documentation (same publisher) · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Independent user report #32 · 2026-11-10

16 GB system-memory exhaustionMemory-intensive areas, including Hyrule FieldProject notes confirm this risk; individual reports vary by settings and hardware.Close memory-heavy applications and try lower resolution or frame-generation settings; record logs if the crash continues.0.6.0–0.6.1#240, #259, #3362sources

Independent user report #240 · 2026-11-10

Independent user report #259 · 2026-11-10

Independent user report #336 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Video-memory pressure or allocation failureHigher resolution or frame generation on memory-limited GPUsReports describe allocation failures; no project-wide VRAM minimum is published.Try lower resolution and disable frame generation; keep each hardware report separate rather than infer a universal VRAM threshold.0.6.0–0.6.1#240, #259, #3362sources

Independent user report #240 · 2026-11-10

Independent user report #259 · 2026-11-10

Independent user report #336 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

AMD integrated GPU fails at title or area loadIntegrated Radeon graphics, including 5600G and Legion Go S reportsProject notes describe a host-memory-heap limit.Compare the issue and required extensions; select an existing discrete GPU where available. No general integrated-GPU fix is established.0.5.0–0.6.1#155, #3172sources

Independent user report #155 · 2026-11-10

Independent user report #317 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Mesh draws skipped; missing geometry or crashGPU or driver does not expose VK_EXT_mesh_shaderThe project requires this Vulkan extension and publishes no fallback.Check the extension list and a current driver. A runtime download cannot supply an unsupported GPU feature.0.5.0–0.6.1#222, #329, #3613sources

Independent user report #222 · 2026-11-10

Independent user report #329 · 2026-11-10

Independent user report #361 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Device lost or upload-submit failureArea changes, driver problems or memory pressurev0.6.1 fixes one freed-texture path; other reports remain hardware-specific.Update to v0.6.1, check the driver and reduce memory pressure; compare the exact log and version with the linked report.0.6.0–0.6.1#335, #344, #3613sources

Independent user report #335 · 2026-11-10

Independent user report #344 · 2026-11-10

Independent user report #361 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Random red flashes with HUD still visibleRX 9070 XT reports on 0.6.1Cause is not established by the cited reports.Compare the affected version and scene with the issue; a rollback is a reported workaround rather than a general fix.0.6.1#331, #280, #3743sources

Independent user report #331 · 2026-11-10

Independent user report #280 · 2026-11-10

Independent user report #374 · 2026-11-10

Crash when opening settingsSome AMD Radeon GPUs on 0.6.1Listed as a known issue in the release notes.Back up nx2navi.ini and change documented settings there while following release updates.0.6.11source

Project documentation (same publisher) · 2026-11-10

Inspect Your Game stops with exit code 1Unusable or incompatible input file; path or inspection errorThe launcher inspection result is the evidence; a file-size guess does not establish integrity.Check the inspection log for the required game version and build. Keep the original files and include the report in an issue.0.6.1#347, #3952sources

Independent user report #347 · 2026-11-10

Independent user report #395 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

SmartScreen warning or antivirus detectionUnsigned Setup; separate antivirus reportsSmartScreen signing status and malware detection are different signals; no malware verdict is established here.Use GitHub Releases and compare the SHA-256. A matching digest confirms identity only; review a security warning before deciding whether to run the file.0.4.0–0.6.1#8, #135, #194, #227, #2935sources

Independent user report #8 · 2026-11-10

Independent user report #135 · 2026-11-10

Independent user report #194 · 2026-11-10

Independent user report #227 · 2026-11-10

Independent user report #293 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Proton tools or Linux shader/build failureSteam Deck, Proton, Wine or native Linux source buildsThe launcher and Setup are Windows-only; public Linux reports describe different failure paths.Compare the exact issue and source-build documentation. The Hookshot Deck video describes a different project and establishes no NX2navi compatibility result.0.5.0–0.6.1#36, #186, #258, #265, #267, #2986sources

Independent user report #36 · 2026-11-10

Independent user report #186 · 2026-11-10

Independent user report #258 · 2026-11-10

Independent user report #265 · 2026-11-10

Independent user report #267 · 2026-11-10

Independent user report #298 · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Project documentation (same publisher) · 2026-11-10

Tela preta · Requisitos

Questions

Onde fica o log?

logs\nx2navi.log, ao lado da instalação. Procure FATAL, o exit code e a GPU.

16 GB bastam?

É o mínimo do readme. O mesmo texto lista falta de memória em Hyrule Field nessas máquinas.

Sources

Advertisement