Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a4
2019.3.0a12
Issue ID
1175264
Regression
Yes
[VCS] Inspector VCS button bar is too big when the Check Out button is available and is misplaced for GameObject Materials
How to reproduce:
1. Create a new project in your preferred workspace
2. Connect it to Perforce
3. In the Project Window Create a new material, observe its VCS button bar at the top of its Inspector Window
4. Submit the material
5. The VCS button bar should now have the "Check Out" button available, observe the difference in the button bar sze from the previous state
Additional repro steps:
1. Create a new Material and observe the VCS Button bar
2. Attach the material to any GameObject and observe the VCS Button bar again on the GameObject's Material Component
Expected result: the button bar is exactly the same size with all VCS states/buttons
Actual result: the button bar when the Check Out button is available is too big
Reproduced in: 2019.3.0a12, 2019.3.0a4
Not reproducible in: 2019.3.0a3, 2019.2.1f1, 2019.1.14f1, 2018.4.6f1, 2017.4.31f1
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 2020.1):
Fixed in: 2020.1.0a2