Fix Interaction Passthrough layers to match the client behavior #120
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
momo-the-monster
approved these changes
Jan 14, 2025
Collaborator
momo-the-monster
left a comment
momo-the-monster
left a comment
There was a problem hiding this comment.
Your fix is approved, has been merged upstream and released as part of SDK 3.7.5!
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The VRC Scene Descriptor has a property called "Interact Passthrough" that determines whether User Layers will block interaction rays. We have updated this setting to reflect changes in interaction behavior.
We have also revised the layer specifications to account for the built-in layers: PlayerLocal ignores rays, while InternalUI blocks interaction. Although these layer objects are unlikely to be used, we have confirmed that this change ensures the interaction behavior matches that of the VRChat client.
These behaviors are clearly stated in the VRChat documentation as well.
https://creators.vrchat.com/worlds/layers/