Skip to content

Releases

DOSBox-X Virtuality SU2000 with WebXR headset play (2026-10-15)

Choose a tag to compare

@LeonG-ZA LeonG-ZA released this 15 Oct 19:35

Experimental DOSBox-X build that emulates the Virtuality SU2000 VR arcade machine (Dactyl Nightmare, Dactyl Nightmare 2, Boxing, Ghost Train, Pac-Man VR, Missile Command VR, Shoot for Loot, ...) and lets you play it in a modern VR headset through a web page.

Windows x64 build of the su2000 branch. No game data is included: you need your own SU2000 hard-disk image (see "Game files" below).

Start it from the su2000 folder, which holds the configs and documentation:

cd su2000
..\dosbox-x.exe -conf dosbox-su2000-solo.conf     (Solo cabinet disk: DAC, Pac-Man VR, Missile Command, ...)
..\dosbox-x.exe -conf dosbox-su2000.conf          (two-player cabinet disk: DN2, Boxing, Ghost Train, ...)

Both configs already serve the headset page on port 8090.

Playing in VR: the WebXR page

DOSBox-X has a small built-in web server. When [su2000] vr port is set, it serves a page that a headset's web browser opens. The page shows the SU2000 picture in your headset, plays the game's sound and sends your head, hands, buttons and microphone back to the emulator. To the game, the headset is the cabinet: it stands in for the Visette (the original head-mounted display), the InsideTrak head and hand trackers, the hand controller and the cabinet microphone.

