Lost Odyssey Recomp

An experimental native PC port of Lost Odyssey for Xbox 360.

Windows x64 · Linux x64 · macOS arm64 (experimental) · Direct3D 12 · Vulkan · Metal

Download · Installation guide · 简体中文

Features · Controls · Debug Menu

Changelog · Report an issue · Project board · Build from source

Choose a package from the latest release. The current published version is v0.8.7.

1. Import your game data. The built-in importer opens when no usable game installation is found. Use Files or Folder to select an extracted game folder, default.xex, an XDVDFS ISO or GOD data.
2. Choose the interface language, game language and graphics options. The game starts after setup and shader preparation. If no precompiled shaders for the selected renderer are installed, it first offers to download them; skipping compiles them on your PC. Later launches reuse the shader cache.
3. Add the remaining discs and DLC when needed. Open Gameplay → Import discs & DLC in Settings. With all four matching discs imported, the game selects the requested disc automatically.

Disc 1 is required to start. Use one of the audited Asian multilingual or USA/Europe four-disc sets; do not mix editions. The installation guide covers disc identification, Linux setup, file locations and updates. Release packages need neither Python nor Visual Studio. Keep your saves and profiles when updating.

v0.7.35 was the first release with a macOS package and v0.8.0, v0.8.5, v0.8.6 and v0.8.7 followed: an experimental arm64 path that renders with Metal. Open LostOdysseyRecomp-macos-arm64-v0.8.7.dmg, drag LostOdysseyRecomp.app to the Applications link and start it. The app requires an Apple Silicon Mac with macOS 15 or later (the game has only run on macOS 26). It is ad-hoc signed and not notarized, and it stays that way: the maintainer decided on 2026-10-03 not to do Developer ID signing or notarization. macOS therefore blocks the first launch. Try to open the app once, then open System Settings → Privacy & Security, choose Open Anyway for it and confirm; or run xattr -dr com.apple.quarantine /Applications/LostOdysseyRecomp.app. The installation guide has the steps and file locations. The game's update check only offers to open the release page, so you replace the app yourself. Validation so far is one Mac: on the maintainer's M1 Max (macOS 26.6.2) the opening new-game battle ran with Metal, and with v0.7.35 the Metal shader pack was downloaded and used; a source build with GTAO and 4× shadows also ran the opening battle there. Long play, broader scenes, other Macs, image quality and performance have not been tested. To build it yourself, use the macOS build instructions.

v0.8.7 includes experimental HDR output paths for Windows D3D12/Vulkan, Linux Vulkan and macOS Metal. Enable HDR in Graphics, save and restart. HDR peak brightness opens a frozen frame of the current game scene: the left view is an SDR brightness preview clipped at reference white, while the right view uses normal HDR tone mapping and updates the peak live. Switch between the Scene and Test pattern with the mouse or controller X button; if no valid scene is available, the standard pattern is used. Auto follows the active display's reported peak when available; if none is available, it uses a 1000-nit content reference. The current Linux Vulkan path has no display-peak report, so Auto uses that fallback. On macOS, Auto derives a relative EDR headroom estimate, not a measured panel brightness. Peak adjustments preview on the calibration page; peak and paper-white changes apply after saving without a restart. Since v0.8.0, HDR works together with every anti-aliasing mode (FXAA, SMAA and TAA run on the HDR scene) and every upscaler (DLSS, FSR and MetalFX upscale the SDR scene, and the HDR frame is rebuilt from the upscaled frame plus the game's pre-upscale highlights). DLSS frame generation on Vulkan keeps HDR (checked on an RTX 5080 through the SDR preview only, not on an HDR panel; LO_HDR_FG=0 keeps an SDR swap chain instead). Other frame generation paths (FSR on Vulkan, and everything on Direct3D 12 and Metal) keep an SDR swap chain. Unsupported surface format/color-space pairs fall back to SDR. The maintainer confirmed on-device HDR validation on 2026-10-02; exact platform, backend and display coverage was not recorded, so this does not establish cross-platform coverage. In the v0.7.35 run on a Mac whose external display had no EDR headroom, HDR requested in the game stayed in SDR, and Metal HDR output itself had not been seen. See the HDR technical note for output semantics and validation limits.

An experimental arm64 APK, LostOdysseyRecomp-android-arm64-v0.8.7.apk, is part of the v0.8.7 release: the release workflow builds it with the other packages. It was first added to the v0.8.0 release by hand after publication. It is a development build (the app is labelled "Lost Odyssey (development)") and not a generally supported Android release. The app is signed with the project's debug key and stays that way, so each release installs over the previous one. The runtime uses an SDL Android activity, app-owned external storage, the Android ARM64 FFmpeg configuration and an Android DXC build. See the Android build instructions and the Android port research note for the pinned toolchain and current validation limits.

