citron neo crashes on launch
Check whether a Sunshine or Apollo host is running and which Citron build you installed, since both cause launch crashes that look like graphics faults.
Citron Neo describes itself as a continuation of the Citron codebase — its site calls it “a reincarnation of the now gone yuzu emulator” — and its README lists Windows, Linux, macOS and Android (arm64) as supported targets. The launch failures on its tracker are rarely graphics settings. They trace to a handful of causes that can be told apart before you change a single option.
First: which Citron did you install?
Citron Neo continues an older Citron, and on Linux the two were found to share one data directory: /home/<user>/.local/share/citron/. The reporter had installed Citron Neo first, then the original Citron, and games would not boot in the original (#439). That report states its scope plainly — the author tested Linux and had not tested Windows — so treat it as a Linux finding rather than a cross-platform rule.
There is a second, related wrinkle: the 2026-03-27 release notes say “PORTABLE MODE ON BY DEFAULT: this means you can use user folder”, so the build keeps a user folder rather than relying on a fixed system path. If you have switched between builds, check whether a user folder sits alongside the executable before concluding that a build is broken.
Second: is a streaming host running?
This is the failure nobody guesses. Citron’s GPU thread crashes whenever the Sunshine or Apollo game-streaming host is running — the host does not have to be streaming, merely having the process alive is enough, and closing it stops the crash entirely (#321).
The evidence is unusually solid: the same pattern reproduces on Windows and Linux, across different NVIDIA drivers, and over completely different capture stacks (DXGI Desktop Duplication versus KMS/DRM), which rules out a driver-specific cause. A separate report narrowed it further — not game-specific, not NVIDIA multimedia engine contention, not a third-party DLL (#319). Validation layers in #321 additionally caught the emulator generating invalid SPIR-V during pipeline creation, though that report itself notes the connection to the crash is not established.
So before anything else: quit Sunshine/Apollo from the tray or systemd, then launch Citron again. If the crash disappears, you have found it, and no emulator setting will fix it while the host lives.
On an ARM Linux handheld, check the packaging
On devices with a recent Mesa Turnip driver — the report names Qualcomm SM8750 / Adreno 830 in an AYN Odin 3 — the arm64 AppImage crashes immediately on every game launch, before rendering, with an undefined symbol. The cause is packaging, not your setup: since the Linux arm64 nightlies switched to the -use-nopgo build packaging, the AppImage bundles its own libxcb-dri3 and libwayland-client, which shadow the system Mesa driver (#289). The last build before that switch — db04a1263, 2026-07-15 — works on the same machine. On a handheld, go backwards rather than forwards.
On macOS, the crash arrives before the log
Two reports share a shape: the app dies at launch, and one of them explicitly notes no log file gets written, so there is nothing to inspect (#322, MacBook Air M4 on macOS 26.5.1; that reporter also confirmed a downgrade to the 2026-03-20 build behaves the same). The other comes from a dmg whose Applications folder shortcut did not appear; the user moved the app across manually, bypassed the security prompt, and it crashed on open (#313, ARM-64 native).
Neither thread carries a confirmed fix, and downgrading did not help in #322. What you can rule out cheaply: move the app with the dmg’s own shortcut rather than a manual drag, and confirm you are launching the app bundle rather than a copy that lost its resources.
Windows: two zips, one of them English-only
Windows builds ship as two separate archives, -x64-clangtron and -x64-msvc. The difference is not cosmetic for some users: the clangtron nightly is built without Qt translation files, so its interface only appears in English even though the repo contains dist/languages/zh_CN.ts and other translations. The cause is a CMake flag — ENABLE_QT_TRANSLATION defaults off and the clangtron build script does not enable it (#310). If you want a non-English UI, that is a build choice, not a setting you missed.
Games slow down on a high-refresh monitor
On a 240 Hz display, games were reported running in slow motion while the same games behaved normally at 60 Hz. It happens in-game under heavier rendering, not in menus, and the reporter suspected adaptive frame skipping not coping with the higher refresh rate (#315). The practical check is free: cap the display or the game to 60 Hz and see whether the slowdown leaves with it.
The official floor for hardware
Citron Neo’s own FAQ gives a minimum of 6 GB of RAM, a GT 710 2 GB DDR2 or similar, Windows 10 or Android 13 and up, and a Core 2 Quad Q6600. It also states the project’s focus is Vulkan only and that OpenGL support is not required — so a card that handles Vulkan badly is the real bottleneck, not the OpenGL version. On Android, the same page admits support continuity is uncertain because nobody on the team wants to maintain it, which is worth knowing before you pick this emulator for a phone.