DuckStation has shipped a new preview build that exposes additional PlayStation 2 hardware internals to developers and advances cross-backend consistency in the emulator. The update lands directly from project lead Stenzek and is available now through the project’s GitHub releases page (DuckStation Releases).
The most notable change in this preview build is the exposure of the target memory map and registers. For developers working on compatibility hacks or low-level debugging, this means direct visibility into how the emulated PS2 maps memory during runtime. Previously, inspecting these values required invasive workarounds or custom builds; now they are accessible through the standard debugging interface. Stenzek implemented this change directly in the emulator core, giving researchers and modders a clearer view of emulated hardware state without needing to instrument the codebase themselves.
Alongside the memory map changes, the build exposes GTE (Geometry Transform Engine) registers. The GTE handles 3D coordinate transformation, lighting, and matrix operations in PS2 games, making it one of the most complex coprocessors to emulate accurately. Exposing these registers helps developers trace geometric calculations in real time, which is particularly valuable for diagnosing rendering glitches in titles that rely heavily on custom GTE tricks. Games like Shadow of the Colossus and God of War push the GTE to its limits, and this level of access makes it easier to pinpoint where emulation diverges from real hardware behavior.
The third change unifies buffer sizes across rendering backends. DuckStation supports multiple graphics APIs—Vulkan, OpenGL, and software rasterization—and each backend previously managed its own internal buffers. This inconsistency sometimes caused frame pacing differences or audio-video desync when switching between backends. By standardizing buffer sizes, Stenzek reduces those variables, making behavior more predictable regardless of which renderer a user selects. For players who switch between integrated and discrete graphics on laptops, this translates to smoother transitions and fewer manual configuration tweaks.
Users downloading this preview build should verify its authenticity. Because the release is signed through GitHub’s commit verification system, you can confirm that the commits originate from Stenzek’s verified identity by checking the verification status on the release page (GitHub Docs).
For readers interested in how GitHub’s verification workflows support open-source development, our explainer on GitHub’s ‘Harness Is All You Need’ Workflow covers the broader ecosystem.
This is a preview build, not a stable release, so expect occasional crashes or incomplete feature implementations. The changes are targeted at developers and advanced users who need the exposed hardware interfaces for compatibility work or emulator improvement.
