12-05-2021, 07:50 AM
(This post was last modified: 12-05-2021, 08:20 AM by josemendez.)
Hi hatchling,
Can you share a scene/project that reproduces this (send to support(at)virtualmethodstudio.com)?
I've been testing, but so far I've been unable to get this behavior. What I've done is programmatically add a rope between a static collider and a rigidbody with all rotational axis constrained (using a modified version of the RuntimeRopeGenerator script) at runtime. Then, get out of play mode, and play again. Things behave just like the first time, no ghost forces applied to rigidbodies.
The behavior you describe (or the way I understood it) doesn't make much sense to me, since ObiRigidbody does not store/serialize velocities between play sessions. There's no way that I can think of for data from the previous play session to affect the next one.
With no solvers/updaters in the scene ObiRigidbody.UpdateVelocities shouldn't even be called, so in theory there's no way the rigidbody velocities can be modified by Obi.
Can you share a scene/project that reproduces this (send to support(at)virtualmethodstudio.com)?
I've been testing, but so far I've been unable to get this behavior. What I've done is programmatically add a rope between a static collider and a rigidbody with all rotational axis constrained (using a modified version of the RuntimeRopeGenerator script) at runtime. Then, get out of play mode, and play again. Things behave just like the first time, no ghost forces applied to rigidbodies.
The behavior you describe (or the way I understood it) doesn't make much sense to me, since ObiRigidbody does not store/serialize velocities between play sessions. There's no way that I can think of for data from the previous play session to affect the next one.
Quote:Also worth nothing that no ObiSolvers are present in the scene until a rope is added.
With no solvers/updaters in the scene ObiRigidbody.UpdateVelocities shouldn't even be called, so in theory there's no way the rigidbody velocities can be modified by Obi.