@absolutejs/rapier3d 0.4.0 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -132,3 +132,29 @@ features; disabling warm starting changes convergence. Neither is a general fix
132
132
  for penetration. Evaluate the entire requested simulation horizon and geometric
133
133
  intersections, alongside live/cached contact diagnostics. A process that exits
134
134
  successfully after an early physical guard is not a completed physical test.
135
+
136
+
137
+ ## Current-body shape contact queries (0.5.0)
138
+
139
+ ```ts
140
+ const contact = firstCollider.contactColliderAtCurrentBodyPoses(secondCollider, 0);
141
+ ```
142
+
143
+ This additive query composes each collider's local pose with its current parent
144
+ body pose. It observes direct body edits before the next world step without
145
+ propagating poses, stepping the simulation, or altering cached solver contacts.
146
+ Parentless colliders use their own world pose. The optional third argument reuses
147
+ a `ShapeContact` result. Prediction must be finite and nonnegative, in world units.
148
+
149
+ Use this for bounded explicit diagnostics, not every render/physics tick. It
150
+ allocates shape queries and returns a world-space native shape contact, not a
151
+ solver manifold, continuous sweep or authored-material overlap bound. Collision
152
+ filters, hooks and contact skin are not applied. Native unsupported shape pairs
153
+ can return null as well as separated pairs; null is not a general disjointness
154
+ proof. Existing `contactCollider` retains its stored-collider-pose semantics.
155
+
156
+ The distinction matters for rotating contacts: projecting current anchors onto a
157
+ stored normal can report no penetration while a fresh shape query finds overlap.
158
+ Both observations are useful, but answer different questions. Release 0.5.0 keeps
159
+ the 0.4.0 native kernel byte-for-byte unchanged; it does not include the private
160
+ relative-motion, EPA or clamp-graph solver experiments.
@@ -6,5 +6,5 @@
6
6
  "wasmSha256": "65ebc43d69dc3b4b290b29ca30ff44955711c8002799503749bcc03060783b39",
7
7
  "wasmBytes": 3299287,
8
8
  "solverChanges": false,
9
- "addition": "Validated contact recycling, recycle distance and warm-start controls; contact and CCD diagnostics"
9
+ "addition": "Current-body-pose shape contact query; validated contact policy and CCD diagnostics; native kernel unchanged"
10
10
  }