Closed MaxBittker closed 3 months ago
Good catch. Looks like I didn’t wire up the spring constraint when attached to two dynamic bodies.
Yippee! Thanks for the fix and the excellent engine
On Sat, Mar 23, 2024 at 5:34 AM Sébastien Crozet @.***> wrote:
Closed #602 https://github.com/dimforge/rapier/issues/602 as completed via #603 https://github.com/dimforge/rapier/pull/603.
— Reply to this email directly, view it on GitHub https://github.com/dimforge/rapier/issues/602#event-12224006630, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNEHGSRZKUZQH2OHWTLE5DYZVEB7AVCNFSM6AAAAABFAL74B6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGIZDIMBQGY3DGMA . You are receiving this because you authored the thread.Message ID: @.***>
I reproduced this by editing examples2d/joints2.rs to use springs instead of revolute joints.
let joint: SpringJointBuilder = SpringJointBuilder::new(0.0, 0.1, 0.1).local_anchor2(point![0.0, 0.0]);
it panics inside of JointTwoBodyConstraint::solve: https://github.com/dimforge/rapier/blob/master/src/dynamics/solver/joint_constraint/joint_velocity_constraint.rs#L335
and
self.solver_vel1[0]
is equal to18446744073709551615
(usize::max )I've tried to investigate when this value becomes wrong but I can't figure it out so far!
Originally found here:https://github.com/dimforge/rapier.js/issues/268 but I found it also occurs in the native version.