Search Issue Tracker
Fixed in 2018.2.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X, 2018.1.X
Votes
12
Found in
5.6.0p2
Issue ID
905161
Regression
Yes
Version Control Check Out window not popping up when using Provider.Checkout()
To reproduce:
1. Download attached project "BombBall.zip" and open in Unity
2. Open "RootScene" scene
3. Go to Edit > Project Settings > Editor
4. In "Version Control" connect with your server
Note: I'm using "Perforce"
5. Open "TestBehavior.cs" script which is in "Scripts" folder
6. In the Provider.Checkout modify path to "ResetableComponent.cs" script location
7. Save script and return to Unity Editor
8. In toolbar click Test > Test Behavior option
Expected result: The ResetableComponent.cs script is checked out, denoted by a red tick badge on its icon in the Project window and its presence in a changelist in the VCS Window and P4V.
Actual result: The script is not checked out.
Fixed in: 2018.2.0a2, 2018.1.0b11, 2017.4.1f1, 2017.2.2p3, 2017.1.3p4, 5.6.5p4
Reproduced on Unity 5.6.0b3, 5.6.0b5, 5.6.0p4, 2017.1.0b3
Not reproduced on Unity 5.4.5p1, 5.5.3p2, 5.6.0b1 and 5.6.0b2
Regression on Unity 5.6.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment