urt-rs / docs /research /QVM_CONTACT_DISPATCH.md
nmarshall's picture
qvm: contact basis and damage dispatch
73a5d10
|
Raw History Blame Contribute Delete
1.35 kB

Contact direction basis and health-damage dispatch

RE-712. Reproduce with python3 scripts/analyze_qvm_contact_dispatch.py; check with python3 scripts/test_qvm_contact_dispatch.py. The machine report retains source identity and bounded fixtures.

Actual293373–293627 converts attacker pitch/yaw/roll at60/64/68 using word1016003125, invokes six explicitly modeled native sin/cos calls, and stores global forward36477748, right36477736 and up36477724. The complete nine-argument211239 request is target, attacker, attacker, forward pointer, trace point pointer, truncating integer scalar, zero flags, original descriptor4200+432×weapon, location. A nonzero scalar and zero special flag are required; nonzero subunit scalars still dispatch integer0, and explicit negative fixtures dispatch signed negative integers. Signed zero skips dispatch. All paths return the unchanged float scalar. Original nearest-point words supply trace points. Native transcendental parity, earlier contact/event stages and actual211239 health/armor mutations remain open;211239 is captured without effects.

No original executable/full QVM/native collision/physics/rendering executes. Native responses and legal input domains are supplied or unverified where stated; full runtime/macOS/Linux Rust/Bevy/Solari gameplay remains open.