Installing. Install the APK, then put your game data where the app looks for it: either import on the device (the Game folder page has an Import disc images… button that runs the same importer as the desktop on .iso images or extracted discs from the internal storage or an SD card; it needs "All files access", defaults to the custom game folder or else the app folder below, and starts the game when it finishes) or use the desktop importer (any package) to produce game/disc1–disc4 (and game/dlc/…), connect the device to a PC over USB in file-transfer mode and copy that game folder into Android/data/io.github.freefrank.lostodyssey/files/ (the app creates the game folder with a README.txt there as soon as it is opened, on the internal storage and on every SD card; the four discs take about 20 GB). Disc 1 is required. The game reads the first storage, internal or SD card, that has game/disc1/default.xex, otherwise the internal one. With Automatic updates on, the app checks for a newer release at startup and shows the same update prompt as the desktop (Download (A) / Later (B)); accepting opens the APK download in the browser, and you install it over the current app. On the first start a Qualcomm device shows the GPU driver page (see below); then the game offers the Vulkan shader pack download, which you accept with the on-screen A button. Settings are changed on the in-game Settings page. The installation guide has the steps and the file locations the Android rows.

Logs. The app writes its logs to Android/data/io.github.freefrank.lostodyssey/files/logs/. To report a crash or a black screen, open the app once more, connect the device to a PC over USB in file-transfer mode and attach the newest runtime-*.log, native-stderr.log and any java-crash-*.txt from that folder; see Android logs.

The Android runtime now loads the development resources, plays the opening video and reaches the first battle on the test tablet. Touch input passed title/menu navigation and two opening-battle attacks with visible damage; one initial-battle shader preparation observed a pause of about 40 seconds. Longer play, audio beyond native queue evidence, other GPUs, 16 KB devices and physical-controller validation remain pending. See the Android port research note and Android DXC build note.

The runtime keeps SDL physical-controller support and adds an Android on-screen touch controller. Its source implementation now supports the Controller settings size/opacity controls and an Edit layout screen for dragging, saving, resetting and showing or hiding individual controls; the layout model checks and device UI flow are verified on the development tablet. This source path has not yet been accepted through a complete game session. The generated PPC code also remains available as a separate Android ARM64/PIC static-library target.

On Qualcomm devices the proprietary Vulkan driver draws the text on the highlighted menu row fully transparent. The app therefore opens a GPU driver page before the first game start (and from CTRL → GPU driver while playing) where a Mesa Turnip package can be downloaded from the same sources the Eden emulator uses, or installed from a zip, and selected; the fix was verified with KIMCHI Turnip v26.0.0 R8 on the development tablet. See the Android instructions.

Connecting a USB or Bluetooth controller automatically hides the touch controls while keeping CTRL available. Enable Show touch controls to use both together; disconnecting the last controller restores the saved touch preference. Android also hides unavailable desktop graphics options and rebuilds its Vulkan surface when returning from the background. Its Vulkan shaders can be prebuilt on a host with the Android-specific shader contract; desktop Vulkan bundles are incompatible. See the Android instructions for generation and installation.

