Fix Rocketship wall damage flash misinterpreted as model scaling

This commit is contained in:
UnixNight committed 2026-11-03 16:53:56 -05:00
1 parent b5ef5b8b64
commit 62e908e26d
13 files changed
+255 -21

No files matched your search

+8 -1
View File
@@ -47,7 +47,14 @@ Sound197 is ordinary wall hit. All three are PCM in the existing sound bank.
Ordinary wall impact starts duration1 and E84, ED0=false.43E6E8 adds dt and tests
the unrounded sum **strictly greater** than duration. Equality still pulses;
expiry restores DRIVE/scale1. Shape-only scale is(1,s,s), s=(sin(time*20)+1)/2.
expiry restores DRIVE and white material. The first material RGBA is(1,s,s,1),
s=(sin(time*20)+1)/2: a red damage flash. The initial port/report misidentified
this as shape scaling; corrected after the user's wall-impact bug report.
EXE43E76E selects material interface+500;43E78B..43E7A7 writes+4C..58.
OurDLL1003787C..100378F6 consumes those fields as ARGB diffuse. See
[impact-render proof and regression](rocketship-impact-render.md). Original
probe fixture/log retains its historical `scale` field label for provenance;
the numeric values are valid but do not establish geometry deformation.
Strong ED0 queuesY−700; EC0 burst separately queues−750, excluded from ordinary
VR02. Eight copied-original suffix cases in impact-probe/wine.log verify strict
expiry/pulse/queued impulses, including a float-store equality whose unrounded