Download
Windows builds are published as GitHub releases. When a tag is pushed, CI publishes only what passed the Release build and the sample tests.
Latest release
- rePIU-v0.0.225-win32.zip
- openwatcom-samples-v0.0.225.zip
- rePIU-v0.0.225-linux-i386.tar.gz
- rePIU-v0.0.225-linux-x64.tar.gz
What changed in this version
Changes since v0.0.224 (issue #76). The game can be played with the keyboard and gamepads on the web page, with the same key layout as on Windows and Linux. Release builds (Windows, Linux) behave as before.
Resolved issues
| issue | Summary | Commit |
|---|---|---|
| #76 | keyboard and gamepad input on the browser page (the input part of phase 4 unit 2); the issue stays open for the in-game check | 3f4c8e8 |
Changed
Keyboard. Until now the web build had no input, so F5 (COIN1) reloaded the page.
- While the game runs, the page sends keys to the engine, which takes them as a native window's keys, so the layout is
the same: coin
F5, testF1, serviceF2, clearF3, P1QESZC, P2 keypad79513, the OSDTab. - Keys go by the key's position (
KeyboardEvent.code), not the character, so the same key is the same input whatever the keyboard layout. - The browser's default action for game keys is stopped: F5 does not reload and Tab does not move the focus. Ctrl and Meta combinations, F11 (fullscreen) and F12 (developer tools) stay the browser's.
- When the page loses focus or is hidden, every held key is let go of (as a native window does).
- The page lists the keys.
Gamepads. A pad the browser recognises with the standard mapping (most XInput pads) is handed to SDL as a gamepad, so the native pad bindings and chords apply as they are: coin on Back, the OSD on LT+RT+Y, exit on LT+RT+L3+R3. A pad without the standard mapping is not used, and the console says so once.
Verified
| Configuration | Check |
|---|---|
| Browser | in headless Edge, F5 does not reload the page |
| Key name table | core probe browser_key_code (ranges, named keys, every key of the default layout, unknown names): Win32, Linux x64 and i386, web |
Win32 direct Release |
core probe 45/45, pumpitea stops normally after 40 s |
| Linux x64 and i386 Release | core probe 47/47 and 45/45 |
Web (repiu, repiu_browser, repiu_core_probe) |
build; Node core probe 37/37 |
| CI | the Win32 Debug build and probes |
Known
- Whether the coin and the OSD react in the game, and whether gamepads work, has not been checked in a browser yet. On this PC headless browsers' file reads had slowed down and the CHD unpack stalled (the build before this change as well). #76 stays open for the user's check.
- The web build has no sound yet (the next unit).
- On Win32 a GL error is sometimes recorded at pumpitea's first texture upload. v0.0.224 has it too; it is #78.
Getting started
- Unzip the archive into a folder of your choice.
- Create
roms\in that folder and putroms\<set>.zipandroms\<set>\<disc>.chdthere. - Run
repiu.exeto open the launcher. Picking a ROM set starts it in the same window; sets that cannot run are dimmed with the reason. - From a command line, with that folder as the current directory,
repiu.exe pumpit1starts a set directly.
Requirements
- Windows 10/11 (runs as a 32-bit x86 program on a 64-bit OS)
- Legally owned MAME-format PIU ROM ZIP and CHD
Earlier releases
Build from source
For the Linux x64 build and development builds, follow Getting started in the README.
Notice
rePIU is an unofficial project and is not affiliated with the rights holders of the original games. This site and its releases do not include or distribute any ROM, CHD or original executable.