From 50bfaeac131d05003072b2265d1800e0a30dc446 Mon Sep 17 00:00:00 2001 From: Nicolas Earnshaw Date: Tue, 6 Aug 2024 14:25:44 -0300 Subject: [PATCH] Update colliders.md Signed-off-by: Nicolas Earnshaw --- content/creator/sdk7/3d-essentials/colliders.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/creator/sdk7/3d-essentials/colliders.md b/content/creator/sdk7/3d-essentials/colliders.md index ca0e2447..67db553d 100644 --- a/content/creator/sdk7/3d-essentials/colliders.md +++ b/content/creator/sdk7/3d-essentials/colliders.md @@ -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`). +{{< /hint >}} + ```ts // create entity const myEntity = engine.addEntity()