Hello everyone. I would like to have some tips on how I can reduce or eliminate the impact of my Motor PrismaticConstraint from shaking on its own, even without any movement. You see, I currently use a Motor ActuatorType to raise the model up or down within the main model, but since these are moving parts I cannot anchor them and sometimes they start shaking on their own until part of the model either eventually comes apart by itself, or starts vibrating violently even when both parts of the model are not moving through scripts and just start vibrating on their own after lack of movement.
Having said that the Motor PrismaticConstraint can sometimes be unreliable. Sometimes it stays still other times it shakes violently on its own, and it’s impossible to know whether you’ve fully fixed the issue or not before it reoccurs; something like I call a case of arbitrary behavior. So what kind of good practices may I be able to implement to help reduce the likelihood of this issue occurring? Is simply adjusting the MotorMaxForce property, a foolproof solution to this topic?
As a quick update just to confirm, I’ve reduced the value of the MotorMaxForce property and so far its temporarily fixed the issue. Whether this is just chance or arbitrary, this is the whole point of this topic to reduce this problem from occurring rather than patching with temporary unreliable fixes.
So I was wondering, is this the most reliable way or are there other ways which I might have missed? How can I be sure that the problems don’t reoccur? Are there other ways aside from changing or reducing the MotorMaxForce alone, to reduce the impacts or likelihood of the PrismaticConstraint shaking violently on its own accord? Any help is appreciated.
Edit:
Here is what I mean when the PrismaticConstraints’ excessive vibrations cause the model attached to come apart.
I am going to mark this topic as solved for now so this topic becomes useful for others with potentially the same problem. If anybody else has any other ideas, aside from retrospectively reducing the MotorMaxForce property alone, then feel free to comment further on this topic. Otherwise, this is the best solution that I can give to anybody so far with potentially the same issue.
