Problem summary
Importing a Material Preset and then re-saving and importing it results in everything from that material group being imported, it sometimes even includes environment and locked items.
Customer reported version
modo.n/a
Customer reported platform
n/a
Steps to reproduce
1) Open Modo and create a Primitive Sphere.
2) Select the Sphere and Press 'M' to create a new material group, leave the settings as default and select 'OK'.
3) Select Add Layer and create a Checker, Scratches and Dented item.
4) Right-click the Default Material group and select Presets > Save As Material Assembly Preset.
5) Select 'Save Preset' and choose a location of your choice.
6) Name it 'Bug_Test' and select OK.
7) Press 'F6' to open the Preset Browser and locate the previous saved asset. Drag and drop it to import it into the existing material group.
8) Drag the Bug_Test.lxp group to the bottom of the material group and select Presets > Save As Material Assembly Preset. Select 'No' to the Window that appears and then select 'Save Preset'.
9) Go to the same location and name it 'Bug_Test2'. Drag and drop the newly created 'Bug_Test2' into the Shader Tree and notice that it contains all of the items that was present inside of the material group.
Expected behaviour
The Preset should contain the specified material group which should be the only assets that are saved and imported.
Actual behaviour
The Preset contains all of the assets in the parent material groups hierarchy, and sometimes includes environment and locked items.
Workaround
Unknown
Reproduced by support
This bug has been reproduced in:
16.1v1 - Windows 10, macOS 11.6
15.2v1 - Windows 10, macOS 11.6
Earliest version tested
15.2v1 - Material Assembly Presets did not exist before this version.
