![]() |
Help Rod is shown with a "stair" effect - Printable Version +- Obi Official Forum (https://obi.virtualmethodstudio.com/forum) +-- Forum: Obi Users Category (https://obi.virtualmethodstudio.com/forum/forum-1.html) +--- Forum: Obi Rope (https://obi.virtualmethodstudio.com/forum/forum-4.html) +--- Thread: Help Rod is shown with a "stair" effect (/thread-1557.html) |
Rod is shown with a "stair" effect - cberinger - 13-12-2019 Dear Obi Team, while experimenting with rods, I came along this "stair" effect (see attachments) Question is: how to get rid of the "stairs"? Cheers, Christian RE: Rod is shown with a "stair" effect - josemendez - 13-12-2019 (13-12-2019, 10:26 AM)cberinger Wrote: Dear Obi Team, Hi Christian, This is because in sequential mode, constraints are grouped in batches to be able to simulate them in different threads. Switch the bend/twist and/or stretch/shear constraints to parallel mode. This will somewhat hurt convergence, but you can make up for that by using more substeps or iterations. See: http://obi.virtualmethodstudio.com/tutorials/convergence.html Also, this post by DissidentDan is related (his point #3): http://obi.virtualmethodstudio.com/forum/showthread.php?tid=1550 RE: Rod is shown with a "stair" effect - cberinger - 13-12-2019 (13-12-2019, 10:31 AM)josemendez Wrote: Hi Christian, Hi Jose (hope I got the name right :-)) thanks for the quick answer! I will try and experiment with the parallel mode! Cheers, Christian RE: Rod is shown with a "stair" effect - josemendez - 13-12-2019 (13-12-2019, 10:46 AM)cberinger Wrote: Hi Jose (hope I got the name right :-)) You got it right, don't worry ![]() I've slightly updated the solver docs to reflect this important difference between the two modes: http://obi.virtualmethodstudio.com/tutorials/obisolver.html Quote:In Sequential mode, all constraints are evaluated in the order they were created (which is determined by each specific ObiActor) and each constraint “sees” the adjustments made by all previous constraints. This ensures quick convergence, so your constraints will need few iterations to look good. However it is not very stable when several constraints are fighting for control, so there are some use-cases where this mode is not a good choice. It is order-dependent, so in low-budget situations (few iterations and/or large timesteps) this can result in visible patterns in particle arrangement. For those of you a bit on the technical side, this is a Gauss-Seidel type of solver. |