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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment