Xbox2Windows research shows early static recompilation progress

A fragmented circuit board shaped like a globe, with one half rendered in deep green and black (console architecture) gradually transforming into silver and blue metallic traces (PC architecture), con

A research project called Xbox2Windows has demonstrated early-stage technical progress in statically recompiling components from an Xbox Series X|S (Scarlett) title to x64 Windows. The initiative, led by developer R0Y00, translates selected x64 machine code into C++ and gfx1013 shaders into desktop DXIL. While no full game has been launched, tests confirm that recompiled programs and shaders produce outputs matching reference implementations on both hardware and Microsoft’s WARP software renderer.

The work does not require a full game installation. Instead, it uses source-built executables and synthetic test cases derived from extracted data packages. Verified components include an archive reader using blast 1.3 decompression, which produces identical output across native, mapped, and recompiled versions — matching in callback order, memory allocations, record processing, and exit status.

Shader translation achieves hardware validation

Of 12,101 pixel shader records, 851 have been successfully compiled into desktop DXIL, built into D3D12 pipelines, and validated against controlled outputs on an RTX 4060 Laptop GPU and WARP. Tests include explicit LOD 0 verification and constant-buffer read probes affecting 1,024 pixels across 529 blocked records. Compute shaders (12 of 2,689) passed 14 full-buffer comparisons under varying dispatch group counts. Mesh shaders correctly fetched indexed vertices and rendered matching pixel sets (1,024 and 276 pixels) on a 32×32 target, validated on both hardware and WARP.

AMD GPUs including the RX 6600, RX 6750 XT, RX 6800 XT, RX 9070, RX 9070 XT, and RX 7900 GRE support forced wave64 execution, while NVIDIA adapters (RTX 2060, 3070, 4060, 4060 Ti, 4070 Ti SUPER, 5070, 5080) operate with native 32-lane wavefronts and do not support wave64 in these tests. All tested configurations passed 408 BVH differential queries, indicating consistent ray-tracing pipeline behaviour across vendors.

The project requires DXC 1.8.2502 or newer for shader validation. On Windows 10, the Agility SDK and app-local WARP packages are needed to run BVH and DXR checks.

CPU and runtime translation remains partial

Recompiled x64 programs run from PE entry point to process exit in test fixtures, but the main game executable was absent from the inspected package. Translation covers leaf functions, chained-range calls, cross-function control flow, Bink frame-plane allocations, and Bink group descriptor construction. Memory allocation, deallocation, and exit status are consistent across native and recompiled paths.

However, full-game startup, gameplay logic, and frame rate performance remain unverified. The absence of the primary executable means no conclusions can be drawn about playable functionality.

The Windows runtime successfully routes Bink frame-buffer allocations through the system heap. FidelityFX upscaling experiments confirm correct scratch memory handling through RCAS output on an 8×4 tile. Additional validated components include resource metadata resolution, texture recovery (packed mip tails, BC7 block generation, resident mips), audio metadata parsing (stream counts, codec IDs, sample rates in AWC banks), and script state resolution (parent/child lookups, ambiguous selections).

Community collaboration drives verification

The project is open on GitHub and encourages contributions through structured workflows. Developers can claim tasks, submit focused pull requests, or run GPU checks on their hardware. Over a dozen GPU configurations — including NVIDIA RTX 20, 30, 40, and 50 series and AMD RX 6000, 7000, and 9000 series — have submitted results via issue #1, confirming consistency across drivers and vendors.

Contributors must install Python 3.11+, Visual Studio with the Desktop development with C++ workload (including MSVC, CMake, Ninja, and Windows SDK 10.0.26100), and DXC. The build supports both debug (dev) and release (/O2) presets. Non-Windows developers can participate in platform-independent Python and LLVM 15 checks.

Hardware results are collected via a standalone GPU check script (Run-GpuCheck.ps1), which runs without requiring a compiler, console SDK, or game files. Reports are posted in the hardware coverage thread (#1), not as new issues.

What it means

This research represents a methodical, reverse-engineering effort to enable Xbox-native titles on Windows through static recompilation rather than emulation. For businesses, it illustrates the emerging feasibility of binary translation for complex, closed-source software — particularly in gaming and legacy system migration. While not a playable port, it demonstrates functional fidelity in low-level components, suggesting that full translation may be technically achievable over time.

For developers in the UK, UAE, US, and Kazakhstan, this work offers insights into cross-platform runtime abstraction, shader portability, and memory management across heterogeneous systems. It may inform strategies for multi-platform deployment or long-term software preservation, though legal and technical risks remain high.

The project maintains transparency: every claim is tied to reproducible tests, and limitations are explicitly documented. No game files are distributed; all tests use synthetic or extracted assets. Rockstar Games has not commented on the project.

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *