10-12-2019, 05:47 PM
(This post was last modified: 10-12-2019, 06:00 PM by BisuDagger.)
(10-12-2019, 05:39 PM)josemendez Wrote: You have 100 (!) distance and friction iterations, that's enough of a reason to get awful performance. Why do you need that many iterations?
Btw, "smoothing" can be found in the ObiRope component inspector (in Obi v4). It's clearly visible in the screenshot you posted.
IIRC, because of the long length of the rope and load attached to it, the load was springy and didn't have a smooth movement when I used cursor.ChangeLength("using a value between 0 and 1").
I fixed the rope components and was able to run all 4 solvers on the Oculus Quest. The result unfortunately is in the movement. The position of the Load and Rope is update and then the rope stretches downward some giving the load a bouncy movement. What attribute can I use to reduce the stretching of the rope? I need to be able to treat this rope more like a chain where there is very little stretching and the length of the rope should be within inches of what I tell it to be.