# MRTK Spatial Mesh observer inspector confusing

**URL:** <https://forum.magicleap.cloud/t/mrtk-spatial-mesh-observer-inspector-confusing/2099>\
**Category:** Unity Development\
**Tags:** development\
**Created:** [June 20, 2023, 11:47am UTC](https://forum.magicleap.cloud/t/mrtk-spatial-mesh-observer-inspector-confusing/2099 "2023-06-20T11:47:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheMunk](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@TheMunk](https://forum.magicleap.cloud/u/TheMunk)\
**Post date:** [June 20, 2023, 11:47am UTC](https://forum.magicleap.cloud/t/mrtk-spatial-mesh-observer-inspector-confusing/2099/1 "2023-06-20T11:47:53Z")

</div>

Why is there double of the same settings?

 ![image](https://us1.discourse-cdn.com/flex019/uploads/magicleap1/original/1X/83b8213fe57d1cd852d6911b00ac10853c205f59.png)  
It implies only changing the overrides in the top, but from looking at the code (and building) it doesn't seem to have any effect.  
Why not just hide the fields we shouldn't touch?

---

<div class="post-metadata">

**Author:** ![etucker](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.magicleap.cloud/etucker/32/842_2.png) [@etucker](https://forum.magicleap.cloud/u/etucker)\
**Post date:** [June 21, 2023, 3:08pm UTC](https://forum.magicleap.cloud/t/mrtk-spatial-mesh-observer-inspector-confusing/2099/3 "2023-06-21T15:08:47Z")

</div>

Hi @TheMunk,

Thank you for bringing this to our attention. We've logged this as feedback and shared it with our voice of customer team.

Thank you,

El

---

<div class="post-metadata">

**Author:** ![kdowney](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.magicleap.cloud/kdowney/32/481_2.png) [@kdowney](https://forum.magicleap.cloud/u/kdowney)\
**Post date:** [July 7, 2023, 9:14pm UTC](https://forum.magicleap.cloud/t/mrtk-spatial-mesh-observer-inspector-confusing/2099/4 "2023-07-07T21:14:52Z")

</div>

Hi @TheMunk, As @etucker noted, we have indeed logged your feedback. I wanted to follow up to best answer your question: Magic Leap offers a few extra settings in our Meshing Subsystem compared to the default AR Foundation's implementation. We intended to provide users the ability to adjust all of those values. To your point, we are investigating streamlining the editor UI to reduce confusion in the future.
