Search Issue Tracker
Fixed
Fixed in 6000.5.0a9, 6000.6.0a1
Votes
0
Found in
6000.3.5f1
6000.4.0b6
6000.5.0a5
6000.6.0a1
Issue ID
UUM-133170
Regression
No
UI Builder becomes unresponsive and UXML assets get corrupted when assigning a Texture2D AssetReference variable to a selector
Steps to reproduce:
- Create a new Unity project using a 3D Universal Template
- Create a new UXML file and open it in UI Builder
- In UI Builder create a new selector and a new USS file
- Select the created selector
- In the Inspector, expand the "Variables" foldout
- Click on the "+" icon and select "AssetReference"
- In the Texture2D field click on object picker
- Select "Default-Particle" Texture 2D
- Save the UXML file in UI Builder
- Observe the Console and UI Builder
Actual results: UI Builder is not interactable and UXML assets corrupt and are not openable, "Assertion failed on expression: 'type != SubFilterType::Exact'" and "NullReferenceException: Object reference not set to an instance of an object" errors are thrown
Expected results: no errors or asset corruption
Reproducible with versions: 6000.3.5f1, 6000.4.0b6, 6000.5.0a5
Can’t test with versions: 6000.0.66f1 (Variables not available)
Tested on (OS): macOS 26.2 (M1)
Notes:
- Additionally, trying to close the Editor opens up Bug Reporter
- Trying to create new UXML files - creates ~5 files at once and none of them are openable
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:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9