Guides · Performance & graphics
Performance & graphics
Frame rate and visuals depend on the game, scene, GPU, drivers, and the exact Citron NEO build. Read GitHub release notes before changing settings or versions.
Basics first
- Update GPU drivers (Windows / Linux) or OS GPU stack (macOS / Android).
- Citron is Vulkan-focused on desktop — confirm Vulkan works on your system.
- Meet at least the recommended bar on System requirements.
- Close heavy background apps; prefer SSD storage for game libraries when possible.
In-app graphics settings
Labels vary by build — open Options → Settings or per-game Properties. Common levers:
- Resolution scale — higher looks sharper, costs GPU; 1× native is the fairness baseline for comparisons.
- VSync / frame limit — match display refresh or unlock for benchmarking (with tearing).
- Shader cache — first run stutters while caches build; later launches usually smooth out.
- Anti-aliasing, anisotropic filtering, and API choice — when exposed, change one setting at a time while testing.
Compare builds fairly
- Same game, same scene, same resolution scale, same driver branch.
- Do not compare a promo clip on one GPU to your laptop on another build — see Troubleshoot → Rendering, FPS, and GPU differences.
- When a regression appears after upgrade, roll back one GitHub Asset and retest before tuning graphics (All builds).
Platform notes
- Laptop: plug in power; switch to discrete GPU if hybrid graphics causes low FPS.
- Steam Deck: lower resolution scale or cap FPS in heavy areas; Desktop Mode for bulk settings.
- Android: thermals limit sustained FPS — see Android devices.
Reporting performance bugs
Include exact asset filename, GPU model, driver version, game title, and whether it reproduces on the latest tagged release or nightly.