Skip to content

Blinx 0.5.2-xbe.1 — Experimental XBE compatibility test

Pre-release
Pre-release

Choose a tag to compare

@mstan mstan released this 05 Nov 19:27

Experimental Windows test for Blinx disc rips that 0.5.1 reports as Unsupported XBE Revision.

This prerelease attempts other Blinx XBEs and collects diagnostics automatically. It is based on 0.5.1; compatibility with a different executable is unverified. The stable release remains 0.5.1.

  1. Download BlinxRecomp-windows-x64-0.5.2-xbe.1.zip and extract it into a separate folder.
  2. Open Start Game.exe, choose Skip for console setup, and select your ISO/XISO or extracted default.xbe normally.
  3. An unknown Blinx executable shows Experimental XBE - unverified. Start it and note whether it reaches the title screen and gameplay.
  4. If it stops, use Copy diagnostic ZIP or Open report folder in the report window and attach that ZIP. After a normal exit, the report location is shown. Reports are under data/diagnostics/crash-reports.

No PowerShell commands are needed. The ZIP reports the actual XBE hash, public header metadata, section/layout differences, selected mods and runtime failure information. Original game files, console keys, saves and private paths are excluded.

Unknown XBEs use separate test saves. Normal saves, external save folders and HDD images are preserved and are not used by experimental attempts. Fresh graphics settings retain adaptive Fit to screen.

Validation: 73 relevant automated tests passed. The packaged launcher accepts the experimental same-title input and retains strict/wrong-game rejection. A deliberately header-modified owned XBE reached New Game and first-stage gameplay in adaptive 16:9; diagnostic ZIP contents and packaged file hashes were verified. This does not establish that the reported a5885cf7... XBE works; its returned report is needed.

This remains an early beta, with regular playtesting through World 2 and no end-to-end completion guarantee. Windows x64 only for this experiment. Matching project/framework source, prepared dependency source and SHA-256 checksums accompany the download.