Can you send me NX2navi-Setup by email?

No. Use GitHub Releases or the Direct download button, which points there.

Can you walk me through obtaining a .nup?

No. The README does not provide those instructions. These pages stay on Setup, F1, and GitHub Assets.

Which page should I open first?

Windows install if the .exe will not start. First-time setup if the launcher opens. Requirements if Vulkan fails. Releases if you cannot tell Setup from the helper zips. Controls after the window is up. Troubleshoot if a previously working folder broke after an update.

Do you answer Nintendo account questions?

No. This inbox cannot reset a Nintendo or GitHub login. It cannot sign Setup.exe either. Keep SmartScreen questions on the Windows install page instead.

NX2navi · Windows · Vulkan

Contact

For this website: support@nx2navi.online. For NX2navi the program: GitHub Issues with logs\nx2navi.log. Include the tag number.

Setup and updates come from GitHub Releases for tangerineturtle1/NX2navi. Latest tag is read at request time.

This website

Email support@nx2navi.online about broken links, incorrect wording, privacy questions, or accessibility issues. Include the page URL and what you expected to see. That inbox is not Nintendo support and not the NX2navi maintainer list. We cannot reset a GitHub account, sign an executable, or speed up a local compile. If you write in a language other than English we may still reply in English; this site’s pages are English only for now. Typical useful mail: “/install/windows still names an Asset the latest tag renamed,” plus the tag number and the filename you see on GitHub. Typical useless mail: a screenshot of the whole desktop with no URL.

The program

Use the NX2navi issue tracker. Include the tag, whether you used Setup or source, a short description of what you were doing, and logs\nx2navi.log. Follow CONTRIBUTING.md. Discord rumors and random mirrors are not a substitute for the log.

https://github.com/tangerineturtle1/NX2navi/issues

Keep build output on the PC that built it

This domain exists to point at GitHub and to explain SmartScreen and the first build. A .nup or a playable output directory is not useful as an email attachment. If you need a human to read a failure, paste the last lines of logs\nx2navi.log.

What a good site email looks like

Write from an address you can read. Put the page path in the subject. Quote the sentence that is wrong. Say what the GitHub README currently says if you already compared them. Links to a specific tag help; a screenshot of a whole desktop does not. If the download button showed Open release Assets, that is the designed fallback, not always a bug — mention whether GitHub itself loaded. Accessibility reports should include the browser and whether you use a screen reader. We cannot promise a service-level agreement.

What a good GitHub issue looks like

Use the project’s issue forms when they exist. Title the area or the failure, not “help.” Include tag, GPU, driver, Setup versus source, and a trimmed log. If SmartScreen is the entire story, say so and stop; that is usually not an application bug. If the first build ran for two minutes and died, disk space and antivirus locks are more likely than a bad GitHub URL. If you already found a duplicate, add a comment there instead of a second ticket. CONTRIBUTING.md is short; read it once.

Citing this guide, translations, and impersonation

If you run a blog and want to cite these guides, link the page. Setup still comes from GitHub Releases, not from a scrape of this domain. If you want a translation, wait until this site grows extra locales; English is the only published language today. If a search ad claims to be the official home of the port, it is not this page and it is not Nintendo. Affiliates, coupon pages, and “free Steam keys” banners that wrap our URLs are also not us. The only email we publish is support@nx2navi.online for the guide, and GitHub Issues for the program. If a helper asks for remote-desktop access to “finish the compile,” decline. The launcher does not need your Windows password, and neither do we. If you need a human to read a failure, paste the last lines of logs\nx2navi.log. Ten honest lines beat a two-gigabyte archive every time. If the log is huge, attach the last hundred lines and say so in the first sentence. Name the tag, Setup versus source, GPU, and driver. That is the same report CONTRIBUTING.md already asks for. Useful upstream links from this site: the README for hardware, docs/launcher.md for first run, docs/controls.md for F1 and pads, docs/building.md and docs/README-BuildKit.md for compilers, nx2navi.ini.example for file defaults. Privacy and terms on this domain cover logs and outbound GitHub clicks, not Nintendo accounts. Do not open a GitHub issue against the port for a typo on nx2navi.online; that is what this inbox is for.

FAQ

Can you send me NX2navi-Setup by email?: No. Use GitHub Releases or the Direct download button, which points there.
Can you walk me through obtaining a .nup?: No. The README does not provide those instructions. These pages stay on Setup, F1, and GitHub Assets.
Which page should I open first?: Windows install if the .exe will not start. First-time setup if the launcher opens. Requirements if Vulkan fails. Releases if you cannot tell Setup from the helper zips. Controls after the window is up. Troubleshoot if a previously working folder broke after an update.
Do you answer Nintendo account questions?: No. This inbox cannot reset a Nintendo or GitHub login. It cannot sign Setup.exe either. Keep SmartScreen questions on the Windows install page instead.