ReStreet: FIFA Street (2012) recompiled for Windows PC, with online play, a launcher with friends, chat and rooms. Bring your own game.
Test procedure
The recorded results are in STATUS.md. These steps describe checks for a new build; unchecked steps must not be reported as passed.
Installer
- Use a personal supported Xbox 360 ISO and a new, empty installation folder.
- Record installer version, start/end times, Windows version, CPU, GPU/driver, free space and ISO region/revision.
- Confirm extraction, menu-credit patching and compilation finish successfully.
- Confirm the following files exist:
Game/fifastreet.exeGame/fifastreet_fifadllzf_xex.dllGame/fifastreet_FootballCompEngzf_xex.dll
- Confirm
Game/Backends/D3D12andGame/Backends/Vulkaneach containrexruntime.dllandrexgpu-xenos.dll. - Confirm the initial root runtime/GPU pair corresponds to Direct3D 12.
- Test the optional desktop shortcut and OPEN LAUNCHER.
- Repeat separately on a clean Windows machine to test missing C++ prerequisites.
For cancellation, use a disposable new destination, cancel during extraction/build, and confirm the active child process stops. Partial installation files can remain. Do not reuse that destination as a completed game.
Backend switching
Test both graphics APIs from the same clean installation.
Direct3D 12
- Select Direct3D 12.
- Confirm GPU-adapter selection is enabled.
- Press PLAY.
- Confirm the game starts and renders correctly.
- Record the active root runtime/GPU hashes if validating a release package.
Vulkan
- Select Vulkan.
- Confirm the launcher uses automatic Vulkan device selection.
- Press PLAY.
- Confirm the game starts and renders correctly.
- Confirm the active root runtime/GPU pair has changed to the packaged Vulkan pair.
Switch back to Direct3D 12 and repeat when validating backend switching in both directions.
Resolution testing
Output resolution and internal rendering resolution must be tested separately.
The launcher exposes internal scales:
- 1x — 1280x720
- 2x — 2560x1440
- 3x — 3840x2160
- 4x — 5120x2880
Test output modes supported by the display, including 1280x720, 1920x1080, 2560x1440, 3200x1800 and 3840x2160 where applicable.
Changing output resolution must not implicitly change the selected internal scale.
Record both values in performance reports.
Credits and content checks
The local patch test was run on copies of the original data1.big and data1.bh, using the packaged installer's --credit-test <GameDataFolder> <LogPath> developer entry point. Wait for the process to exit before inspecting the log.
Verification compared all outer archive entries with the original. Only data/ui/game/screens/bootflow/03_pressstart.big and data/ui/game/screens/menus/mainmenu.big changed. Both replacement payloads matched the working game byte for byte, and each companion-index offset/length matched. Running the patch again reported that the credits were already applied.
For a new recipe or ISO revision, repeat those checks with local private files. Do not commit the archives, font, generated code or private test fixtures.
Audit the distributable bundle separately for game ISOs, original XEX files, BIG/BH archives and generated game executables. The presentation images and credit difference recipe are intentional source assets, with their license scope documented.
Launcher and game
- Confirm the start screen and main menu display PORTED BY: SAMUELITODAVILA.
- Confirm Direct3D 12 and Vulkan can each launch the game.
- Confirm the Readback Resolve option is set to Full (the default) unless you are testing another mode.
- Test fullscreen and windowed mode. Minimize/restore repeatedly from the menu and during play.
- Play a complete match. Check controls, sound, transitions and results.
- Enter World Tour and exercise the progression path that previously failed.
- Save, close the game, relaunch and load the saved state.
- Test additional modes/venues and controllers individually. Record unsupported options and reproduction steps.
ReXGlue patch
Before a release, verify the project patch against the recorded ReXGlue base:
git -C ReXGlue apply --check ../patches/rexglue-local-changes.patch
git -C ReXGlue apply ../patches/rexglue-local-changes.patch
The v0.3.0 patch was checked and applied successfully against ReXGlue commit c94f5eb.
Performance reporting
Use a repeatable scene and settings, identify hardware/driver and graphics API, and report output resolution and internal scale separately.
Distinguish a cold shader cache from a warm cache. A screenshot of recent FPS is useful evidence of that moment, not a sustained benchmark.
Do not infer a universal performance guarantee from a single machine. In particular, availability of 3x/4x internal scaling or 4K output does not imply that those combinations maintain 60 FPS.