@absolutejs/rapier3d 0.16.2 → 0.17.0

package/README.md

@@ -59,7 +59,7 @@ reconstructing the entire angular velocity through the inertia frame.
 
 Use Bun 1.4.4+absolute.1, Rust 1.94.0 with `wasm32-unknown-unknown`, and Python 3.12.
 Run `bun install --frozen-lockfile`, then `bash absolutejs/scripts/build-native.sh`.
-Cargo's exact lockfile is versioned, compilation is limited to two jobs, and the
+Cargo's exact lockfile is versioned, compilation defaults to one job (override with `CARGO_BUILD_JOBS`), and the
 wasm-bindgen 0.2.129 CLI archive is checksum verified before extraction. Caches and
 generated build output are reproducible; modified source and selected test
 receipts are committed. `dist/provenance.json` records the resulting WASM hash.
@@ -532,3 +532,67 @@ Independent builds match all 49 distribution files and the packaged native
 payload byte-for-byte. Raw executable/data sections match; only unshipped
 wasm-bindgen custom metadata differs. Snapshot layout and public APIs are
 unchanged.
+
+## Approaching contact support (0.16.3)
+
+Contact-patch reduction now applies the same contact-skin, soft-body and
+velocity-prediction eligibility rule as final solver admission. Previously,
+reduction filtered outer points by current distance alone. An approaching tilted
+box could consequently receive support along just one edge even though points
+on the opposite edge qualified for the solver. The regression now retains four
+support points spanning both sides, across three scales and both insertion orders.
+Stationary and receding outer points remain excluded by the existing rule.
+
+This is a two-file solver correction. It changes no public API, snapshot layout,
+material coefficient, solver budget or admission tolerance. Published Parry
+c566aabd is unchanged; the separate GJK-normal, persistent triangle-frame and
+conservative-CCD experiments are excluded. This release does not solve the
+remaining generated-heightfield or rotational direct-sweep limitations.
+
+Qualification includes 236 package tests, 844 game tests, exact snapshot replay,
+GPU-disabled browser tests, native one/two-worker controls and allocation-enabled
+no-std. The 24 paired terrain controls add no rejection, but the existing raw
+variant-0/1920 rejection remains. Four actual generated/excavated work requests
+and 18 flat-floor tree cases pass their original limits. Twenty of 24 paired
+terrain rows retain their measured physical fields exactly; others change.
+These checks do not establish continuous authored-material separation.
+
+Bounded paired CPU ratios versus 0.16.2 were approximately 1.03, 1.05 and 0.95
+for stationary predictions, resting stacks and falling boxes, with identical
+final physical fields. The affected tilted-patch ratio was 0.95. These shared-host
+observations are not hardware FPS or a universal speedup claim. See
+`absolutejs/research/predictive-support/` for complete evidence and limitations.
+
+Independent builds match all 49 distribution files and the packaged native
+payload byte-for-byte. Raw executable/data sections match; only unshipped
+wasm-bindgen metadata differs.
+
+## Rotational intervals and cached contact directions (0.17.0)
+
+Orientation-changing 3D direct sweeps now use separating-plane motion bounds
+to detect the captured case where a rotating bar crosses a surface between
+two clear endpoint poses. Translation-only sweeps retain the existing path.
+The distance-query budget remains 25, with explicit failure if safe progress
+cannot be established. Composite traversal is a separate limitation; this is
+not a universal continuous-separation guarantee.
+
+Stalled convex queries preserve the direction associated with the support
+bound used for classification. This fixes a captured tree/triangle query that
+reported about 202 mm penetration while independent plane projection bounded
+required separation to about 0.013 mm. Both corrections are qualified together: 
+the rotational change alone exposed this cached-direction error in the full
+oak excavation test. The combined engine passes it and all 844 game tests.
+
+Package API, snapshot layout, contact tolerances and solver budgets are unchanged.
+The raw variant-5/960 terrain clearance rejection remains identically present;
+physical outcomes elsewhere may change. Bounded CPU control scenes retain
+identical physical results and comparable timings. The targeted tilted-contact
+fixture costs about 51% more after extended warmup, about 0.037 ms extra per
+restored step in that fixture. This is a measured correctness tradeoff, not a
+browser FPS or general performance guarantee.
+
+Qualification includes 432 direct-sweep cases, captured old/new contact
+regressions, 237 package tests, GPU-disabled browser checks, native one/two-worker
+controls, no-std, 24 tree/rate comparisons, four generated/excavated requests,
+18 flat-tree cases and an independent build matching all shipped files.
+Evidence: `absolutejs/research/rotational-contact/`.

