Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a7
2019.2.0b4
Issue ID
1158202
Regression
Yes
[Windows] Help window buttons break after changing the Version Control mode to Perforce on the 2019.2 versions
How to reproduce:
1. Create a new project
2. Go to "Edit" -> "Project Settings" -> "Editor" and under "Version control" change the mode to "Perforce"
3. Go to "Help" -> "Check for updates"
4. Observe that no new window is opened
Expected result: a new update "Unity update check" window is opened
Actual result: no new window is opened and the "Help" dropdown is closed
Reproduced in: 2019.2.0b4, 2019.2.0a7
Not reproducible in: 2019.3.0a4, 2019.3.0a1, 2019.2.0a6, 2019.2.0a1, 2019.1.5f1, 2019.1.0a1, 2018.4.1f1, 2018.3.0a1, 2017.4.28f1, 2017.4.0f1
Note:
- This issue reproduced with any button under the "Help" dropdown, other dropdowns seem to be functioning properly. Changing the version control mode back to "Hidden Meta Files" won't fix the issue, only an editor restart fixes the button functionality.
- Additionally when switching back from Perforce the added Version Control menu in "Assets" -> "Version Control" is not removed
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (fix version 2019.3):
Fixed in: 2019.2.0b7