erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs: close #160 (user-verified) - RemoteWeenie run-rate chain fix 41006e79

Browse source
This commit is contained in:
Erik 2026-07-03 16:20:12 +02:00
parent 41006e795a
commit 6870857cc2
1 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/ISSUES.md
View file

@ -48,7 +48,14 @@ Copy this block when adding a new issue:
## #160 — Remote moveto: run animation pace vs actual movement speed mismatch
**Status:** OPEN (2026-07-03, R4-V5 live verify)
**Status:** CLOSED (2026-07-03, `41006e79`, user-verified same session).
**Root cause:** remote interps carried NO weenie, so retail's
apply_run_to_command rate chain (`weenie ? (InqRunRate() ?: my_run_rate)
: 1.0`, raw 305062-305076) took the degenerate 1.0 branch and the wire's
MoveToRunRate (stored in MyRunRate by the mt-6/7 unpack, M13) was never
consumed — run dispatches at speed 1.0 = slow-motion legs + crawl. Fix:
`RemoteWeenie` (retail's per-object ACCWeenieObject stand-in; InqRunRate
fails → my_run_rate fallback) on every RemoteMotion interp.
**Symptom:** observing a retail player's server MoveToChain from acdream:
close-range movetos WALK correctly; at run distance the RUN cycle plays but
the body moves visibly slower than the legs (treadmilling). The legs' pace