# Node Material Editor recursive frames?

**URL:** <https://forum.babylonjs.com/t/node-material-editor-recursive-frames/20126>\
**Category:** Feature requests\
**Created:** [April 19, 2021, 3:43pm UTC](https://forum.babylonjs.com/t/node-material-editor-recursive-frames/20126 "2021-04-19T15:43:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajp](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/ajp/32/9504_2.png) [@ajp](https://forum.babylonjs.com/u/ajp)\
**Post date:** [April 19, 2021, 3:43pm UTC](https://forum.babylonjs.com/t/node-material-editor-recursive-frames/20126/1 "2021-04-19T15:43:59Z")

</div>

Hey, I love the Node Material Editors (NMEs) frame concept. Is there any interest to make it recursive? I was playing around with “extending” the SimplexPerlin3D noise to make it scalable and wanted to have a single input be used multiple times, e.g. the `xz_scale` in [https://nme.babylonjs.com/#QPRJU9#26](https://nme.babylonjs.com/#QPRJU9#26)

 ![Babylon_js_Node_Material_Editor](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/2X/2/229df3b60b70016591276f4cbc5be1613ffd2c72.png)

I thought one solution (perhaps there is a better) would be to make a no-op node which is just an addition of 0.

But on collapsing the parent frame it did not contain the child frame within it:

![Babylon_js_Node_Material_Editor](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/2X/2/20515dee91e76210271fb9fcf7a850d8b17f2d0a.png)

Is there any interest in a PR to implement nesting / recursive frames? Perhaps there are good reasons not to support this. For example then when you get a parent frame, it would need to load all the child frames as well. If you had the same child frame it would have to de-dup, if you had a difference, even if subtle and unimportant it would have to add another entry (with an identical name? – in which case that would be confusing).

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 19, 2021, 4:30pm UTC](https://forum.babylonjs.com/t/node-material-editor-recursive-frames/20126/2 "2021-04-19T16:30:15Z")

</div>

Yeah so far it is not part of the design to keep things as simple as possible ☹

---

<div class="post-metadata">

**Author:** ![unicomp21](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/unicomp21/32/7989_2.png) [@unicomp21](https://forum.babylonjs.com/u/unicomp21)\
**Post date:** [April 25, 2021, 9:43pm UTC](https://forum.babylonjs.com/t/node-material-editor-recursive-frames/20126/3 "2021-04-25T21:43:20Z")

</div>

I’m all for keeping things simple. Maybe there is a way we could codegen/generate “nodeblock”'s from frames?

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 26, 2021, 3:39pm UTC](https://forum.babylonjs.com/t/node-material-editor-recursive-frames/20126/4 "2021-04-26T15:39:31Z")

</div>

Can you elaborate?

---

<div class="post-metadata">

**Author:** ![unicomp21](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/unicomp21/32/7989_2.png) [@unicomp21](https://forum.babylonjs.com/u/unicomp21)\
**Post date:** [April 27, 2021, 10:19am UTC](https://forum.babylonjs.com/t/node-material-editor-recursive-frames/20126/5 "2021-04-27T10:19:45Z")

</div>

Please disregard. The more I think about it, terrible idea.
