- Newest
- Most votes
- Most comments
Hey @REDACTEDUSER
Here's the reference: http://docs.aws.amazon.com/lumberyard/latest/userguide/component-constraint.html
Thanks for this approach! By using a simple Ball constraint it works, but by looking over the actual problem IMHO this limiting shouldn't be required at all if LY would provide a method for retrieving the actual mass for a given point. This way it would be possible to consider the current mass at a given point when applying an impulse and the hovercraft never should go crazy again with its rotations. So the formula would look something like this:
impulseAtThruster = Lerp(rayDistanceRatio, 0, maxEnergy) * massAtThrusterRatio
Did I overlooked smth or doesn't LYs physics system provide such a method for retrieving the current mass at a given point?
Impulses are generally applied at the center of mass unless you state a particular point (a 3d vector) in world space you want it to act upon so any inconsistencies are either from the engine or your maths calculating the correct thrust vector.
It is also possible that air resistance is to blame here but I dont know how extensive the physics engine is.
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- Accepted Answerasked a year ago
- Accepted Answerasked 6 years ago
- Accepted Answerasked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 23 days ago
- AWS OFFICIALUpdated a year ago