-
Notifications
You must be signed in to change notification settings - Fork 2
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
Body Representation breaks if climbing through geometry #7
Comments
Is this still an issue? |
Yeah it's part of my 5 bullet point list to enhance climbing further. The idea is to not allow diverging, even while climbing, by utilizing a smaller collider (that resembles the headset rather than the whole body). |
Would this cause the character to release the grab when the collision happens? I'm encountering a scenario where if my body touches a collider while climbing, the grab lets go. Wondering if it's related. |
This is still an issue last I checked. |
That's why this issue is still open |
ExtendRealityLtd/Zinnia.Unity#157 brought Body Representation and Climbing.
If the user climbs down and therefore moves the play area through a collider the body won't follow as the virtual physics prevent it from doing so. While this is the expected and desired outcome the Body Representation logic actually breaks when doing this - the play area offset from the body staying out of the geometry keeps being applied to the body.
This problem ultimately boils down to a regular event of body↔️ headset divergence which should probably be handled by default for this particular issue. A solution currently is to disable and enable the
BodyRepresentationInternalSetup
as itsOnEnable
ensures the necessary movement of the play area to converge the headset back into the virtual body. A better solution may be to extract that logic into a public method and allow specifying a teleporter to use for this kind of absolute position change. That in turn will allow fading if necessary and offers using the teleporter pipeline for more customization.The text was updated successfully, but these errors were encountered: