ColliderMesh with collider layer = NONE #419
Merged
Conversation
This file contains 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
Signed-off-by: Nicolas Earnshaw <[email protected]>
Deploying documentation with
|
| Latest commit: |
50bfaea
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6381c400.new-docs-6m4.pages.dev |
| Branch Preview URL: | https://nearnshaw-patch-5.new-docs-6m4.pages.dev |
gonpombo8
requested changes
Aug 6, 2024
| @@ -131,6 +131,10 @@ You can configure a `MeshCollider` component or the `GltfContainer` component to | |||
| - `ColliderLayer.CL_CUSTOM1` through to `CL_CUSTOM8`: Can be used together with raycasts, so that a ray only detects collisions with one specific layer. | |||
| - `ColliderLayer.CL_NONE`: Doesn't respond to collisions of any kind. | |||
|
|
|||
| {{< hint warning >}} | |||
| **📔 Note**: To disable collisions form a `MeshCollider` component, delete the component. Do not set the collision layer to `ColliderLayer.CL_NONE`. There's a known issue with the `MeshCollider` component. Instead of disabling all collisions, it makes this value equivalent to the default (`ColliderLayer.CL_PHYSICS | ColliderLayer.CL_POINTER`). | |||
There was a problem hiding this comment.
ColliderLayer.CL_NONE should work as expected
There was a problem hiding this comment.
We discussed this a bit over Slack but I'll bring some context here for the record:
I created an issue here: #418
"The technical explanation: CL_NONE enum value is 0, which is bitwise-treated the same as not having a ColliderLayer defined, which defaults to CL_PHYSICS & CL_POINTER."
A potential fix would be to change the enum value, but that would require more development time, in the mean time I think this warning is enough to be clear to creators that this is a known issue, what do you think @gonpombo8 ?
AlejandroAlvarezMelucciDCL
approved these changes
Aug 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.