package/absolutejs/README.md

@@ -59,7 +59,7 @@ reconstructing the entire angular velocity through the inertia frame.
 
 Use Bun 1.4.4+absolute.1, Rust 1.94.0 with `wasm32-unknown-unknown`, and Python 3.12.
 Run `bun install --frozen-lockfile`, then `bash absolutejs/scripts/build-native.sh`.
-Cargo's exact lockfile is versioned, compilation is limited to two jobs, and the
+Cargo's exact lockfile is versioned, compilation defaults to one job (override with `CARGO_BUILD_JOBS`), and the
 wasm-bindgen 0.2.129 CLI archive is checksum verified before extraction. Caches and
 generated build output are reproducible; modified source and selected test
 receipts are committed. `dist/provenance.json` records the resulting WASM hash.
@@ -532,3 +532,67 @@ Independent builds match all 49 distribution files and the packaged native
 payload byte-for-byte. Raw executable/data sections match; only unshipped
 wasm-bindgen custom metadata differs. Snapshot layout and public APIs are
 unchanged.
+
+## Approaching contact support (0.16.3)
+
+Contact-patch reduction now applies the same contact-skin, soft-body and
+velocity-prediction eligibility rule as final solver admission. Previously,
+reduction filtered outer points by current distance alone. An approaching tilted
+box could consequently receive support along just one edge even though points
+on the opposite edge qualified for the solver. The regression now retains four
+support points spanning both sides, across three scales and both insertion orders.
+Stationary and receding outer points remain excluded by the existing rule.
+
+This is a two-file solver correction. It changes no public API, snapshot layout,
+material coefficient, solver budget or admission tolerance. Published Parry
+c566aabd is unchanged; the separate GJK-normal, persistent triangle-frame and
+conservative-CCD experiments are excluded. This release does not solve the
+remaining generated-heightfield or rotational direct-sweep limitations.
+
+Qualification includes 236 package tests, 844 game tests, exact snapshot replay,
+GPU-disabled browser tests, native one/two-worker controls and allocation-enabled
+no-std. The 24 paired terrain controls add no rejection, but the existing raw
+variant-0/1920 rejection remains. Four actual generated/excavated work requests
+and 18 flat-floor tree cases pass their original limits. Twenty of 24 paired
+terrain rows retain their measured physical fields exactly; others change.
+These checks do not establish continuous authored-material separation.
+
+Bounded paired CPU ratios versus 0.16.2 were approximately 1.03, 1.05 and 0.95
+for stationary predictions, resting stacks and falling boxes, with identical
+final physical fields. The affected tilted-patch ratio was 0.95. These shared-host
+observations are not hardware FPS or a universal speedup claim. See
+`absolutejs/research/predictive-support/` for complete evidence and limitations.
+
+Independent builds match all 49 distribution files and the packaged native
+payload byte-for-byte. Raw executable/data sections match; only unshipped
+wasm-bindgen metadata differs.
+
+## Rotational intervals and cached contact directions (0.17.0)
+
+Orientation-changing 3D direct sweeps now use separating-plane motion bounds
+to detect the captured case where a rotating bar crosses a surface between
+two clear endpoint poses. Translation-only sweeps retain the existing path.
+The distance-query budget remains 25, with explicit failure if safe progress
+cannot be established. Composite traversal is a separate limitation; this is
+not a universal continuous-separation guarantee.
+
+Stalled convex queries preserve the direction associated with the support
+bound used for classification. This fixes a captured tree/triangle query that
+reported about 202 mm penetration while independent plane projection bounded
+required separation to about 0.013 mm. Both corrections are qualified together: 
+the rotational change alone exposed this cached-direction error in the full
+oak excavation test. The combined engine passes it and all 844 game tests.
+
+Package API, snapshot layout, contact tolerances and solver budgets are unchanged.
+The raw variant-5/960 terrain clearance rejection remains identically present;
+physical outcomes elsewhere may change. Bounded CPU control scenes retain
+identical physical results and comparable timings. The targeted tilted-contact
+fixture costs about 51% more after extended warmup, about 0.037 ms extra per
+restored step in that fixture. This is a measured correctness tradeoff, not a
+browser FPS or general performance guarantee.
+
+Qualification includes 432 direct-sweep cases, captured old/new contact
+regressions, 237 package tests, GPU-disabled browser checks, native one/two-worker
+controls, no-std, 24 tree/rate comparisons, four generated/excavated requests,
+18 flat-tree cases and an independent build matching all shipped files.
+Evidence: `absolutejs/research/rotational-contact/`.

