@absolutejs/rapier3d 0.1.0 → 0.2.1

package/README.md

@@ -12,7 +12,10 @@ await RAPIER.init();
 world.solverContactPair(firstCollider, secondCollider, (manifold, flipped) => {
   for (let i = 0; i < manifold.numSolverContacts(); i++) {
     const point = manifold.solverContactPoint(i);
-    const distance = manifold.solverContactDist(i);
+    const cachedDistance = manifold.solverContactDist(i);
+    const separation = manifold.solverContactSeparation(i);
+    const anchor1 = manifold.solverContactPoint1(i);
+    const anchor2 = manifold.solverContactPoint2(i);
     // Copy values here. The callback view expires when the callback returns.
   }
 });
@@ -55,3 +58,37 @@ queries and exception cleanup. Browser-worker validation is separate from native
 GPU performance testing; no GPU is required by the engine.
 
 This is a maintained AbsoluteJS distribution, not an official Dimforge release.
+
+## Live anchors and explicit clustering control (0.2)
+
+`solverContactPoint1/2` return the native solver anchors transformed by current body
+poses. `solverContactSeparation` projects their difference onto the stored world
+solver normal. Negative means overlapping anchors; invalid indices return null.
+Anchor values include contact skin and hook offsets, so they are not necessarily
+points on the visible material surface. The normal is from the contact update;
+this is not a new narrow-phase query or a continuous material penetration bound.
+The old cached `solverContactDist` remains explicitly separate.
+
+`world.integrationParameters.contactClustering` exposes the existing engine switch.
+It defaults to true, exactly as upstream. Set it only between steps; disabling it
+may increase solver workload and is not a general penetration fix. Snapshot restore
+preserves the setting. The game is not instructed to turn it off by this release.
+
+The independent every-step cube/cavity audit demonstrates the distinction: about
+0.459mm current penetration is visible in live anchors when the cached distance is
+zero. Disabling clustering retains about 0.469mm peak penetration in that case.
+Neither extra telemetry nor changing clustering is presented as a physics cure.
+
+`minCcdDt` exposes the engine's minimum CCD substep duration in seconds. Its
+upstream default stays `1/60/100`, even when the outer timestep is changed.
+The setter rejects negative, non-finite and f32-overflowing values. Smaller values
+can introduce instability; changing it is an explicit experiment, not an automatic
+quality preset. Both controls are retained through native snapshot serialization.
+
+## Restored collider ownership (0.2.1)
+
+Snapshot restoration now preserves `null` for an unowned collider's `parent()`.
+Previously an absent native handle could be coerced to body zero during JavaScript
+wrapper reconstruction. Real body-zero and fixed-body attachments remain intact.
+This changes wrapper metadata only; native ownership, WASM and solver behavior are
+unchanged. Repeated snapshot restoration and browser workers are regression tested.

package/absolutejs/README.md

@@ -12,7 +12,10 @@ await RAPIER.init();
 world.solverContactPair(firstCollider, secondCollider, (manifold, flipped) => {
   for (let i = 0; i < manifold.numSolverContacts(); i++) {
     const point = manifold.solverContactPoint(i);
-    const distance = manifold.solverContactDist(i);
+    const cachedDistance = manifold.solverContactDist(i);
+    const separation = manifold.solverContactSeparation(i);
+    const anchor1 = manifold.solverContactPoint1(i);
+    const anchor2 = manifold.solverContactPoint2(i);
     // Copy values here. The callback view expires when the callback returns.
   }
 });
@@ -55,3 +58,37 @@ queries and exception cleanup. Browser-worker validation is separate from native
 GPU performance testing; no GPU is required by the engine.
 
 This is a maintained AbsoluteJS distribution, not an official Dimforge release.
+
+## Live anchors and explicit clustering control (0.2)
+
+`solverContactPoint1/2` return the native solver anchors transformed by current body
+poses. `solverContactSeparation` projects their difference onto the stored world
+solver normal. Negative means overlapping anchors; invalid indices return null.
+Anchor values include contact skin and hook offsets, so they are not necessarily
+points on the visible material surface. The normal is from the contact update;
+this is not a new narrow-phase query or a continuous material penetration bound.
+The old cached `solverContactDist` remains explicitly separate.
+
+`world.integrationParameters.contactClustering` exposes the existing engine switch.
+It defaults to true, exactly as upstream. Set it only between steps; disabling it
+may increase solver workload and is not a general penetration fix. Snapshot restore
+preserves the setting. The game is not instructed to turn it off by this release.
+
+The independent every-step cube/cavity audit demonstrates the distinction: about
+0.459mm current penetration is visible in live anchors when the cached distance is
+zero. Disabling clustering retains about 0.469mm peak penetration in that case.
+Neither extra telemetry nor changing clustering is presented as a physics cure.
+
+`minCcdDt` exposes the engine's minimum CCD substep duration in seconds. Its
+upstream default stays `1/60/100`, even when the outer timestep is changed.
+The setter rejects negative, non-finite and f32-overflowing values. Smaller values
+can introduce instability; changing it is an explicit experiment, not an automatic
+quality preset. Both controls are retained through native snapshot serialization.
+
+## Restored collider ownership (0.2.1)
+
+Snapshot restoration now preserves `null` for an unowned collider's `parent()`.
+Previously an absent native handle could be coerced to body zero during JavaScript
+wrapper reconstruction. Real body-zero and fixed-body attachments remain intact.
+This changes wrapper metadata only; native ownership, WASM and solver behavior are
+unchanged. Repeated snapshot restoration and browser workers are regression tested.

package/dist/provenance.json

@@ -3,8 +3,8 @@
   "engine": "0.36.0",
   "bindings": "0.21.0",
   "bindgen": "0.2.129",
-  "wasmSha256": "2b2be5df0023f15b0dfc54629019f8e370365b90d8669be98fd67cc49230a5d5",
-  "wasmBytes": 3295710,
+  "wasmSha256": "91d68ed4f46fa1febbaf82abb7e8018150a3ad982560381df700e009997e6721",
+  "wasmBytes": 3297510,
   "solverChanges": false,
-  "addition": "Separate clustered solverContactPair query"
+  "addition": "Live solver anchors, explicit diagnostic controls, and correct restored collider ownership"
 }