v0.8.7 adds to the Android APK: it checks for updates at startup and offers the new APK, creates the game folder as soon as the app opens, reads the game from an SD card or from a folder chosen on the new Game folder page, imports the game on the device from disc images or extracted discs, and writes its logs where a PC can copy them over USB. The MetalFX settings texts are now translated into Japanese, Korean and Simplified Chinese. See the changelog for the full list and earlier releases, including v0.8.6 with the Lunar Palace pillar platform fix (#171), v0.8.5 with the 90/120 FPS battle dialogue fix (#148, #173), the No Random Encounters switch and the Android APK in the release, and v0.8.0 with HDR for every anti-aliasing mode and upscaler, and the development status for validation coverage.

Fullscreen, mixed-DPI displays, broader upscaler coverage, Linux hardware, the tall/ultrawide layout across more hardware, and later-disc progression still need more testing. Current work is tracked in the roadmap and Project board.

SDL-mapped controllers and the keyboard can be used together for player 1. Unmapped joysticks need an SDL controller mapping; see the input reference.

For Ring actions, use the controller's right trigger or R. Rumble is enabled by default; set LO_CONTROLLER_RUMBLE=0 to disable it.

Press F1, or LB+RB on a controller (L1+R1 on PlayStation layouts), to open or close the Debug Menu. The game pauses while it is open. It has three pages: Overview, Teleport and Cheats. This overlay is separate from the normal Settings menu and uses keyboard or controller input, not the mouse.

Overview shows the current map name and ID. It also contains the menu language, Capture render state, Save Anywhere, No Random Encounters, and actions to request a win for the current battle or cancel a pending win request.

To record a rendering problem, select Capture render state, confirm, then close the menu so rendering can continue. The capture collects three frames and creates an archive in captures/ in the background. The status message gives its absolute path: .zip on Windows or .tar.gz on Linux. If archiving fails, the original capture directory remains available. Captures include screenshots, rendering data, shaders and logs; review the contents before sharing.

Save Anywhere enables the original game's System → Save action. Close the Debug Menu and reopen the game's System menu to use it. It does not create a separate quicksave.

No Random Encounters stops random battles while you walk around the field. Story and other scripted battles still happen.

The Teleport page provides a position bookmark, editable X/Y/Z coordinates and step size, and the current map's available points of interest. On the coordinate row, press Enter to select X, Y or Z, then use ←/→ to adjust that axis by the selected step. Confirm the teleport action or a point of interest, then close the menu to move. A scene change clears the bookmark and cancels a pending teleport.

The Cheats page groups its tools into six categories:

Fast-forward works independently of memory editing and currently requires a controller. Choose Hold to accelerate while holding LT, or Toggle to switch acceleration on and off with each LT press. Select a multiplier of 2×, 3×, 4×, 6× or 8×, then close the overlay to use it. Acceleration stops while a menu is open, the window is unfocused or the scene editor is active; LT+RT does not accelerate. Audio is not time-stretched.

Memory editing is off by default. To change game data, first back up your save and enter a controllable scene outside battle. Enable Allow memory edits, choose an action, then confirm Yes. When the status shows a pending change, close F1 to let the action run. Reopen the menu to check the result. A scene change cancels a pending edit.

The menu language, Save Anywhere and No Random Encounters options are written to settings.ini. Fast-forward settings and memory-edit permission reset when the program restarts. Changes to game values can become part of a normal game save.

The Windows ZIP is portable: everything stays in the folder you extracted it to. A Linux build whose own folder is writable, such as a source build or an extracted AppImage, is portable too. The AppImage, the Flatpak and a macOS .app cannot write next to the program, so they keep your files in per-user folders.

On Linux, set XDG_CONFIG_HOME, XDG_DATA_HOME or XDG_STATE_HOME to move the AppImage folders.

On Android, app-private storage is /data/data/io.github.freefrank.lostodyssey/files/, which file managers cannot show. Game data and logs are the exceptions: they live in the app's external files folder, where a PC connected over USB can reach them. The app reads game data from Android/data/io.github.freefrank.lostodyssey/files/game/ on the internal storage or on an SD card (the first one that has game/disc1/default.xex) and writes logs to Android/data/io.github.freefrank.lostodyssey/files/logs/. Since v0.8.7 the Game folder page (shown when no game data is found, and under CTRL → Game folder) can instead point at any folder on the internal storage or an SD card; the game is then looked up there first, and its Import disc images… button imports straight into the device.

How the game is found when --game is not given:

1. The program reads game-path.txt.
2. If that file is absent, it looks for default.xex in the data folder's game/ (per-user packages only).
3. Then it checks game/, the program folder and ../game next to the program.
4. If nothing is found, the importer opens.

The Android app always starts with --game pointing at game/disc1 in the external files folder of the storage that has the game (internal first, then SD cards); the other discs are found beside it. Launching with --game keeps the current working directory. In a portable layout, settings, saves, profiles, cache, logs and captures then follow the folder you start from. In per-user packages only captures/ does.

Options must be spelled exactly. Write --game <path> as two arguments; --game=<path> is ignored, along with any other unknown argument. There is no --help or --version. The updater and restart logic use internal arguments (--apply-plan, --wait-process, --restart-ready, --restart-parent-fd, --restart-ready-fd); do not pass them yourself. LostOdysseyRecomp.exe is a GUI program and prints nothing to a console; check the log instead.

LostOdysseyRecomp.exe --game "D:\Games\Lost Odyssey"
./LostOdysseyRecomp-linux-x64-v0.8.7.AppImage --game ~/Games/LostOdyssey
flatpak run io.github.freefrank.LostOdysseyRecomp --game ~/Games/LostOdyssey
LostOdysseyRecomp.app/Contents/MacOS/LostOdysseyRecomp --game ~/Games/LostOdyssey

Environment variables give more launch options. Each one overrides the saved setting for that run.

Include the exact package or source version, operating system, graphics backend, GPU/driver, game edition and disc, and the steps or scene that reproduce the problem. Attach the complete current logs/runtime-<timestamp>.log; it records startup and graphics details. LO_LOG_FILE=<path> selects another log path, and LO_LOG_FILE=0 disables the duplicate file sink.

For a visual defect, use the capture procedure while the problem is visible. Share the resulting archive only after reviewing it. Do not attach game executables, resource archives, saves or personal data.

Optional diagnostics are off by default and can be disabled in Settings. See Privacy for the data collected and sharing controls.

Ring combat	City exploration

Unmodified screenshots from development builds leading up to v0.1.

See Building for dependencies and build commands, Developer tools for the available utilities, and the documentation index for current references and historical notes.

Thank you to Cristian and Whitesun for supporting the project on Ko-fi.

With research and tools from UnleashedRecomp, re:Blue, XenonRecomp, XenosRecomp, plume and Xenia. Audio uses the pinned Xenia FFmpeg fork, with its license. On Android, the custom Adreno GPU drivers (Mesa Turnip builds) come from the driver list of the Eden emulator and load through libadrenotools.

Lost Odyssey and its assets belong to their respective owners. This is an unofficial project. Supply data extracted from your own discs; do not commit game executables, resource archives, textures, audio, video, generated game code or captures to this repository. Dependencies retain their respective licenses.