-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contract listener questions #132
Comments
Btw. the video plays for me in Edge, but not in Firefox. |
|
|
I added some extra documentation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I visualize contacts, I see unexpected results.
Here is a box (if it doesn't play download the file and try with VLC, not sure what went wrong, but VLC works). The box falls down twice, once reporting contacts only on the ground, but the second time, it also reports a contact in the air (when it bounces back up).
contact.points.mp4
With the box it doesn't happen all the time, but with a sphere for the collision shape, I get this every time:
This is really weird, I don't see any reason why it should report a contact there.
And another question: This system is meant for impact sounds and so on. In PhysX the contact report gave me an "impulse" for each contact, so that I could determine how strong the impact was and pick a suitable reaction. Is that possible in Jolt? All I see is a penetration depth value, but I would expect this to be highly dependent on the framerate, rather than on the actual forces involved.
And yet another question: The ContactManifold structure holds mWorldSpaceContactPointsOn1+2. What's the dfifference? I would expect the manifold to be identical for both bodies involved, and since the points are given in world space, I don't see how these could ever differ? There is no helpful comment on the code about it.
The text was updated successfully, but these errors were encountered: