Files

T

CydandClaude Opus 4.8 7a615449c5 VDB decode SOLVED: six displays bit-packed in the 16bpp pixel

The gauge framebuffer is an encoded stream: each 16bpp pixel packs all six
cockpit displays. Decoded live into per-display windows:
  bits 0-5   = the COLOR radar/tactical display, as 6-bit RGB (2 bits/channel)
  bits 6-7   = mono display 1 (nav scope)
  bits 8-9   = mono display 2 (weapons/systems)
  bits 10-11 = mono display 3 (sensor cluster)
  bits 12-13 = mono display 4
  bits 14-15 = mono display 5
That's 6 + 5x2 = 16 bits exactly -> six displays (1 color + 5 mono), matching
the pod hardware. A 7th window (bits 16-17) confirms the budget: it's black.

Each display now renders in its own 640x480 window from the shared framebuffer
(vga.mem.linear). Mono screens show as brightness; the three VDB palettes are
the per-display color maps (next: apply them).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-03 20:09:36 -05:00

serialport

Phase 3e: live texturing + serial receive-latency fixes for the RIO

2026-07-03 16:43:21 -05:00

README.md

Phase 1 complete: captured VPX boot conversation from shipped binary

2026-07-02 22:46:20 -05:00

vpxlog.cpp

VDB decode SOLVED: six displays bit-packed in the 16bpp pixel

2026-07-03 20:09:36 -05:00

README.md

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 base 0x150, 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 separate vpx.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, append vpxlog.cpp to libhardware_a_SOURCES (we inserted it after glide.cpp).
Call the init — in src/src/gui/sdlmain.cpp, declare void VPXLOG_Init(); next to the other *_Init() prototypes and call VPXLOG_Init(); right after GLIDE_Init(); in the machine bring-up sequence.

Build:

cd emulator/src
./build-mingw-sdl2 --enable-debug=heavy

Output: src/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.