Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Cloth mesh lags when moving after skin
#1
Bug 
[Image: LJk5bYM]
Vertices closed to the ring are set fixed, when the ring is moving, vertices closed to the ring move slower than expected.
The solver update mode is set to lateupdate. Please tell me how to fix this bug Confundido
If the gif failed to load, try this https://imgur.com/LJk5bYM
Reply
#2
(30-07-2019, 12:34 PM)Madashidiao Wrote: [Image: LJk5bYM]
Vertices closed to the ring are set fixed, when the ring is moving, vertices closed to the ring move slower than expected.
The solver update mode is set to lateupdate. Please tell me how to fix this bug Confundido
If the gif failed to load, try this https://imgur.com/LJk5bYM

Hi there,

This is not a bug. Obi is an iterative solver. So this means it won't converge to a perfect solution every frame. If you move fixed particles very far away in a frame, all particles attached to them will only correct a fraction of the error (that is, "extra" distance to the fixed particles) each frame.

A possible fix would be simulating in local space, so that you can control the amount of world-space inertia transferred to the cloth. See:
http://obi.virtualmethodstudio.com/tutor...space.html

Also, don't use LateUpdate mode unless 100% necessary as it is highly unphysical. Using AfterFixedUpdate and moving your object around in FixedUpdate would be much better.
Reply
#3
(01-08-2019, 08:09 AM)josemendez Wrote: Hi there,

This is not a bug. Obi is an iterative solver. So this means it won't converge to a perfect solution every frame. If you move fixed particles very far away in a frame, all particles attached to them will only correct a fraction of the error (that is, "extra" distance to the fixed particles) each frame.

A possible fix would be simulating in local space, so that you can control the amount of world-space inertia transferred to the cloth. See:
http://obi.virtualmethodstudio.com/tutor...space.html

Also, don't use LateUpdate mode unless 100% necessary as it is highly unphysical. Using AfterFixedUpdate and moving your object around in FixedUpdate would be much better.

Corazón Thanks!
Reply