CydandClaude Fable 5
8231bee58c
The [map] audit named it in one run: subsystem 17 = Torso, attribute ids 12/13 unresolved. The donor's decompiled torso.hpp carries the authentic enum with binary offsets -- ids 3..15, including StickPosition(9), TorsoUp/Down/ Left/Right(10-13), TorsoCenter(14), MotionState(15). Our table stopped at seven entries with MotionState at id 9, on the strength of a comment claiming the rest were messages. The streamed control mappings bind BY ID as direct WRITE destinations, so the truncation produced two different crashes from one cause: in TM mode the button ids 12/13 resolved NULL (the boot write-fault the moment the joystick polled), and in RIO mode the analog id 9 resolved to our motionState StateIndicator -- every analog packet from a live vRIO wrote raw floats over a watcher-socketed object, and the corrupted chains walked into unmapped memory ~30-40s later. That was the 'intermittent' pod fault at the fixed DPMI-host address. vRIO down = no analog = no corruption, which is why the norio conf launched: every observation from the whole hunt drops out of this mechanism. Fix: the full 13-entry donor table; five int command members carved from the dynamicsState reserve (class size unchanged); ctor zeros them. Verified, two agreeing runs each way: TM mode launches with a clean audit and the Thrustmaster joystick driving the torso (stickY=0.907 -> torsoElev 0.349); RIO mode with vRIO STREAMING launches, zero faults, weapons cycling. pod_render_rec is no longer poisoned and the norio workaround is obsolete. The audit-before-the-archive-call pattern (BT_MAP_LOG walks the same streamed table CreateStreamedMappings consumes, naming what will not resolve) turned a two-day intermittent-corruption hunt into a one-run lookup. The streamed RES tables are binding contracts on our attribute enums. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
86 lines
3.0 KiB
Plaintext
86 lines
3.0 KiB
Plaintext
# pod_render_norio.conf -- pod_render_rec with the RIO serial port OFF.
|
|
#
|
|
# The emulator log shows a steady stream of serial1 RX OVERRUN errors on
|
|
# the RIO pipe, and controls post their events at HighEventPriority
|
|
# UNCONDITIONALLY (CONTROLS.HPP:250) -- so a chattering RIO port would
|
|
# flood a priority the background pump always serves first, starving the
|
|
# priority-0 renderer events the load gate waits on. This conf tests that
|
|
# by removing the port entirely. Everything else is identical to the rec
|
|
# conf, so a launch here and a hang there isolates the RIO.
|
|
#
|
|
[sdl]
|
|
output=opengl
|
|
# higher,higher not highest: HIGH_PRIORITY_CLASS starved the host desktop;
|
|
# with the retry patches a rare dropout self-recovers (see gauge_rio.conf).
|
|
priority=higher,higher
|
|
[dosbox]
|
|
memsize=32
|
|
machine=svga_s3
|
|
[cpu]
|
|
core=dynamic
|
|
cputype=pentium
|
|
cycles=max
|
|
[sblaster]
|
|
sbtype=sb16
|
|
sbbase=220
|
|
irq=5
|
|
dma=1
|
|
hdma=5
|
|
[mixer]
|
|
# match the EMU8000s' native rate (no resample) and buffer ~60ms so brief
|
|
# emulation-thread stalls (RIO retry recovery) don't audibly chop
|
|
rate=44100
|
|
blocksize=1024
|
|
prebuffer=60
|
|
[serial]
|
|
# RIO on COM1 with the low-latency options (rxpollus/rxburst) so the board's
|
|
# few-ms ACK deadline is met; plasma display on COM2 (real pod has both).
|
|
# VWE fork namedpipe backend (com0com/realport retired -- COM1/COM2 gone):
|
|
# DOSBox = pipe client (retry), vRIO/vPLASMA apps = servers; an unconnected
|
|
# pipe behaves as an unplugged cable so the mission still runs. serialnamedpipe.h
|
|
serial1=disabled
|
|
serial2=namedpipe pipe:vplasma
|
|
# live UNBUFFERED game output: DOS char devices are not buffered, so
|
|
# redirecting stdout to COM3 lands every line immediately. A normal
|
|
# '> file' redirect stays 0 bytes until the process exits, which hides
|
|
# all progress on a run that does NOT crash.
|
|
serial3=file file:C:\VWE\TeslaRel410\emulator\render-bridge\podlog.txt
|
|
[autoexec]
|
|
mount c "C:\VWE\TeslaRel410\ALPHA_1"
|
|
c:
|
|
cd \REL410\BT
|
|
set VIDEOFORMAT=svga
|
|
rem production pod card init (PARAMETR.BAT:181-186): DIAGNOSE + AWEUTIL per
|
|
rem card -- AWEUTIL /S does the EMU8000 bring-up and DRAM detect the HMI SOS
|
|
rem driver relies on; skipping it left the cards uninitialized (silent).
|
|
rem aweutil /s SKIPPED for now: it verifies the AWE32 GM ROM, which the
|
|
rem emulated cards lack (hangs in a retry loop) -- restore once the ROM is
|
|
rem dumped from a real card. diagnose /s kept (passes, sets mixer config).
|
|
set BLASTER=A220 I5 D1 H5 P330 T6
|
|
c:\sb16\diagnose /s
|
|
set BLASTER=A240 I7 D3 H6 P300 T6
|
|
c:\sb16\diagnose /s
|
|
set BLASTER=A220 I5 D1 H5 P330 T6
|
|
set TEMP=c:\
|
|
rem arena1 city mission (TESTARN.EGG: map=arena1, time=day) with the RIO
|
|
rem attached; stdout redirected so mission-load progress survives kills.
|
|
set BT_MECH_LOG=1
|
|
set BT_MAP_LOG=1
|
|
set BT_MER_LOG=1
|
|
set BT_VID_LOG=1
|
|
set BT_LAUNCH_LOG=1
|
|
set BT_STACK_LOG=1
|
|
set BT_FORCE_THROTTLE=0.6
|
|
set BT_FORCE_TURN=0.25
|
|
set HEAPSIZE=15000000
|
|
set L4GAUGE=640x480x16
|
|
call setenv.bat r s n p
|
|
32rtm.exe -x
|
|
BTL4REC.EXE -egg testarn.egg > COM3
|
|
|
|
echo GAME-RC=%errorlevel% >> RC.TXT
|
|
32rtm.exe -u
|
|
echo ALPHA1-RUN-DONE
|
|
pause
|
|
|