Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0b8
Issue ID
966180
Regression
No
When a file is exclusively locked through Perforce the Unlock context option does nothing
Steps to reproduce:
1. Set up Perforce server and Unity Editor integration
2. In Unity create a random file
3. Through P4 mark the file for exclusive check out
4. Back in the editor, through the VC context menu check out the file
5. In the VC context menu select Unlock
6. It does nothing
Expected: If it's available to select, it should do something, otherwise, it should be marked as unclickable
Actual: You can click it and nothing happens
Reproduced on: 2018.1.0a3, 2017.3.0b8, 2017.2.0p1, 2017.1.2p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment