Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.3
2019.3.0f6
2020.1
Issue ID
1221046
Regression
No
Layered Materials are not including child materials as dependencies when exporting a package
How to reproduce:
1. Open user-submitted project (Layered Materials.zip)
2. Select the Assets/Materials/Material.mat
3. See that it has 3 child materials: '0_Blue.mat', '1_Red.mat', '2_Yellow.mat'
4. Right-click 'Material.mat' and select 'Export package'
5. Make sure 'Include dependencies' is checked
Expected result: the 3 child materials are in the list of items to export
Actual result: the 3 child materials are not in the list of items to export
Reproducible with: 2018.4.17f1, 2019.3.2f1, 2020.1.0a24
Could not test with: 2017.4.37f1(HDRP unavailable for Layered Materials)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Lights with Cookies generate Cookie Atlas and increase Memory usage every time when Play mode is entered
- Crash on mono_traverse_object_internal when exiting Play mode on a specific project
- Camera prefab shows up in overrides after upgrade when game view is changed to Simulator
- Prefab Override context menu does not appear when changing attributes on a Terrain Component
- Particles are visible through Mesh when Sprite-Lit-Default Material is used
Resolution Note:
There is no dependency between layered material and child material. The "child" material are just an ease of authoring, when pressing the button it is just copy/pasting the attribute, that all, so they can be exported. To export them, they need to be explicitly selected.