Search Issue Tracker
Fixed in 6000.0.11f1
Fixed in 6000.0.X, 6000.1.X, future release
Votes
0
Found in
2022.3.35f1
6000.0.37f1
6000.1.0a7
Issue ID
UUM-74364
Regression
No
[VFXG] Setting an exposed texture to none assigns a random texture
Steps to reproduce:
1. Import the attached package
2. Open Test-Mesh Instancing Scene
3. In the Hierarchy, select any Mesh Count
4. Set exposed texture to None
5. Pan Scene View Camera around
Actual results: random texture is assigned while panning camera
Expected results: default texture is assigned and remains consistent
Reproducible with versions: 2022.3.X
Not reproducible with versions: N/A
Can’t test with versions: N/A
Tested on (OS): Windows
Notes:
- We need a PR #49416 (PR link in the description) to be merged in order to reproduce this issue
h1.
- It can be workarounded by assigning a valid texture
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
Add comment