CydandClaude Opus 4.8
e75913b5d3
Refine the display decode for pairing: window 0 renders the color radar from bits 0-7 (3:3:2 RGB); windows 1-8 each render a single bit (8..15) as white/black. Each bit turns out to be a recognizable display plane -- e.g. bits 8 & 12 are both the weapons panel, bits 9/11/13 the systems panel -- so the mono displays' 2-bit fields are scattered (out of order) across the word. This fan-out lets the bits be re-paired into their six displays by eye. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
VPX device — DOSBox-X integration
Our original source for the emulated Division VPX link adapter. Kept here under
version control because the DOSBox-X source tree itself
(emulator/src/, ~490 MB) is git-ignored.
vpxlog.cpp— Phase 1 logging device. Impersonates the INMOS C012 link adapter at I/O base0x150, answers status reads so the game keeps transmitting, and logs every access to$VPXLOG. (Phase 2 will grow this into a responding transputer-monitor + i860-loader + frame-stream renderer, or fork into a separatevpx.cpp.)
Applying to a DOSBox-X source checkout
Tested against DOSBox-X v2026.06.02, MSYS2 mingw64.
- Copy the device in:
cp emulator/vpx-device/vpxlog.cpp emulator/src/src/hardware/vpxlog.cpp - Add it to the hardware build — in
src/src/hardware/Makefile.am, appendvpxlog.cpptolibhardware_a_SOURCES(we inserted it afterglide.cpp). - Call the init — in
src/src/gui/sdlmain.cpp, declarevoid VPXLOG_Init();next to the other*_Init()prototypes and callVPXLOG_Init();right afterGLIDE_Init();in the machine bring-up sequence. - Build:
Output:
cd emulator/src ./build-mingw-sdl2 --enable-debug=heavysrc/src/dosbox-x.exe.
Running
set VPXLOG=C:\VWE\TeslaRel410\emulator\vpxlog.txt
emulator\src\src\dosbox-x.exe -conf emulator\capture.conf
python emulator\analyze_capture.py
With VPXLOG unset the device is inert and the build behaves like stock
DOSBox-X.