# Mesh.isEnabled versus Mesh.isVisible

**URL:** <https://forum.babylonjs.com/t/mesh-isenabled-versus-mesh-isvisible/35079>\
**Category:** Questions\
**Tags:** mesh\
**Created:** [October 24, 2022, 4:22pm UTC](https://forum.babylonjs.com/t/mesh-isenabled-versus-mesh-isvisible/35079 "2022-10-24T16:22:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![srothst1](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/srothst1/32/26001_2.png) [@srothst1](https://forum.babylonjs.com/u/srothst1)\
**Post date:** [October 24, 2022, 4:22pm UTC](https://forum.babylonjs.com/t/mesh-isenabled-versus-mesh-isvisible/35079/1 "2022-10-24T16:22:35Z")

</div>

Hello everyone 👋

Can someone please help me understand the difference between `Mesh.isEnabled` and `Mesh.isVisible`? `Mesh.isVisible` is pretty self explanatory, however I am not sure if it should be used in conjunction with `Mesh.isEnabled`. Both seem to update the visibility.

I created this babylon.js playground to help me improve my understanding:

> **[Babylon.js Playground](https://www.babylonjs-playground.com/#VF15SJ%234)**
>
> Babylon.js playground is a live editor for Babylon.js WebGL 3D scenes

From my observations, it seems like updating `Mesh.isEnabled` does not necessarily change the visibility of a `Mesh` or the value of `Mesh.isEnabled`.

---

<div class="post-metadata">

**Author:** ![srothst1](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/srothst1/32/26001_2.png) [@srothst1](https://forum.babylonjs.com/u/srothst1)\
**Post date:** [October 24, 2022, 4:49pm UTC](https://forum.babylonjs.com/t/mesh-isenabled-versus-mesh-isvisible/35079/2 "2022-10-24T16:49:40Z")

</div>

Some similar questions:

- What does it mean for a ~~node~~ mesh to be enabled?
- How is being enabled different than being visible?

---

<div class="post-metadata">

**Author:** ![Takemura](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/takemura/32/25836_2.png) [@Takemura](https://forum.babylonjs.com/u/Takemura)\
**Post date:** [October 24, 2022, 5:02pm UTC](https://forum.babylonjs.com/t/mesh-isenabled-versus-mesh-isvisible/35079/3 "2022-10-24T17:02:15Z")

</div>

If disabled, it will block node and its children from rendering (not considered by scene), so it improves performance. From what I know this includes all kinds of stuff like matrix (position, scale, rotation), visibility etc., everything related to scene. That way the renderer can skip all the calculations and it will use less memory/storage.

While invisible meshes can still update its matrix (position, scale, rotation), so you can move them like as collision meshes. Which (the collision) will not be considered on disabled meshes.

Note: I never heard of isVisible-property for nodes.

---

<div class="post-metadata">

**Author:** ![srothst1](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/srothst1/32/26001_2.png) [@srothst1](https://forum.babylonjs.com/u/srothst1)\
**Post date:** [October 24, 2022, 5:40pm UTC](https://forum.babylonjs.com/t/mesh-isenabled-versus-mesh-isvisible/35079/4 "2022-10-24T17:40:01Z")

</div>

Thank you @Takemura. This helps a lot 🙏
