Naruto: Rise of a Ninja — Recomp

A static recompilation for PC powered by ReXGlue
Native Direct3D 12 and Vulkan renderer with 60 and 120 FPS • Windows and Linux • DLC support • Seven languages

Installing · Updating · Native renderer and 60 FPS · Build and run · Configuration · Troubleshooting

A PC port of Naruto: Rise of a Ninja, originally released for Xbox 360. The project uses the ReXGlue SDK to translate the game's PowerPC code into C++ and compile it for native execution. The SDK runtime provides system services, audio, and input.

The game can be drawn by two renderers, available in the executable: the native renderer, the default, which draws the game's Direct3D calls with Direct3D 12 or Vulkan and can present at 60 or 120 FPS, and Xenos, the SDK's emulation of the Xbox 360 GPU, as the alternative.

Releases target Windows x64 (ZIP) and Linux x86-64 (AppImage, native renderer on Vulkan). Presets for other platforms exist, but do not represent complete or verified support for this port.

Graphics

• Two renderers: the native renderer on Direct3D 12 or Vulkan (default) and Xenos as the alternative. See Native renderer and 60 FPS.
• 60 and 120 FPS with the native renderer, keeping the game's logic at its original rate.
• 21:9 and 32:9 ultrawide with the Xenos renderer, with projection adjustments and anamorphic presentation; configured through narutorise.toml.
• Internal resolution from 1× to 4× (also 1.5× with the native renderer), up to 16× anisotropic filtering, FXAA, FidelityFX CAS/FSR, fullscreen, and VSync.
• Native renderer options: MSAA (2×, 4×, 8×), transparency antialiasing, brightness, frame latency, and triple buffering.
• Graphics card selection for both renderers; hybrid laptops use the dedicated card by default.

Content and languages

• DLC support, with import from the setup screen or in-game menu and STFS package installation at game startup. Character DLCs use additional recompiled engine modules.
• Game language selection, with English, French, German, Spanish, and Italian options in Settings → Game; available text and voices depend on your game files.
• External translation mods, selected in the menu's game language list, with UTF-8 text replacements by ID and fallback to the original English text. Releases include the complete Brazilian Portuguese package. See the translation mod guide.

Menus and distribution

• Open the game directly: extract the ZIP, run narutorise.exe, and select your original Xbox 360 ISO or a complete extracted copy. The ISO is read in place.
• Setup screen on first launch, for missing game files, or in safe mode (hold Shift while opening or use --setup).
• In-game menu with Settings, DLC and Exit game: press F1 or Back+Start. Both shortcuts are remappable. The game continues running while menu input is captured.
• Seven interface languages, shared settings before and during the game, Show FPS, shader progress, update notices and desktop shortcut creation.
• ZIP distribution, plus a temporary compatibility bridge for older installed copies.
• Native Linux AppImage with the Vulkan renderer, on Wayland or X11.
• Local diagnostics: each session keeps its log and, after a crash, a dump; Settings → Advanced → Diagnostics exports a session to a ZIP for bug reports. Sending crash reports is opt-in: the first start asks, and nothing is sent before the answer. See Local diagnostics.
• Shader caches: bundled Xenos storage seeds the user cache; native shaders are translated at build time and embedded in the executable.

On Xbox 360, the game runs its logic in fixed steps: 30 per second in the open world and 60 in fights. The Xenos renderer keeps those rates. The native renderer can present more frames than the logic produces:

The native renderer is the default: choose Direct3D 12 or Vulkan and the Frame rate under Settings → Display (60 by default). Xenos is available by setting renderer = "xenos" in narutorise.toml; its path does not provide the native setup or in-game menu. Builds without the native renderer use Xenos (build guide).

Above 30 FPS, the game's logic keeps its original step, and the renderer draws the frames in between by interpolating objects, characters' poses, and the camera between the last two logic steps. Game speed, physics, and timing stay those of the console. With VSync on, the rate does not exceed the monitor's refresh rate. The HUD minimap still updates at 30 FPS, and the image trails the logic by one step (up to about 33 ms in the open world).

See Renderers and frame rate for how it works, its limits, and its known issues, and Configuration for every option.

• Windows: Windows x64, a GPU and driver compatible with Direct3D 12 or Vulkan (Xenos requires Direct3D 12), and the Microsoft Visual C++ x64 Redistributable.
• Linux: x86-64 with glibc 2.43 or newer (check with ldd --version), a Vulkan driver (Mesa or NVIDIA) and FUSE. On an older glibc the AppImage does not start; use the Windows ZIP through Proton there.
• Your Xbox 360 ISO or a complete extracted copy, including default.xex. The source tree does not include game data or DLC packages.
• An SDL-compatible controller is recommended. Keyboard and mouse can be configured in Settings → Controls; see Keyboard and mouse.