package/dist/build-info.mjs

@@ -1 +1 @@
-var e=Object.freeze({schemaVersion:1,scope:"package",packageName:"@absolutejs/rapier3d",packageVersion:"0.16.2",qualifiedKernelRelease:"0.16.2",upstream:"b716d375efc0201003f0cd9ef7168eee0b62c177",engine:"0.36.0",collisionLibraryVersion:"0.31.1",collisionSource:"git+https://github.com/absolutejs/parry?rev=c566aabd77be8ac7a427c2b704860c47e34657b9#c566aabd77be8ac7a427c2b704860c47e34657b9",bindings:"0.21.0",bindgen:"0.2.129",wasmSha256:"f1539c74bb9192cf8f6dfaa95bb6654a605d326faa0bdd02939d798a455bc57c",wasmBytes:3357159,solverChanges:!0});export{e as buildInfo};
+var e=Object.freeze({schemaVersion:1,scope:"package",packageName:"@absolutejs/rapier3d",packageVersion:"0.17.0",qualifiedKernelRelease:"0.17.0",upstream:"b716d375efc0201003f0cd9ef7168eee0b62c177",engine:"0.36.0",collisionLibraryVersion:"0.31.1",collisionSource:"git+https://github.com/absolutejs/parry?rev=8c68a625c15930ca8b685f30861aedf5d59c3726#8c68a625c15930ca8b685f30861aedf5d59c3726",bindings:"0.21.0",bindgen:"0.2.129",wasmSha256:"0dad2a033f7d46e262a08a370429dc6e23ea95009f824c14a76302a15a8f73a8",wasmBytes:3362690,solverChanges:!0});export{e as buildInfo};

package/dist/provenance.json

@@ -2,15 +2,15 @@
   "schemaVersion": 1,
   "scope": "package",
   "packageName": "@absolutejs/rapier3d",
-  "packageVersion": "0.16.2",
-  "qualifiedKernelRelease": "0.16.2",
+  "packageVersion": "0.17.0",
+  "qualifiedKernelRelease": "0.17.0",
   "upstream": "b716d375efc0201003f0cd9ef7168eee0b62c177",
   "engine": "0.36.0",
   "collisionLibraryVersion": "0.31.1",
-  "collisionSource": "git+https://github.com/absolutejs/parry?rev=c566aabd77be8ac7a427c2b704860c47e34657b9#c566aabd77be8ac7a427c2b704860c47e34657b9",
+  "collisionSource": "git+https://github.com/absolutejs/parry?rev=8c68a625c15930ca8b685f30861aedf5d59c3726#8c68a625c15930ca8b685f30861aedf5d59c3726",
   "bindings": "0.21.0",
   "bindgen": "0.2.129",
-  "wasmSha256": "f1539c74bb9192cf8f6dfaa95bb6654a605d326faa0bdd02939d798a455bc57c",
-  "wasmBytes": 3357159,
+  "wasmSha256": "0dad2a033f7d46e262a08a370429dc6e23ea95009f824c14a76302a15a8f73a8",
+  "wasmBytes": 3362690,
   "solverChanges": true
 }