@absolutejs/rapier3d 0.2.1 → 0.3.0

package/README.md

@@ -42,8 +42,8 @@ web/Node/Bun; it does not claim a 2D, f64, CommonJS or SIMD distribution.
 
 Source base: dimforge/rapier commit
 `b716d375efc0201003f0cd9ef7168eee0b62c177`. Upstream Apache-2.0 licensing is retained.
-All engine source remains upstream; changes are confined to binding queries and
-this package's build/test tooling.
+Engine calculations remain upstream. Additions cover binding queries, package
+build/test tooling, and CCD profiler timer wiring; no solver equations are changed.
 
 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`.
@@ -92,3 +92,21 @@ Previously an absent native handle could be coerced to body zero during JavaScri
 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.
+
+## Actual CCD substeps (0.3)
+
+Enable `world.profilerEnabled = true`, step the world, then read
+`world.ccdSubsteps()`. It reports the native count of CCD passes in the last
+completed profiled step, rather than the configured maximum. Zero means CCD did
+not act, not that the world failed to advance. It returns null when unavailable:
+before a profiled step, while profiling is disabled, or after toggling profiling
+until a new step completes. Setting an already enabled profiler to true is idempotent.
+Restored worlds start with profiling disabled and no sample. Event-enabled stepping
+is covered too. This is opt-in telemetry; no physics policy or defaults change.
+The counter does not expose individual substep durations or times of impact.
+
+CCD timing now accumulates activation/impact-planning and motion-clamping work
+across all passes in a step. The TOI timer also accumulates instead of resetting
+for every clamp pass. Both are recorded only with profiling enabled. The timing
+fix leaves contact equations and trajectories unchanged; package tests compare
+profiled/unprofiled poses and official upstream trajectories.

package/absolutejs/README.md

@@ -42,8 +42,8 @@ web/Node/Bun; it does not claim a 2D, f64, CommonJS or SIMD distribution.
 
 Source base: dimforge/rapier commit
 `b716d375efc0201003f0cd9ef7168eee0b62c177`. Upstream Apache-2.0 licensing is retained.
-All engine source remains upstream; changes are confined to binding queries and
-this package's build/test tooling.
+Engine calculations remain upstream. Additions cover binding queries, package
+build/test tooling, and CCD profiler timer wiring; no solver equations are changed.
 
 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`.
@@ -92,3 +92,21 @@ Previously an absent native handle could be coerced to body zero during JavaScri
 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.
+
+## Actual CCD substeps (0.3)
+
+Enable `world.profilerEnabled = true`, step the world, then read
+`world.ccdSubsteps()`. It reports the native count of CCD passes in the last
+completed profiled step, rather than the configured maximum. Zero means CCD did
+not act, not that the world failed to advance. It returns null when unavailable:
+before a profiled step, while profiling is disabled, or after toggling profiling
+until a new step completes. Setting an already enabled profiler to true is idempotent.
+Restored worlds start with profiling disabled and no sample. Event-enabled stepping
+is covered too. This is opt-in telemetry; no physics policy or defaults change.
+The counter does not expose individual substep durations or times of impact.
+
+CCD timing now accumulates activation/impact-planning and motion-clamping work
+across all passes in a step. The TOI timer also accumulates instead of resetting
+for every clamp pass. Both are recorded only with profiling enabled. The timing
+fix leaves contact equations and trajectories unchanged; package tests compare
+profiled/unprofiled poses and official upstream trajectories.

package/dist/provenance.json

@@ -3,8 +3,8 @@
   "engine": "0.36.0",
   "bindings": "0.21.0",
   "bindgen": "0.2.129",
-  "wasmSha256": "91d68ed4f46fa1febbaf82abb7e8018150a3ad982560381df700e009997e6721",
-  "wasmBytes": 3297510,
+  "wasmSha256": "82c8735acd1b112c2d1368c8e46c91ce46a87e3d941b1a8d2fe11d46a8acbd3a",
+  "wasmBytes": 3298797,
   "solverChanges": false,
-  "addition": "Live solver anchors, explicit diagnostic controls, and correct restored collider ownership"
+  "addition": "Live contacts, fresh CCD pass counts, and aggregate CCD/TOI timing repair"
 }