Search Issue Tracker
Fixed in 2021.1.X
Duplicate in 2020.1.X
Votes
0
Found in
2018.3.0a1
2018.4
2019.3
2019.4
2020.1.0b10
2020.2.0a12
2020.2.0a17
Issue ID
1259939
Regression
Yes
[Vulkan] Player settings window turns black on clicking "+" button with Vulkan Graphics APIs.
Player settings window, Project Window, Scene view and Hierarchy turns black on clicking "+" button with Vulkan Graphics APIs.
Steps to repro:
1. Create a new project.
2. File > Build Settings > Player Settings > Other Settings.
3. Uncheck Auto Graphics API for Windows checkbox.
4. Add Vulkan Graphis APIs > Drag to the top of the list > Restart the Editor.
5. Click on "+" / Click on Project Window.
Actual Result:
Windows turns black on clicking over with Vulkan Graphics APIs
Expected Result:
Windows should not turn black on clicking over.
Reproducible in:
2020.2.0a17, 2020.2.0a12, 2020.1.0b14, 2020.1.0b10, 2019.4.3f1, 2019.3.15f1, 2018.4.23f1, 2018.4.0f1, 2018.3.6f1, 2018.3.0a1.
Working fine in:
2020.2.0a11, 2020.1.0b9, 2018.2.0f2.
Note: Issue started occurring after updating Graphics drivers.
Reproducible on Driver Version:
1. Driver File Version: 27.21.0014.5148 (English)
Driver Version: 27.21.14.5148
2. Driver File Version: 26.21.0014.4587 (English)
Driver Version: 26.21.14.4587
Not Reproducible on Driver Version:
1. Driver File Version: 26.21.0014.3200 (English)
Driver Version: 26.21.14.3200
Environment:
Occurring only on Windows.
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
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a6.1011