Search Issue Tracker
By Design
Votes
0
Found in
2021.3.36f1
2022.3.21f1
2023.2.13f1
2023.3.0b10
6000.0.0b11
Issue ID
UUM-65453
Regression
No
Vector2 and Vector3 properties don’t have property locks in the Inspector window when a material is created using Shader Graph
How to reproduce:
1. Open the attached “Vector.zip” project
2. Select “Shader Graphs_New Shader Graph.mat”
3. Move a cursor a bit to the left from “Vector2” or “Vector3” text and observe the result
Expected result: property lock appears
Actual result: property lock doesn’t appear
Reproducible with: 2021.3.36f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b10
Reproduced on: macOS 14.2.1 (Intel)
Not reproducible on: No other environment tested
Notes:
- not reproducible with Vector4
- in 2021.3.36f1, it’s also reproducible with Vector4
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:
We're making note of general UI/UX improvements like this, but won't be addressing this as an independent issue.