Download naruto-rise-recomp-win-amd64.zip from the Releases page. Extract it to a writable folder and run narutorise.exe. Game data is supplied separately. The ZIP creates data/ for preferences, logs, saves and DLC packages; defaults/narutorise.toml is the factory template. Settings → Advanced can show, open or change the data folder after restart. Linux AppImage uses the XDG data directory by default. See Data folder and recovery.

On first launch, choose your original Xbox 360 ISO or default.xex from a complete extracted copy. The game validates the supported revision and reads the ISO directly. Later launches follow the Show menu at startup preference. Hold Shift while opening, or run narutorise.exe --setup, to return to setup.

Press F1 or Back+Start while playing for Settings, DLC and Exit game. Create a desktop shortcut from Settings → Advanced. See the DLC guide for additional content.

On Linux, download NarutoRise-<version>-x86_64.AppImage, make it executable (chmod +x) and open it. Select the ISO or a complete game folder on first launch, or put the game files in game/ beside the AppImage. Data goes to ~/.local/share/narutorise ($XDG_DATA_HOME). Without FUSE, run it with --appimage-extract-and-run.

The game checks GitHub Releases in the background and offers to open the release page. It does not download or install updates. Release eligibility follows GitHub's published/pre-release flag; a beta tag can still be eligible. Checks are cached; playing offline works.

Close the game, download the new ZIP, and replace the package files while keeping the active data/ folder and data_location.json selection file. Preserve game/, game_root/, saves, DLC and mods. All active mods and translations live in the active data folder's mods/; eligible old mods are copied there with originals preserved. Updates refresh only the immutable defaults/mods/pt-br seed and preserve active personalizations. To update an active translation, back it up and merge the new seed deliberately. See data-folder recovery.

For an installed 0.3.0-beta copy, use the separately attached NarutoRiseInstaller.exe compatibility bridge. The old launcher's updater can hand off to it using /MODE=update. It keeps the installation folder and user data, replaces the known shortcuts to open narutorise.exe, and removes the old launcher. You can also run the bridge manually, choose Update an existing installation and select the PC port folder. There is no ISO import step.

The bridge remains attached for several releases because older launchers check only the latest release. For a portable ZIP updated manually, the old narutorise_launcher.exe is left untouched; you may delete it. See the packaging guide for commands and migration tests.

On Linux, close the game and replace the AppImage file. The data folder stays where it is.

Planned work, in no particular order:

• Linux on more systems. The AppImage needs glibc 2.43; distributions with an older glibc and the Steam Deck still need a compatible build and testing.
• Ultrawide with the native renderer. It currently draws at 16:9, with bars on wider monitors.

Read the technical analysis before changing the runtime or code generation files. When reporting an issue, include reproduction steps, version/build, CPU, GPU, driver, the renderer and frame rate you use, your configuration, and logs from logs/ inside the active data folder shown in Settings → Advanced. After a crash, attach the ZIP from Settings → Advanced → Diagnostics → Export previous session. Also mention whether you use ultrawide, DLCs, or a Title Update.

Keep game files, content packages, derived shader data, and generated recompiled code out of commits. SDK changes should include reproducible patches in patches/sdk/.

Testing

• entityeternal, for testing the native renderer and frame rate builds and reporting issues.
• JellySnek, for helping the project since the beginning, reporting bugs and suggesting features.
• tylerl567, for testing on the Steam Deck.
• rubenlopezgirao, for helping investigate crashes (#72) to improve the game's stability.

Projects and libraries

• ReXGlue, recompilation SDK and runtime.
• Xenia and XenonRecomp, foundations and references for the Xbox 360 recompilation ecosystem.
• XenosRecomp, shader translation for the native renderer (forked in tools/xenosrecomp/), and Plume with D3D12 Memory Allocator, its Direct3D 12 backend.
• SDL, Dear ImGui, AMD FidelityFX, extract-xiso, and Inno Setup.

References

• Unleashed Recompiled, the model for the native renderer's design and its graphics card option.
• The Xenia Canary community and Hells Gate Recomp, references cited in the ultrawide implementation.
• Ubisoft Montreal, for the original game. Logo source.

Copyright (C) 2026 Jorge Barbosa. The source code of this port is licensed under version 3 of the GNU General Public License (GPL-3.0-only). The v0.2.0-beta.1 release was published under the MIT License.

Third-party code keeps its own license: the ReXGlue SDK (sdk/, BSD-3-Clause) and its dependencies, the XenosRecomp fork (tools/xenosrecomp/, MIT), Plume and D3D12 Memory Allocator (MIT), RmlUi (MIT), FreeType (FTL), and the embedded Roboto Condensed fonts (app/ui/fonts/, OFL-1.1). The developer extractor remains under its own license in tools/extract-xiso/. Release packages include the notices of every component they ship in licenses/ (component list).

Naruto: Rise of a Ninja, its content, and its artwork and trademarks, including the game artwork in launcher/assets/ and docs/assets/, belong to their respective owners and are not covered by this license. No game data is distributed with this project.