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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #667026