# Display the mesh setup as a child in the part model tree

**URL:** <https://prepomax.discourse.group/t/display-the-mesh-setup-as-a-child-in-the-part-model-tree/3739>\
**Category:** Feature Requests\
**Created:** [October 14, 2026, 12:57pm UTC](https://prepomax.discourse.group/t/display-the-mesh-setup-as-a-child-in-the-part-model-tree/3739 "2026-10-14T12:57:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SergioP1975](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/sergiop1975/32/37_2.png) [@SergioP1975](https://prepomax.discourse.group/u/SergioP1975)\
**Post date:** [October 14, 2026, 12:57pm UTC](https://prepomax.discourse.group/t/display-the-mesh-setup-as-a-child-in-the-part-model-tree/3739/1 "2026-10-14T12:57:15Z")

</div>

When we have multiple components in the model, would be great if the mesh setups (sometimes are several ones for one part of the assembly) would appear as child items in the model tree, so if we want to modify the mesh the different setups were available directly.

Today as this relation is not reinforced, and as creating new mesh setups is not direct (too much menus and clics), I finish re-using those changing the feature (and part) were is applied (or for mesh refinement the quantity or size), but if I want to remesh with modifications the first part the setups are lost or changed.

---

<div class="post-metadata">

**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\
**Post date:** [October 14, 2026, 1:09pm UTC](https://prepomax.discourse.group/t/display-the-mesh-setup-as-a-child-in-the-part-model-tree/3739/2 "2026-10-14T13:09:29Z")

</div>

Maybe use Duplicate?

---

<div class="post-metadata">

**Author:** ![SergioP1975](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/sergiop1975/32/37_2.png) [@SergioP1975](https://prepomax.discourse.group/u/SergioP1975)\
**Post date:** [October 14, 2026, 1:16pm UTC](https://prepomax.discourse.group/t/display-the-mesh-setup-as-a-child-in-the-part-model-tree/3739/3 "2026-10-14T13:16:54Z")

</div>

Could be used, but take a look at this example, this is a medium complexity assembly, I have some with lots more components. Imagine that I would create individual mesh setups for every component, imagine one for size, one for sweep and one or two for local size to control the quantity of elements. Here we have 14 components, with 3 setups each…42 mesh setups that today we need to navigate to identify which one is affecting which component. If they were displayed as child items, we could just open it and change it easily knowing that will not affect other meshes.

 ![image](https://global.discourse-cdn.com/free1/uploads/prepomax/original/2X/1/18b89777bc2651ae6699afbd3a20c9941bdfc3a0.png)

---

<div class="post-metadata">

**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\
**Post date:** [October 17, 2026, 12:48pm UTC](https://prepomax.discourse.group/t/display-the-mesh-setup-as-a-child-in-the-part-model-tree/3739/4 "2026-10-17T12:48:45Z")

</div>

Today, you can group the mesh setup items and give them names.

If they are attached to parts, what happens to the mesh setup items that are assigned to multiple parts?

---

<div class="post-metadata">

**Author:** ![SergioP1975](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/sergiop1975/32/37_2.png) [@SergioP1975](https://prepomax.discourse.group/u/SergioP1975)\
**Post date:** [October 17, 2026, 1:04pm UTC](https://prepomax.discourse.group/t/display-the-mesh-setup-as-a-child-in-the-part-model-tree/3739/5 "2026-10-17T13:04:43Z")

</div>

Maybe you should only allow to select items (edges, surfaces…) of one part only. Otherwise, automaticly copied to each part colector.