Restore tutorial return placement and source terrain collision eligibility

This commit is contained in:
UnixNight committed 2026-10-25 01:30:09 -04:00
1 parent ca08c468ba
commit 8d60a68511
36 files changed
+991 -69

No files matched your search

+10 -7
View File
@@ -2,7 +2,7 @@
This checkpoint implements deterministic static geometric collision against the
extracted original scene. It is **not the recovered original collision solver**.
The original collision masks, class activation rules, shape selection, tolerances,
Remaining collision masks, class activation rules, tolerances,
step handling and controller state integration are still unresolved. No original
runtime comparison establishes collision fidelity.
@@ -12,8 +12,10 @@ runtime comparison establishes collision fidelity.
`5a33d11311fc222631eb8f7384d1863192cb1f55f7e67035caa0ae12fd9892ab`.
The existing read-only extractor produces
`artifacts/extracted/level1b/scene.json` in unchanged original Y-up world units:
8,607 expanded vertices and 2,869 triangles. Collision uses **all nondegenerate
source triangles**, independent of `Mesh.Draws`, texture or material resolution.
8,607 expanded vertices and 2,869 triangles. Collision now excludes the18
triangles of shape94 ncwater, following the recovered NC shape-name gate at
44DD2F..44DD70. All2,851 other nondegenerate source triangles remain eligible,
independent of `Mesh.Draws`, texture or material resolution.
The actual lab has no degenerate triangles removed by this rule. Mesh vertex/index
arrays and original files are not modified.
@@ -27,10 +29,11 @@ collision mask. Rendering visibility alone is therefore not used to discard them
The regression creates a mesh with no visible draws and proves its original
triangles still block movement.
No decorative surface is excluded at this checkpoint: there is insufficient
specific evidence for a general exclusion rule. This conservative policy can block
on decorative surfaces or invisible proxies that original state/activation logic
would disable. Animated/dynamic scene entities are not added to this static mesh.
The NC exclusion is a shape-name prefix rule, not a material heuristic. The shape
metadata already exists in prepared scene mesh records; vertex/index/render data
is preserved. Other activation/mask rules remain unresolved. See water-collision.md
and underground-route.md for source bytes and the actual passage regression.
Animated/dynamic scene entities are not added to this static mesh.
There is no invented room-sized collision box or coordinate clamp.
## Capsule coordinates and API