Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.4f1
Issue ID
822007
Regression
No
Exporting a material includes textures that were assigned to other shaders
Reproduction steps:
1. Open the attached project
2. Select the 'mat' material
3. Assign texture '1' to Albedo and texture '2' to Height Map
4. Change the shader of the material to Mobile>Skybox
5. Assign texture '3' to Front and texture '4' to Back
6. Export Package 'mat'
Actual result: Exporting the material will include all four of the assigned textures, regardless of what shader is selected.
Expected: Exporting the material will include only the textures that are used in the selected shader
Reproduced with: 5.5.0a5, 5.4.0p1, 5.3.6p2, 5.2.5f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team