vwemirror/BT411
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

#124: hit-location ASPECT was rotated 180 degrees -- the resolver now speaks the 1995 frame

Browse Source 
Night-10's systematic targeting audit (rear panels unhittable from
direct fire, Owens left torso hitting the RIGHT weapon pod and vice
versa, missiles favoring the far side) measured down to one geometric
fact: the authored wedge ring puts the Front* cells in the +Z arc
(slice-name audit, bit-verified tables), i.e. the 1995 resolver frame
has mech-forward = +Z -- while OUR engine's entity frame carries
forward along -Z. Bench proof: a victim facing its attacker took
frontal beams at local z = -4..-10, theta ~270 deg, resolving the
REAR-named cells (zones 12/14/15) every time.

The two frames differ by a pi ROTATION about Y -- rotation, not
reflection, because the field flank observations CROSS (left->right)
rather than persist. ResolveHit now rotates the local impact into the
cylinder's frame (negate x and z; y untouched; handedness preserved so
the SelectSlice torso-twist add keeps its sign).

A/B (172 resolves, live missiles+beams on a facing victim): before
theta~4.7 -> rear zones only; after theta~1.42-1.59 -> utorso/dtorso/
ltorso/rtorso/arm -- the front-authored cells, with the per-burst
re-roll scatter intact.

NOT this bug: the "one band LOW" Y-axis half of the night-10 table --
that is #16 (pick-ray boresight parallax, code-confirmed, still open).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Joe DiPrima
2026-08-03 01:12:32 -05:00
co-authored by Claude Fable 5
parent 788031bc36
commit c5dfb002f3
2 changed files with 29 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
context/combat-damage.md
+10
View File
@@ -1012,6 +1012,16 @@ code involved; grammar = the binary ctors @0x49ea48/@0x49e5e4). Results:
"Right*", W1/W2 = "Front*" -- with theta = atan2(z,x) from +X toward +Z, the
mech-local FRONT is the **+Z arc (theta 45-135 deg)** and dead-ahead is the
W1|W2 SEAM. (Corrects the earlier #92 comment that put frontal hits in W6.)
* **⚠ PORT FRAME ADAPTER (#124, fixed 2026-08-03)**: that +Z-forward is the
**1995 resolver frame**. OUR engine's entity frame carries forward along
**−Z** (bench-measured: a victim facing its attacker took frontal beams at
local z=−4..−10, θ≈270°, resolving the REAR-named cells — which was the whole
night-10 field table: rear panels unhittable, Owens flanks CROSSED). The
frames differ by a **π rotation about Y** (rotation, not reflection — the
flank observations cross rather than persist), so `ResolveHit` negates
local x and z after `WorldToLocal` before the band/wedge math. A/B verified:
frontal fire θ≈1.5 → utorso/dtorso/ltorso/rtorso, zero rear zones. The
separate "one band LOW" Y-signature is #16 (pick-ray parallax), not this.
Frontal unaimed foot-band hits therefore straddle the RightFoot/LeftFoot
cells by impact-x sign, and the authored cross-bleed (20% opposite foot,
10+10% opposite leg) is a data-true source of "hit the opposite leg" reports.