Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a6
Issue ID
1187137
Regression
Yes
[VCS] Local files can't be marked for Add via the VCS Context Menu
How to reproduce:
1. Create a new project in your prefered workspace and open it
2. Connect it to Perforce or PlasticSCM and uncheck the "Automatic Add" option
3. Create a new folder, right-click it and try to mark it for Add
4. Observe that the option is greyed out
Expected result: Files can be marked for add via the Context menu
Actual result: Files can't be marked for add via the Context Menu and the option is greyed out
Reproducible in: 2020.1.0a6,
Not reproducible in: 2020.1.0a5, 2019.3.0b5, 2019.2.7f2, 2018.4.10f1, 2017.4.32f1
Note: reproduces both with Perforce and PlasticSCM
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.0a7