Why a web page instead of a native VR driver

  • Nothing to install on the headset, nothing VR-specific inside DOSBox-X. A Quest (or any headset with a WebXR browser) just opens a URL over Wi-Fi. PC headsets work through desktop Chrome or Edge, which talk to whatever OpenXR runtime is active (SteamVR, Oculus/Meta, Virtual Desktop). DOSBox-X links no headset SDK or runtime, so the same build works with every headset that has a WebXR browser, and the emulator stays portable.
  • The game runs at its own speed; the headset still feels smooth. The SU2000 drew around 25-50 frames per second, while headsets refresh at 72-120 Hz and make people sick if the picture lags behind their head. The page draws each emulator frame on a large virtual screen in front of you, placed where your head pointed when the frame was taken, and the headset redraws it at its own refresh rate as you turn. Head turns between game frames are therefore smooth (the same idea as a headset's own "time-warp"), and head roll keeps the horizon level, as the original Visette did.
  • The original picture is tiny, so streaming it is cheap. Each eye is 352x250 pixels. Sending that over the local network costs little, and the PC does all of the emulation work while the headset only displays the picture.
  • Two people can play. On a two-player cabinet each player opens the page in their own headset and picks player 1 or 2. Each gets their own picture and sound and drives their own trackers and buttons. Linked cabinets (several DOSBox-X instances on the network) work the same way, one headset each.

How it works

  • Connection. WebXR only runs on localhost or over https, so the server answers http and https on the same port. For https it creates a self-signed certificate (su2000vr.crt / su2000vr.key) on first start. Accept the browser's warning once.
  • Control and fallback: a WebSocket carries the player choice, recentring and connection set-up.
  • Low latency: a WebRTC data channel (UDP; unordered, no retransmissions) carries head and hand poses, game sound, microphone and the still-image video. A late packet is skipped instead of holding up the ones behind it.
  • Video:
    • With Cisco's OpenH264 library next to DOSBox-X and a browser with WebCodecs, the picture streams as H.264. The two eyes alternate in one stream, so each eye is also predicted from the other, which saves about a third of the data. That's about 1-4 Mbit/s for both eyes instead of 10-60 Mbit/s for still images.
    • Without the library, each frame is sent as PNG or JPEG, whichever is smaller.
    • The picture is cut to the real screen width that the game sets.
  • Stereo. With stereo = true a second, shifted copy of the graphics boards renders a real right-eye image (it doubles the graphics work).
  • Sound. Game audio is sent at 48 kHz in 10 ms packets. On a two-player cabinet each headset hears only its own player's sound card. The microphone goes to the game (whose cabinet microphone input it replaces) and to the other player's headset.
  • Without a headset the page shows both eyes side by side: a handy preview.

Setting it up

[su2000]
enable = true
vr port = 8090
stereo = true        # optional: real right-eye picture
  1. Optional, for H.264 video: download openh264-2.4.1-win64.dll.bz2 from http://ciscobinary.openh264.org/, unpack it and put the DLL next to dosbox-x.exe. Cisco's own binary carries the H.264 patent licence, which is why it is not bundled.
  2. Start DOSBox-X with one of the SU2000 configs (they already set vr port = 8090). The log lists the addresses the page is served on.
  3. In the headset's browser open https://<PC address>:8090/. Accept the certificate warning once. Then press Enter VR. Allow DOSBox-X through the Windows firewall if asked.
    • PC headset: open http://localhost:8090/ in Chrome or Edge on the PC.
    • Quest over USB: run adb reverse tcp:8090 tcp:8090, then open http://localhost:8090/.
  4. Add credits on the PC with c.
Headset Game
head head tracker
controller hand tracker (gun / glove)
trigger fire / select
grip or A/X walk / second button
B/Y recentre
thumbstick up/down size of the virtual screen

Page options in the URL: player=1|2 picks the player, fov= sets the screen size, video=0 forces still images, rtc=0 uses the WebSocket only, and swap=1 swaps the eyes (a diagnostic).

What else is in this build

  • PIX 1000 graphics: both Motorola 88110 CPUs of each board run the games' own firmware (low-level emulation), several boards per picture, plus a stereo right-eye board pair.
  • Hardware the games talk to:
    • InsideTrak trackers, with the game's own alignment and sensor set-up applied.
    • The format/control cards: buttons, credits, lamps, microphone level.
    • Up to two Soundscape cards.
    • The SMC 8013 network card, linked between DOSBox-X instances over UDP ([su2000] network = relay:<port> on one, <host>:<port> on the others).
  • Tested:
    • Dactyl Nightmare linked between two pods, each player seeing the other.
    • Dactyl Nightmare 2 with two headsets on one two-player cabinet.
    • Boxing, Ghost Train, Pac-Man VR, Missile Command VR and Shoot for Loot run.
  • Games without their CDs: the CDs only hold the music and a copy-protection check. The undocumented Virtuality option /n skips the check: pac /n /cd- /solo, miss /n, sfl /n /vcc.

Game files

The SU2000 software is not part of this release and is not distributed. The configs expect your own hard-disk image unpacked under su2000/data/work/ (simon/ for the Solo cabinet disk, c/ for the two-player disk). See su2000/README.md.

Known limitations

  • Not covered:
    • The Linux build of the VR link (https, WebRTC, H.264) has not been compiled yet.
    • Four linked cabinets connect but have not been seen in one four-player match yet.
  • Calibration: hand position in games other than Dactyl Nightmare is mapped from the controller with an uncalibrated scale.
  • Test aid: SU2K_P2_FOLLOWS_P1=1 (environment variable) makes player 2 copy player 1. It only exists for testing with one person.
  • Microphone: the other player's voice plays centred rather than placed in 3D.

DOSBox-X Rendition Vérité (2026-10-15)

Choose a tag to compare

@LeonG-ZA LeonG-ZA released this 15 Oct 19:05

Experimental DOSBox-X build with emulation of the Rendition Vérité V1000 (the chip on the Creative 3D Blaster PCI and similar boards), including support for Creative CGL games.

Windows x64 build of the verite branch. Unzip and run dosbox-x.exe. Documentation is included (Rendition-Verite.md, Rendition-Verite-CGL-loader.md).

Configuration

Required

[dosbox]
machine=svga_verite

That is the only setting you need. The emulated card is a PCI Rendition Vérité V1000. It works for Rendition-native games (such as vQuake and the Speedy3D/RRedline titles) and for Creative CGL games.

Recommended for 3D games

[dosbox]
memsize=32

[cpu]
core=dynamic
cputype=pentium
cycles=max

[verite] section (all optional)

Setting Default Description
verite_irq 11 The card's IRQ, used for vertical retrace, RISC and DMA interrupts. 0 turns interrupts off. Battle Race needs an IRQ below 8 when verite_cgl=native (5 works).
verite_cgl native How Creative CGL games run (see below).
verite_bios (empty) Path to a dump of your own Vérité board's BIOS ROM (up to 128 KB). The board's RISC sees it at its ROM address, as on the real card. Not needed: without a dump, DOSBox-X provides its own loader.
verite_risc_mhz 25 Clock rate of the emulated RISC in MHz.
verite_debug false Logs mode changes and RISC statistics.
verite_trace 0 Logs this many host accesses to the card (I/O and PCI configuration) and RISC control-register accesses, for troubleshooting.

CGL modes (verite_cgl)

  • native (default): the game's own Vérité CGL driver module (VRIT*.CGL) runs its microcode on the emulated RISC and pixel engine. Most accurate.
  • hle: DOSBox-X answers the module's calls itself and draws on the host. Faster; a useful fallback.

Tested in both modes: Rebel Moon, Hi-Octane, Battle Arena Toshinden, Flight Unlimited, Screamer 2, Screamer Rally, UEFA Euro 96, Actua Soccer and Battle Race.

Example config

[dosbox]
machine=svga_verite
memsize=32

[cpu]
core=dynamic
cputype=pentium
cycles=max

[verite]
verite_cgl=native
verite_irq=5

Per-game notes

  • Battle Arena Toshinden needs a CD image of the original disc, audio tracks included. Without them it reports "NO CD DETECTED" and allows only network play.
  • Actua Soccer's installer needs fixed cycles (for example cycles=fixed 20000) to avoid a "Divide error".

This is an unofficial, experimental build; please report problems in the discussion.

DOSBox-X PowerVR PCX1/PCX2 (2026-10-15)

Pre-release

Choose a tag to compare

@LeonG-ZA LeonG-ZA released this 15 Oct 19:37
d2d2463

Experimental DOSBox-X build with emulation of the PowerVR Series 1 3D accelerators (NEC/VideoLogic PCX1 and PCX2), as used by PowerSGL and Direct3D games on boards such as the VideoLogic Apocalypse 3D/3Dx and Matrox m3D.

The card is emulated entirely in software on the host CPU, using tile-based deferred rendering like the real hardware, with no OpenGL or Direct3D. It is based on Imagination Technologies' MIT-licensed PowerVR-Series1 source code. See docs/PowerVR-PCX.md for design notes and known limitations.

Windows x64 build of the powersgl branch. Unzip it and run dosbox-x.exe.

Configuration

Required

[dosbox]
machine=svga_s3

[powervr]
powervr_card=pcx1
  • machine must be a VESA 2.0 SVGA card such as svga_s3. The PowerVR card has no video output of its own; it renders into the VGA card's linear frame buffer.
  • powervr_card turns the card on. Choose pcx1 or pcx2 (see below).
  • The PCI bus must be on. It is by default ([pci] enable pci bus=true).

Which card to choose

Value Card Use for
pcx1 PCX1 (Apocalypse 3D and other 1996 boards) DOS PowerSGL games built for PCX1, such as Tomb Raider's tombpcx1.exe
pcx2 PCX2 (Apocalypse 3Dx, Matrox m3D). Adds bilinear filtering and floating-point parameters Windows 95/98 with the VideoLogic/Matrox PCX2 driver installed, and games built for PCX2

[powervr] section

Setting Default Description
powervr_card false false, pcx1 or pcx2.
powervr_irq 11 IRQ for the end-of-render interrupt. Pick one no other device uses. 0 turns the interrupt off, and the driver then polls.
powervr_threads 0 Number of host CPU threads used to render frames. 0 means one per CPU core, up to 8.
powervr_debug false Logs register accesses, frame statistics and render times, and saves renders joncampbell123#60 and joncampbell123#600 to pvrdump_NNNN.bin. Use it for troubleshooting only: it slows emulation down.

Recommended for Windows 9x games

PowerSGL and Direct3D games do much of their geometry work with x87 floating-point code. By default, the dynamic core hands that code to the much slower normal core. To keep it on the dynamic core:

[cpu]
core=dynamic
cputype=pentium
cycles=max
use dynamic core with fpu=true

With this setting, MechWarrior 2 PowerVR Edition went from about 6 to about 35 fps. The option is use dynamic core with fpu, not fpu=true. It can upset FPU task switching in Windows 9x, so only turn it on for games that need it.

Example configs

DOS (Tomb Raider PCX1):

[dosbox]
machine=svga_s3
memsize=32

[cpu]
core=dynamic
cputype=pentium
cycles=max

[powervr]
powervr_card=pcx1

Windows 98 (PCX2 driver):

[dosbox]
machine=svga_s3
memsize=64

[cpu]
core=dynamic
cputype=pentium
cycles=max
use dynamic core with fpu=true

[powervr]
powervr_card=pcx2
powervr_irq=11

Tested

  • Tomb Raider (DOS, PCX1): menu, demo and gameplay.
  • POD (Windows 98, PCX2 driver).
  • MechWarrior 2 PowerVR Edition (Windows 98, PCX2 driver).

Not yet tested: Actua Club Soccer, Flight Unlimited and other PowerSGL titles.

This is an unofficial, experimental build. Please report problems in the discussion, and attach the log and pvrdump_*.bin files from a run with powervr_debug=true.

DOSBox-X ATI 3D Rage preview 1

Pre-release

Choose a tag to compare

@LeonG-ZA LeonG-ZA released this 15 Oct 19:06

Preview build of DOSBox-X with ATI 3D Rage / 3D Rage II (Mach64 GT / GT-B) emulation, including the 3D engine (software rasterised on the CPU). Windows x64 build of branch ati-rage-3dcif.

Configuration

[dosbox]
machine=svga_ati_3drage    # 3D Rage (Mach64 GT); or svga_ati_3drage2 for the 3D Rage II (GT-B)
memsize=128                # guest RAM in MB; 64 or more recommended for Windows 98
vmemsize=4                 # video memory in MB (2 or 4; 4 recommended for 3D games)

[cpu]
core=normal                # recommended: the dynamic core makes Windows 98 unstable
cputype=pentium_mmx
cycles=max

[voodoo]
voodoo_card=false          # avoid a second 3D card competing for Direct3D/Glide

Optional display settings: output=surface, scaler=none, aspect=false.

Which machine type to use

  • svga_ati_3drage: the original 3D Rage. For ATI3DCIF games (Assault Rigs, Wipeout, MechWarrior 2 ATI edition, POD) and Direct3D through ATI's driver (MechWarrior 2 Titanium).
  • svga_ati_3drage2: the 3D Rage II. Needed by titles written for it, such as Time Warriors' ATI Rage build (adds the Rage II texture palette and 2D engine extensions).

Guest setup

  • Windows 95 or 98 with ATI's Mach64/Rage display driver (Windows' built-in Mach64 driver gives 2D only).
  • Games need ATI's ATI3DCIF.DLL (usually shipped with the ATI edition of the game), or DirectX for Direct3D titles.

Tested

Time Warriors (3D Rage II), Assault Rigs, Wipeout, POD, MechWarrior 2 ATI edition and MechWarrior 2 Titanium (Direct3D) run and render correctly.

Known issues

  • The dynamic CPU core can hang or misrender (Time Warriors, Assault Rigs) and makes Windows 98 unstable; use core=normal.
  • MechWarrior 2 ATI edition: the ground texture "swims" slightly while walking. This comes from ATI3DCIF's per-triangle perspective approximation and is expected on this chip.
  • Assault Rigs: a few stale pixels can remain at the left and right screen borders.

Notes

  • 3D rendering is done in software, so cycles=max and a fast host CPU help.
  • This build contains debug-only test hooks controlled by DOSBOX_X_M64… environment variables; they do nothing unless those variables are set.
  • Preview quality: not yet submitted upstream.