Troubleshooting & F7 traces
Verified fixes for frame-pacing choppiness, Title Update 3 mismatches, Intel GPU test builds, and how to capture F7 graphics traces in v0.5.67.
- Log file: ng2.log
- GPU trace key: F7
- Config file: ng2.toml
- Open issues: 33
Known issues & verified upstream workarounds (v0.5.67)
Every symptom and workaround below comes directly from the gamboozino/ng2recomp README and issue tracker (github.com/gamboozino/ng2recomp/issues):
| Symptom / Issue | Verified Fix or Workaround |
|---|---|
| Game looks choppy even though the FPS counter shows a steady 60 FPS | Third-party overlays and frame limiters that hook Vulkan presentation: especially MSI Afterburner with RivaTuner Statistics Server (RTSS), AMD Adrenalin overlays, or Windows notifications in exclusive fullscreen: can disrupt frame pacing. Close MSI Afterburner and RivaTuner completely (exit from the system tray, not just minimized) and restart the game. |
| First-start installer rejects Title Update 3 file | Ensure you are using the World release Title Update 3 (TU_1A461UL_000000G000000.00000000000O4, extracted default.xexp SHA-1 e9df578781355d9a25e1c0adba8fbb859333456a) for Media ID 69F555CB. The Japanese TU3 (TU_1A461UL_000000C000000.00000000000O3, Media ID 0E6FB1CE) has the same byte size (2,486,272 B) but targets a different executable version and is refused. See Title Update 3 Guide. |
| Experimental Frame Interpolation ghosting (cherry petals, Ryu’s shadow blinking, or memexport trails) | Documented in the upstream README: when experimental Frame Interpolation is enabled, render targets that the Xbox 360 engine carries across frames without clearing (and shader memexport writes) can display the previous frame’s state in interpolated frames, causing doubled cherry petals in the opening scene or blinking shadows. Switch back to standard 60 FPS for artifact-free rendering. |
| Slight audio delay in some pre-rendered cutscenes | Known upstream issue while a native audio engine is on the roadmap. If you want to test experimental audio timing fixes on Windows, try NinjaGaiden2-windows-x64-audio-test2.zip from release v0.5.67 on Download & SHA-256. |
| Rendering glitches on Intel Arc or Intel Iris Xe GPUs on Windows | Release v0.5.67 publishes diagnostic Windows builds (NinjaGaiden2-windows-x64-intel-gpu-test2/3/4.zip) targeting Intel Vulkan driver quirks. Update your Intel Graphics Driver and test intel-gpu-test4.zip if you encounter missing geometry or crashes. |
| Startup crash on older pre-2013 CPUs or virtual machines | Both Windows and Linux archives bundle an AVX2 executable and an SSE4.2 fallback executable. If your CPU or VM hypervisor misreports AVX2 support, launch with the environment variable NG2_NO_AVX2=1 to force the SSE4.2 build. |
| Windowed or Borderless mode judder | Upstream notes that Window Mode: Fullscreen has been tested much more thoroughly than Windowed or Borderless. Switch to Fullscreen under RECOMP SETTINGS > Display if you notice uneven pacing. |
Recording an F7 GPU trace & locating ng2.log
When filing a bug report at github.com/gamboozino/ng2recomp/issues, use the built-in diagnostic tools:
| Diagnostic Tool / Setting | How It Works |
|---|---|
| Press F7 in-game | Records the next frames’ Vulkan draw commands into ~/ng2-trace-<n> (Linux) or C:\Users\<you>\ng2-trace-<n> (Windows). Zip and attach that folder when reporting a visual glitch. |
ng2.log | Main runtime log located in %LOCALAPPDATA%\NinjaGaiden2\ng2.log (Windows), ~/.local/share/ng2-recomp/ng2.log (Linux), or userdata/ng2.log (portable mode). Always attach this file when reporting a crash or freeze. |
log_hitches = true in ng2.toml | Writes a detailed breakdown to ng2.log whenever any single frame takes longer than 25 ms. |
log_file_loads = true in ng2.toml | Logs every game archive path loaded at runtime so mod authors can identify exact file paths to override. |
Recommended PC controllers
Ninja Gaiden II Recompiled supports Xbox, PlayStation and Nintendo controllers with native Xelu button prompts (plus low-latency VK_KHR_present_wait input mode):
| Controller | Best For in Ninja Gaiden II Recomp | Hardware Advantage | Link |
|---|---|---|---|
| Xbox Wireless Controller | Original Xbox 360 layout & prompts | Native XInput mapping matching the 2008 Xbox 360 combat layout | View on Amazon |
| GameSir Cyclone 2 | 1000 Hz Master Ninja precision | TMR sticks, micro-switch face buttons and 1000 Hz wireless dongle | View on Amazon |
| Sony DualSense | PlayStation button prompts | Automatic PlayStation button prompt switching and crisp D-pad | View on Amazon |
| 8BitDo Ultimate 2 Wireless | Windows & SteamOS dock play | Zero-drift TMR sticks, charging dock and rear macro paddles | View on Amazon |
As an Amazon Associate, this site earns from qualifying purchases.
Common questions
How do I reset my settings if the game will not open after changing a display option?
Open or delete ng2.toml inside %LOCALAPPDATA%\NinjaGaiden2 (Windows), ~/.config/ng2-recomp (Linux), or userdata/ng2.toml (portable mode). The port will recreate ng2.toml with safe 1x 60 FPS defaults on the next launch.
Where do F7 graphics traces save on Windows and Linux?
Pressing F7 while a visual glitch is on screen writes a folder named ng2-trace-