Fix Rocketship wall damage flash misinterpreted as model scaling
This commit is contained in:
1 parent
b5ef5b8b64
commit
62e908e26d
13 files changed
+255
-21
No files matched your search
@@ -1,5 +1,20 @@
|
||||
# Progress — 2026-11-03
|
||||
|
||||
## Rocketship wall-impact correction
|
||||
|
||||
User Windows testing exposed wild ship scaling on wall hits. The initial port
|
||||
misread first-material RGBA writes as geometry scale. EXE43E76E selects material
|
||||
interface+500;43E78B..43E7A7 writes(1,pulse,pulse,1), and ourDLL10037874..100378FA
|
||||
consumes+4C/+50/+54/+58 as diffuse RGB/alpha. Rocketship now stores ImpactColor;
|
||||
visuals keep unit geometry and tint only the ship material. Driver/Goddard/fire
|
||||
positions, scale and color are independent. Expiry/reset restore white.
|
||||
13 managed groups pass, including two actual static-wall callbacks and per-vertex
|
||||
geometry/color checks over130 frames with repeated renders/expiry. Copied-original
|
||||
numeric fixtures retain their historical raw `scale` label with corrected meaning;
|
||||
Python projections use color and guard the EXE writer/material constructor/DLL
|
||||
consumer. Main build and targeted source/render checks pass. Details, REA evidence
|
||||
and final package verification: [impact report](gameplay/rocketship-impact-render.md).
|
||||
|
||||
## Live VR02 Rocketship
|
||||
|
||||
Implemented owned/reused3ROC flight in VR02: source ceiling/wall/support profile,
|
||||
|
||||
Reference in new issue
Block a user