Recover ordered physical pair collision lifecycle
This commit is contained in:
1 parent
27d91ad697
commit
924ad2f67b
17 files changed
+815
-1
No files matched your search
@@ -49,6 +49,12 @@ The broader priority remains Jimmy movement stabilization, with gadgets paused.
|
||||
JN-Engine native/Godot movement. Use its original decompiler index only as leads,
|
||||
verified with REA/authoritative originals. See docs/gameplay/jimmy-movement-stabilization.md.
|
||||
|
||||
Pair continuation: docs/checkpoint/pair-lifecycle.md records28 complete original/
|
||||
C# cases and20 VR04 class bindings. OriginalPairCollision is a bounded component,
|
||||
not live scene admission. Next recover full physical registration/activation and
|
||||
helpers, real actor responses and shared dynamic reclip before replacing existing
|
||||
collision. Gated pairs retain contacts; sphere exclusions use the earlier actor.
|
||||
|
||||
2026-11-06 continuation: the earlier292 original component cases plus50 derived-
|
||||
caller cases and body/visual-sync audit supply no extra reset. Startup diagnostics
|
||||
now observe backgroundLevel1D/Jimmy allocation after an explicit OS repaint
|
||||
|
||||
Reference in new issue
Block a user