Search Issue Tracker
Fixed
Fixed in 6000.5.0a7
Votes
0
Found in
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133351
Regression
Yes
Production Ready Shaders Sample do not show up as imported in Package Manager window when importing more than one Sample
Reproduction steps:
1. Create a new project
2. Window > Package Management > Package Manager > Shader Graph > Samples
3. Import any of the Shader Graph Sample (e.g. Feature Examples)
4. Import Production Ready Shaders Samples
5. Observe Production Ready Shaders Samples folder in the Project window
6. Observe Production Ready Shaders Samples in the Package Manager
Actual result: “Import” button is still present when Production Ready Shaders Samples are imported
Expected result: “Reimport” button is present and Production Ready Shaders Samples are imported
Reproducible with: 6000.3.0a6, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Not reproducible with: 6000.0.66f2, 6000.3.0a5 (f9a1fab5607a)
Reproduced on: Windows 11, macOS Sequoia 26.2 (M4)
Note:
- Issue is no longer reproducible after deleting Samples folder and importing it again
- Issue is not reproducible when importing Production Ready Shaders Samples only
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 (fix version 6000.5.0a7):
Fixed in 6000.5.0a7