When I apply AngularVelocity to a BodyAngularVelocity it only spins for half a second before stopping. This phenomenon only happens when executed from a localscript. Reapplying the AngularVelocity with the same vector does not affect it. The API clearly states that "The force does not have a goal, meaning that it is constantly applying force." which is apparently not the case in localscripts. Does anyone have an explanation/resolution for this problem?
COMMUNITY QUESTION
AngularVelocity not behaving properly?
3 answers
can you explain it where we can understand? it makes sence to you but not us! What's a AngularVelocity to a BodyAngularVelocity
I'm no expert at this but if the object has a fairly large mass and the 'MaxTorque' setting is set to a low value, then could it be that the velocity can't be satisfied as not enough force can be provided for the object to rotate?
This is the only limit I can think of given the situation you have explained.
2 comments
0
Also, does it come to a very sudden stop or does it seem to slow down a little?
0
I have tried many different maxtorques and powers but they all end up spinning for half a second before stopping instantly. Please try this yourself in studio and see if you get a similar outcome.
This issue was resolved when I increased the part's mass and the dampening of bodyposition. I do not have an explanation to this solution.
This discussion is preserved as it was. New answers, comments, and votes are closed.
2 comments
I'm not sure explaining to you what it is would make you understand it more than I do in order to help me out, but here's an article: http://wiki.roblox.com/index.php?title=API:Class/BodyAngularVelocity
And I expect you to have the common sense to look it up yourself instead of having me explain it to you. Why did you post here in the first place?