TO DO*: the tests with two moveable blocks are very confusing. What would help is to
show both attach points, and the line perpendicular to the normal at each attach
point.
TO DO*: Joint.align() will only align on ONE point, it only translates one of the objects
(and does not rotate). So, an object that has joints at two distinct places is going to
need custom alignment. Basically, Joint.align() works fine with the usual 'double-joint'
approach, and doesn't work in the other cases you find here in JointTest.
TO DO* make tests using each configuration of joints.
Shows that pendulum with 1 joint scenario has fairly good energy conservation
and joint tightness using 'small impacts' on joints and ExtraAccel.VELOCITY.
Returns void
Staticpendulum_1_joint_2
pendulum_1_joint_2(): void
Shows that pendulum with 1 joint scenario has fairly poor energy conservation and
poor joint tightness using extra accel on joints and
ExtraAccel.VELOCITY_AND_DISTANCE, when CollisionAdvance<RigidBodyCollision>.setJointSmallImpacts()
is turned off.
Returns void
Staticpendulum_1_joint_setup
pendulum_1_joint_setup(sim, advance): void
Setup the pendulum with 1 joint scenario; the pendulum travels on a horizontal
track, rocking back and forth because it starts at an angle.
Tests various configurations of Joints.
TO DO*: the tests with two moveable blocks are very confusing. What would help is to show both attach points, and the line perpendicular to the normal at each attach point.
TO DO*: Joint.align() will only align on ONE point, it only translates one of the objects (and does not rotate). So, an object that has joints at two distinct places is going to need custom alignment. Basically, Joint.align() works fine with the usual 'double-joint' approach, and doesn't work in the other cases you find here in JointTest.
TO DO* make tests using each configuration of joints.