test(physics): harden TS-4 production chronology
This commit is contained in:
Erik
parent
75b6f6b6c9
commit
d3c0d9ec0e
5 changed files with 807 additions and 101 deletions
|
|
@ -241,7 +241,7 @@ AP-94..AP-112 for the confirmed retail-UI completion gaps.
|
|||
| # | Divergence | Where (file:line) | Why it is safe / justified | Risk if assumption breaks | Retail oracle |
|
||||
|---|---|---|---|---|---|
|
||||
| ~~TS-1~~ | **RETIRED 2026-07-30 (Campaign P Slice P2) — the row was stale, not the code.** The cited `:1254` line is unrelated stepping-loop code; the file moved substantially since the row was written. Retail's `EdgeSlide → PrecipiceSlide / CliffSlide` chain is already a real, tested port: `SpherePath.PrecipiceSlide` (`TransitionTypes.cs:943-970`, retail `SPHEREPATH::precipice_slide` pc:274316), `Transition.CliffSlide` (`:2080-2164`, retail `CTransition::cliff_slide` pc:272397, return-value mapping verified against `acclient.h:6100-6108`), and `Transition.EdgeSlideAfterStepDownFailed` (`:1907-2078`, mirrors `CTransition::edge_slide` pc:273001-273090). The one real gap (back-probe fallback skipping retail's `walkable_check_pos`/`localspace_sphere` recache, pc:274318-274326) needed no code change: acdream's `WalkableVertices`/`GlobalSphere` are populated in unified world space at assignment time (`SetWalkable`/`SetWalkableTransformed`, `SetCheckPos`/`RestoreCheckPos`), so both operands `BSPQuery.FindCrossedEdge` compares are already commensurable — retail's per-cell local-frame reprojection is a no-op correction here. Documented in-code at the back-probe site and pinned by `EdgeSlideBackProbePrecipiceSlideTests`. The chain's two acdream-only compensating branches (CliffSlide's three-source reference-normal fallback; the walkable-steepness reroute to CliffSlide before PrecipiceSlide) are real, non-retail additions — filed as AD-53 / AD-54 rather than folded into this row. | `src/AcDream.Core/Physics/TransitionTypes.cs` (`SpherePath.PrecipiceSlide`, `Transition.CliffSlide`, `Transition.EdgeSlideAfterStepDownFailed`); `tests/AcDream.Core.Tests/Physics/EdgeSlideBackProbePrecipiceSlideTests.cs` | — | — | `SPHEREPATH::precipice_slide` pc:274316 (0050cc80); `CTransition::cliff_slide` pc:272397 (0050a6d0); `CTransition::edge_slide` pc:273001-273090 (0050b3d0); `SPHEREPATH::get_walkable_pos`/`cache_localspace_sphere`/`set_walkable_check_pos` pc:274318-274326 (0050a8f0/0050c9d0/00509ce0); `docs/research/2026-07-30-response-layer-edge-family-pseudocode.md` §2, §6 Step 1 |
|
||||
| ~~TS-4~~ | **RETIRED 2026-07-31 (Campaign P Slice 2B).** The graph and prepared-flat Path-6 implementations now match retail's exact two-sphere split: every primary/foot polygon hit calls `SetCollide`, sets `WalkableAllowance=LandingZ`, and returns `Adjusted`; only a secondary/head hit writes `CollisionNormal` and returns `Collided`. The steep tangent shortcut and both BSP-layer `SetSlidingNormal` writes are deleted. Exact site tests pin all changed and preserved fields plus raw-bit graph/flat parity. Production-shaped multi-frame vertical/inward/tangential/uphill/downhill roof/wall/ledge traces carry accepted body state between frames, match graph/flat by raw result/body bits, reject penetration and uphill launch/bounce, and pass the complete historical collision matrix without compensation. | `src/AcDream.Core/Physics/BSPQuery.cs`; `src/AcDream.Core/Physics/FlatBspQuery.cs`; `tests/AcDream.Core.Tests/Physics/Ts4Path6ConformanceTests.cs`; `tests/AcDream.Core.Tests/Physics/RetailEdgeResponseOrderingTests.cs`; `tests/AcDream.Core.Tests/Physics/Ts4SteepRoofWedgeCaptureTests.cs` | — | — | `BSPTREE::find_collisions` 0x0053A440: head `0x0053A793..0x0053A7A4`, foot `0x0053A7B3..0x0053A7DC`; research §10 |
|
||||
| ~~TS-4~~ | **RETIRED 2026-07-31 (Campaign P Slice 2B; corrective acceptance complete).** The graph and prepared-flat Path-6 implementations now match retail's exact two-sphere split: every primary/foot polygon hit calls `SetCollide`, sets `WalkableAllowance=LandingZ`, and returns `Adjusted`; only a secondary/head hit writes `CollisionNormal` and returns `Collided`. The steep tangent shortcut and every BSP-layer `SetSlidingNormal` write are deleted. Exact site tests pin all changed and preserved fields plus raw-bit graph/flat parity. A corrective 90-tick already-airborne, zero-root-motion Core suite executes acceleration, body integration, transition resolution, exact commit, and `handle_all_collisions` while retaining every behavior-bearing collision/body field used by that specialized quantum. Vertical, inward, tangential, downhill, and positive-Z uphill-jump traces match graph/flat by raw bits, reject penetration/fixed points/second launches, and pin exact terminal velocity, contact, sliding, and contact-plane state. The older resolver-only capture is explicitly historical and restored to its three-second bound. | `src/AcDream.Core/Physics/BSPQuery.cs`; `src/AcDream.Core/Physics/FlatBspQuery.cs`; `tests/AcDream.Core.Tests/Physics/Ts4Path6ConformanceTests.cs`; `tests/AcDream.Core.Tests/Physics/Ts4ProductionQuantumConformanceTests.cs`; `tests/AcDream.Core.Tests/Physics/Ts4SteepRoofWedgeCaptureTests.cs` | — | — | `BSPTREE::find_collisions` 0x0053A440: head `0x0053A793..0x0053A7A4`, foot `0x0053A7B3..0x0053A7DC`; research §10 |
|
||||
| TS-6 | Weather particle emission suppressed — all weathery DayGroups map to Overcast (correct fog/cloud tone, no precipitation); retail's camera-attached weather subsystem not yet located in the decomp | `src/AcDream.Core/World/WeatherState.cs:200` | Decomp research verified the sky loop never reads `DefaultPesObjectId`; an earlier name-based rain spawn regressed (rained where retail didn't, 2026-04-23) — inventing a name→rain path is forbidden until the real subsystem is found | Rainy/snowy/stormy days never show retail's precipitation effects (permanent missing visuals until the subsystem is found and ported) | FUN_00508010 / FUN_0051bed0→FUN_0051bfb0 (negative findings) |
|
||||
| TS-7 | SkyObject `weather_enabled` gate not honored — weather-flagged sky objects (bit 0x04) always instantiate | `src/AcDream.Core/World/SkyDescLoader.cs:50` | No weather_enabled toggle exists yet; IsWeather flag parsed + documented as the gate to wire | Weather-only sky meshes (rain cylinders) appear where retail-with-weather-off suppresses them | `GameSky::MakeObject` 0x00506ee0, guard at decomp:268630 |
|
||||
| ~~TS-8~~ | **RETIRED 2026-07-31 (#268 stat-chain closeout).** `EnchantmentWireReader` parses the complete 0x02C2 payload and `GameEventWiring` publishes its StatMod type/key/value and bucket through the same `ActiveEnchantmentRecord` used at login. An end-to-end dispatch test proves a mid-session skill modifier changes `LocalPlayerState.GetEffectiveSkill` immediately. | `src/AcDream.Core.Net/Messages/EnchantmentWireReader.cs`; `src/AcDream.Core.Net/GameEventWiring.cs`; `tests/AcDream.Core.Net.Tests/GameEventWiringTests.cs` | — | — | `CEnchantmentRegistry::EnchantAttribute @ 0x00594570`; `CEnchantmentRegistry::EnchantSkill @ 0x005947B0`; holtburger `messages/magic/types.rs` |
|
||||
|
|
@ -306,12 +306,11 @@ phase-gated — they carry their trigger in their row and should land
|
|||
WITH that phase, not before.
|
||||
|
||||
1. **TS-27 — INBOUND retransmit handling** — the outbound sent-packet cache + resend landed with Campaign N Slice N1 (2026-07-29, class-doc gap list fixed same commit); the inbound sequence-aligned ISAAC + client NAK emission (N2/N4) remain the hard blocker for non-loopback play — one lost S2C packet still deafens the session permanently.
|
||||
2. **TS-4 — Path-6 steep slide-tangent shortcut** — landing/contact state diverges on every airborne-steep hit; the L.5+ retail-strict followup is already filed with the missing-ingredient analysis.
|
||||
3. **UN-1 — CheckOtherCells iteration order** — behavior-bearing halt order with a log-cosmetics justification; trivial to fix (iterate CELLARRAY build order, sort only in probe output).
|
||||
4. **UN-6 — 200 ms ConnectResponse sleep** — unexplained constant on every login with an intermittent-failure shape; either find the ACE race and cite it, or replace with an acknowledged-ready check.
|
||||
5. **UN-4 — GfxObj sides/negative-surface logic** — diagnose against the retail-cited CellStruct interpretation on a known double-sided GfxObj; promote to AP with a citation or align it.
|
||||
6. **TS-55 — AdminEnvirons fog/radar presentation** — exact retail mechanism is known; port the authored ambient/fog fields, radar blanking, Clear, and `0x270F` together.
|
||||
7. **TS-19 — Legacy ChaseCamera deletion** — already marked "pending the follow-up deletion commit"; its continued existence can mask or manufacture flap symptoms during debugging.
|
||||
2. **UN-1 — CheckOtherCells iteration order** — behavior-bearing halt order with a log-cosmetics justification; trivial to fix (iterate CELLARRAY build order, sort only in probe output).
|
||||
3. **UN-6 — 200 ms ConnectResponse sleep** — unexplained constant on every login with an intermittent-failure shape; either find the ACE race and cite it, or replace with an acknowledged-ready check.
|
||||
4. **UN-4 — GfxObj sides/negative-surface logic** — diagnose against the retail-cited CellStruct interpretation on a known double-sided GfxObj; promote to AP with a citation or align it.
|
||||
5. **TS-55 — AdminEnvirons fog/radar presentation** — exact retail mechanism is known; port the authored ambient/fog fields, radar blanking, Clear, and `0x270F` together.
|
||||
6. **TS-19 — Legacy ChaseCamera deletion** — already marked "pending the follow-up deletion commit"; its continued existence can mask or manufacture flap symptoms during debugging.
|
||||
|
||||
**Phase-gated (do WITH the phase, flagged here so they aren't forgotten):**
|
||||
M2 combat must land TS-25
|
||||
|
|
|
|||
|
|
@ -99,36 +99,30 @@ character state continuously.
|
|||
|
||||
### P2 — Response-layer edge family — retires TS-1, TS-4, AP-7; closes #166, #116
|
||||
|
||||
**Status (2026-07-30, FINAL — Campaign P final physics slice):** TS-1 and
|
||||
AP-7 retired same-day as originally recorded. **TS-4 is now ALSO
|
||||
RETIRED** — the oracle follow-up pass
|
||||
(`docs/research/2026-07-30-ts4-116-oracle-plan.md`) found the freeze the
|
||||
first implementation attempt hit was one layer downstream of Path 6
|
||||
(inside `AdjustOffset`'s crease projection against a purely-vertical
|
||||
offset — a genuine retail-identical degeneracy, not a bug) and ran the
|
||||
plan's own decisive confirming test: `Ts4SteepRoofWedgeCaptureTests`'s
|
||||
horizontal-velocity variant (matching the realistic live-play input that
|
||||
originally validated the shortcut) converges cleanly with the shortcut
|
||||
removed. The Path-6 steep-poly shortcut is deleted from both
|
||||
`BSPQuery.cs` and `FlatBspQuery.cs`; the pure-vertical degenerate case is
|
||||
pinned (not fixed) as register row AD-56. **#116 is narrowed, not
|
||||
closed**: shape-2 (D4 first-airborne-frame hard-stop) is CLOSED — the
|
||||
oracle plan's structural dispatch-routing hypothesis was confirmed by
|
||||
instrumentation with no cdb session needed, and the D4 pin is un-skipped.
|
||||
Shape-1 (tick-22760 lateral-slide loss) got a real, independently-decomp-
|
||||
confirmed fix (Path 6's foot-clear/head-hit branch now returns `Collided`
|
||||
+ `SetCollisionNormal` directly, matching pc:323824-323834/ACE
|
||||
`BSPTree.cs:221-230`), but the confirming replay showed this does NOT
|
||||
explain tick-22760 itself — that mover is grounded (dispatches through
|
||||
Path 5, not Path 6) and the actual "no normal recorded" mechanism
|
||||
(`SpherePath.PrecipiceSlide`'s `find_crossed_edge`-false fallback) is
|
||||
independently confirmed byte-exact retail behavior too. The remaining
|
||||
divergence is most likely this test's simplified door-registration
|
||||
fixture, not the response layer — see ISSUES.md #116 and the oracle
|
||||
plan's Addendum 2 for the full trace and the concrete next step (re-run
|
||||
against the faithful Setup-based door registration). AD-55 (the sled
|
||||
slope-flatness constant, split out of AP-7's retirement) is ALSO retired
|
||||
this same slice — byte-proven `cos(10°)` per the oracle plan's Addendum.
|
||||
**Status (2026-07-31, FINAL):** TS-1 and AP-7 retired as originally
|
||||
recorded. TS-4's first 2026-07-30 removal was accepted by an incomplete
|
||||
resolver-only fixture, failed the live matrix with a roof wedge/uphill-bounce
|
||||
regression, and was reverted. The 2026-07-31 closure began from a fresh
|
||||
`BSPTREE::find_collisions` read and ports the exact asymmetric Path-6 split:
|
||||
primary/foot hits use `SetCollide` + `LandingZ` + `Adjusted`, while
|
||||
secondary/head hits use `CollisionNormal` + `Collided`; neither writes a
|
||||
sliding normal. Both graph and prepared-flat implementations match that
|
||||
oracle.
|
||||
|
||||
The corrective acceptance no longer calls the old horizontal-input fixture
|
||||
"production-shaped." `Ts4ProductionQuantumConformanceTests` executes the
|
||||
already-airborne, zero-root-motion 30 Hz Core collision tail — acceleration,
|
||||
body integration, transition resolve, exact body/cell commit, then
|
||||
`handle_all_collisions` — and retains its behavior-bearing cell, contact,
|
||||
sliding, stationary-fall, and velocity state for 90 ticks. Graph and flat
|
||||
match by raw bits for vertical/inward/tangential/downhill cases and a genuine
|
||||
positive-Z uphill jump; exact terminal state, non-penetration, no fixed point,
|
||||
and no second launch are pinned. No further product-code correction was
|
||||
needed after that test became faithful, and there is no active AD-56 row. The
|
||||
older resolver-only wedge test remains only as a historical three-second
|
||||
signature control. #116 shape-2 remains closed; shape-1 remains narrowed as
|
||||
recorded in its issue history. AD-55 remains retired by the raw-byte
|
||||
`cos(10°)` proof.
|
||||
|
||||
The collision *response* layer (what happens after a hit): ground
|
||||
friction, cliff edges, downhill landings, near-perpendicular wall
|
||||
|
|
@ -145,10 +139,11 @@ binds every subagent here.
|
|||
stop-at-edge.
|
||||
3. **#166:** port the landing "sled" (Sledding state set/clear sites;
|
||||
the sled friction constants already sit in `calc_friction`).
|
||||
4. **TS-4:** replace the Path-6 steep-poly in-place-slide shortcut with
|
||||
retail's `SetCollide → Path-4 → ContactPlane` landing chain, and
|
||||
remove the two BSP-layer `SetSlidingNormal` writes (retail's only
|
||||
in-transition writer is `validate_transition`).
|
||||
4. **TS-4:** remove the Path-6 steep-poly shortcuts and port retail's exact
|
||||
sphere split: primary/foot uses `SetCollide` + `LandingZ` + `Adjusted`;
|
||||
secondary/head uses `CollisionNormal` + `Collided`. Remove every BSP-layer
|
||||
`SetSlidingNormal` write (retail's only in-transition writer is
|
||||
`validate_transition`).
|
||||
5. **#116:** the near-perpendicular lateral-slide loss + first-airborne-
|
||||
frame divergence, driven by the existing tick-22760 replay and D4
|
||||
pins.
|
||||
|
|
|
|||
|
|
@ -599,17 +599,16 @@ manufacture a caller that sets it.
|
|||
### The former shortcut (HISTORICAL FACT; removed by Slice 2B)
|
||||
|
||||
Before Slice 2B, Path-6 (the default
|
||||
`sphere_intersects_poly → collide_with_pt / SetCollide` dispatch) tested each
|
||||
hit polygon's world-space normal. For BOTH sphere0 (feet) and sphere1 (head),
|
||||
if `worldNormal.Z < PhysicsGlobals.FloorZ` (steeper than ~49° from
|
||||
horizontal), acdream took a SPECIAL BRANCH:
|
||||
projects the move along the steep face, writes
|
||||
`collisions.SetCollisionNormal(worldNormal)` **and**
|
||||
`collisions.SetSlidingNormal(worldNormal)`, and returns
|
||||
`TransitionState.Slid` immediately — bypassing `SetCollide` entirely for
|
||||
steep hits. Only the shallow case (`worldNormal.Z >= FloorZ`) reaches
|
||||
`path.SetCollide(worldNormal); path.WalkableAllowance = LandingZ; return
|
||||
Adjusted;`.
|
||||
`sphere_intersects_poly → collide_with_pt / SetCollide` dispatch) was not
|
||||
symmetrically wrong. The parsed-graph primary/foot branch tested the hit
|
||||
polygon's world-space normal and, below `PhysicsGlobals.FloorZ`, projected
|
||||
the move along the face, wrote both collision and sliding normals, and
|
||||
returned `Slid`. Its secondary/head branch had already been corrected by
|
||||
#116 to retail's unconditional `CollisionNormal` + `Collided` response. The
|
||||
prepared-flat port still applied the steep shortcut to both spheres and sent
|
||||
both shallow cases through `SetCollide` + `Adjusted`; its head branch was
|
||||
therefore wrong for every slope. This distinction matters: retail does not
|
||||
apply one common response to both spheres.
|
||||
|
||||
The in-code comment is unusually candid about why: **"This is a
|
||||
deliberate deviation from retail... Validated against retail debugger
|
||||
|
|
@ -621,10 +620,11 @@ was shipped SAME-DAY as (and BECAUSE) the retail-faithful
|
|||
§2 above — also dated 2026-04-30, tagged "L.4") still wedged in testing
|
||||
when tried without this shortcut.
|
||||
|
||||
### Retail: NO steepness branch at the BSP layer (FACT, pseudo-C:323740-323783, `0053a730` region)
|
||||
### Retail: NO steepness branch in either Path-6 sphere response (FACT, `0053a730` region)
|
||||
|
||||
Read directly from the named decomp (the `sphere_intersects_poly` /
|
||||
`set_collide` dispatch inside `BSPTREE::find_collisions`'s default path):
|
||||
`set_collide` dispatch for the primary/foot sphere inside
|
||||
`BSPTREE::find_collisions`'s default path):
|
||||
|
||||
```
|
||||
if (sphere_intersects_poly(...) || eax_26 != 0) {
|
||||
|
|
@ -635,11 +635,21 @@ if (sphere_intersects_poly(...) || eax_26 != 0) {
|
|||
}
|
||||
```
|
||||
|
||||
**There is no steepness test here at all.** Retail's BSP layer calls
|
||||
`set_collide` and returns `ADJUSTED_TS` **unconditionally**, for a steep
|
||||
roof exactly the same as a shallow ramp. `walkable_allowance` is always
|
||||
set to `LandingZ` (the permissive landing threshold) at this layer,
|
||||
regardless of the actual polygon slope. This directly confirms the P2
|
||||
**There is no steepness test in this foot branch.** It calls `set_collide`
|
||||
and returns `ADJUSTED_TS` for a steep roof exactly as for a shallow ramp.
|
||||
`walkable_allowance` is always set to `LandingZ` (the permissive landing
|
||||
threshold), regardless of polygon slope. If the foot is clear but the
|
||||
secondary/head sphere hits, retail instead performs the other slope-agnostic
|
||||
response:
|
||||
|
||||
```
|
||||
localtoglobalvec(sphere_path.localspace_pos, &normal, &head_poly->plane.N);
|
||||
COLLISIONINFO::set_collision_normal(&collision_info, &normal);
|
||||
return 2; // COLLIDED_TS
|
||||
```
|
||||
|
||||
The head branch neither calls `set_collide` nor returns `ADJUSTED_TS`.
|
||||
Neither sphere response has a steepness branch. This directly confirms the P2
|
||||
plan's description and the digest's #137-mechanism-2 finding
|
||||
(`memory/project_physics_collision_digest.md:1008-1014`): **retail's
|
||||
BSP/sphere collision layer never writes `collision_info.sliding_normal`
|
||||
|
|
@ -653,16 +663,13 @@ domain, §2 above).
|
|||
|
||||
### TS-4 port shape (COMPLETED 2026-07-31)
|
||||
|
||||
Delete both `if (worldNormal{0,1}.Z < PhysicsGlobals.FloorZ) { ... return
|
||||
TransitionState.Slid; }` blocks (`BSPQuery.cs:2200-2215` and
|
||||
`:2240-2255`) entirely. Both sphere0 and sphere1 hits should fall straight
|
||||
through to the existing `path.SetCollide(worldNormal); path.WalkableAllowance
|
||||
= PhysicsGlobals.LandingZ; return TransitionState.Adjusted;` — i.e., make
|
||||
Path-6 do EXACTLY what its own shallow branch already does, for every
|
||||
hit, matching retail's unconditional `set_collide`. This mechanically
|
||||
retires both `SetSlidingNormal` write sites (satisfying DO-NOT-RETRY §0
|
||||
item 1 permanently — deleted, not just avoided) with no replacement logic
|
||||
needed at this layer.
|
||||
Delete the primary/foot steep shortcut in both representations. Every foot
|
||||
hit must call `SetCollide`, set `WalkableAllowance=LandingZ`, and return
|
||||
`Adjusted`. Preserve the parsed-graph head branch corrected by #116, and
|
||||
replace the prepared-flat head steep/shallow split with the same unconditional
|
||||
`SetCollisionNormal` + `Collided` response. No Path-6 branch writes a sliding
|
||||
normal. This is the exact retail foot/head split, not a shared fallback to the
|
||||
foot behavior.
|
||||
|
||||
### Port-order coupling with TS-1 (historical guard, now satisfied)
|
||||
|
||||
|
|
@ -1202,17 +1209,35 @@ representations by raw bits and pin every mutated and preserved field:
|
|||
- both: a pre-existing sliding normal is preserved byte-for-byte.
|
||||
|
||||
The failed first removal was a test-harness lesson, not a retail exception.
|
||||
Its gravity-only replay always passed `isOnGround:false` and discarded each
|
||||
accepted result's Contact/OnWalkable bits, making the nested edge/StepDown
|
||||
chain impossible to exercise on the next frame. The replacement replay uses
|
||||
the same retained `PhysicsBody` chronology as production. Parsed graph and
|
||||
prepared flat now match by raw result/body bits for vertical roof descent,
|
||||
downhill input, uphill pressure (including a no-launch/no-bounce assertion),
|
||||
tangential roof travel, inward-plus-tangent wall travel, and flat-roof ledge
|
||||
rejection. Every trace asserts finite bounded motion and signed-plane non-
|
||||
penetration. The former #116 D4 control is active: its primary-sphere hit
|
||||
hard-stops frame one through SetCollide, then the accepted persistent normal
|
||||
permits the downward slide on frame two.
|
||||
Its gravity-only replay always passed `isOnGround:false`, manually zeroed
|
||||
vertical velocity, and only copied part of the accepted contact state, so it
|
||||
could not reproduce the live caller's next-frame chronology. The replacement
|
||||
`Ts4ProductionQuantumConformanceTests` replay executes each already-airborne,
|
||||
zero-root-motion 30 Hz Core collision quantum in the production order:
|
||||
`calc_acceleration`, `UpdatePhysicsInternal`,
|
||||
`ResolveWithTransition`, exact body/cell commit, then
|
||||
`PhysicsObjUpdate.CommitSetPositionTransition` (the Core owner of retail's
|
||||
Contact/OnWalkable replacement plus `handle_all_collisions`). It carries the
|
||||
same body, cell, contact plane, walkable plane, sliding state, stationary-fall
|
||||
counter, cached velocity, and transient flags for all 90 ticks. PositionManager
|
||||
root composition, animation hooks, movement callbacks, and fresh-airborne
|
||||
`LeaveGround`/`HitGround` edges are deliberately outside this already-airborne
|
||||
dat-free fixture; it does not claim to replay those presentation/motion stages.
|
||||
|
||||
Parsed graph and prepared flat match by raw result/body bits for vertical,
|
||||
inward, tangential, and downhill roof motion plus a genuine positive-Z uphill
|
||||
jump. The foot-contact jump's apex precedes roof contact and every later
|
||||
candidate velocity remains non-positive in Z. A separate elevated head-only
|
||||
collision reaches the wall while Z velocity is still positive and pins the
|
||||
valid-normal, inward-dot retail 5%-elastic reflection without adding vertical
|
||||
velocity. Every direction rejects a half-second fixed point and signed-plane
|
||||
penetration, while exact terminal velocity, Contact/OnWalkable/Sliding bits,
|
||||
sliding normal, and contact plane are fixed by raw float bits. The older
|
||||
resolver-only wedge capture remains a deliberately weaker historical control
|
||||
and is restored to its original three-second bound. The former #116 D4
|
||||
control remains active: its primary-sphere hit hard-stops frame one through
|
||||
SetCollide, then the accepted persistent normal permits the downward slide on
|
||||
frame two.
|
||||
|
||||
The complete historical #273/#271/#269/#265/#185/#137/#116/cellar/roof
|
||||
matrix and the full Core Release suite pass without a replacement
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue