Files
TeslaRel410/emulator
CydandClaude Fable 5 1b204de6d3 BT410: the 3-D path runs to mission load -- btl4vid's next brick is named
Run against the emulated Division card, our build reaches the mission scene
load and stops at the one method we stubbed:

  btl4vid.cpp(42): BTL4VideoRenderer::LoadMissionImplementation
                   -- btl4vid.cpp not yet reconstructed

That proves MakeVideoRenderer, the BTL4VideoRenderer ctor over the engine's
DPLRenderer, the board boot (transputer + i860 firmware, ~858K wire
transactions through the VPX HLE) and Renderer::LoadMission all work in our
build.  btl4vid is not a from-scratch climb; the engine half was always
linked and what is missing is the mission-load hook and its renderables.

Banked the reproduction rig (emulator/vidtest.conf + the host VPX env --
VPX_RESPOND alone is not enough, the iserver handshake dies without
VPX_RENDER), the authentic contract from CODE/RP/MUNGA/RENDERER.CPP:263, and
a note that the BT411 donor restructured this hook so the contract comes from
the 1995 engine and only the renderables come from the donor.

Also corrected today's earlier note: the transient 3-D frame seen during a
gauge run was NOT the dPL path.  MakeVideoRenderer returns NULL without
DPLARG and no gauge conf sets it, so no video renderer exists in those runs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-27 23:32:06 -05:00
..