You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently gravity is a float. Some games like to change the direction of gravity for various reasons.
Alternatively, to not break compatibility, an additional gravity_direction vector can be provided. It might also be worthwhile to just grab gravity from the physics engine itself instead using its own specific gravity value.
The text was updated successfully, but these errors were encountered:
Done in recent commit.
You can grab the build from the latest build workflow.
I will create a release and the update will be on the Asset Library in a few days.
It might also be worthwhile to just grab gravity from the physics engine itself instead using its own specific gravity value.
I'd rather not do this, because these are two completely different systems.
Another option would be to provide a kind of physics material resource for ropes that can be shared.
However, I'm not sure which properties should be included in such a material and which not.
It also only makes sense if there are a lot ropes of the same kind whose properties need to be changed dynamically at runtime.
Hence, this is a problem for the future when there is a certain demand for it.
Currently gravity is a float. Some games like to change the direction of gravity for various reasons.
Alternatively, to not break compatibility, an additional
gravity_direction
vector can be provided. It might also be worthwhile to just grab gravity from the physics engine itself instead using its own specific gravity value.The text was updated successfully, but these errors were encountered: