Search Issue Tracker
Duplicate
Votes
1
Found in
5.6.0f3
Issue ID
911236
Regression
No
Textures removed from shaders are still collected as dependencies
Reproduction steps:
1. Open project attached (ShaderDefaultTextureIssue.zip).
2. Select material_1 from "Assets/Materials".
3. Press "Select Dependencies".
Expected result: Only one texture will be shown.
Actual result: Both textures will be shown.
Note: Material (and shader) used to have 2 textures, but after editing shader, second one were deleted from shader script. After that, material still select both textures as dependencies.
This is how to recreate this situation from scratch:
1. Create a shader with two textures.
2. Assign two different default textures to the shader.
3. Save the project.
4. Comment out the second texture in the shader.
5. Save the project.
6. Do reproduction steps.
Reproduced on: 5.4.0f3, 5.5.3p3, 5.6.1p1, 2017.1.0b5.
Comments (11)
-
Peter77
May 17, 2017 05:36
I imagine this issue is related to:
https://issuetracker.unity3d.com/issues/assetdatabase-dot-getdependencies-returns-unused-texture
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
- Toggling 'Editor Extension Authoring' doesn't dirty the UXML but its state depends on how it was previously saved
- Shader variants are stripped when they are not used during Player building
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
This is a duplicate of issue #667026