Search Issue Tracker
Fixed in 5.3.0
Slow, system-crippling startup of D3D11 players with DisplayPort monitors
1) Locate a machine with an NVIDIA graphics card where the monitor is connected via a DisplayPort connection.
2) Build a Windows Standalone player that is set to use the D3D11 API only.
3) Launch the player.
4) Observe that between double-clicking the executable and seeing the launcher appear, some time passes - anything from 2 seconds to 30 seconds - during which the entire OS is sluggish, almost to the point of being unresponsive.
5) Compare the behaviour to the same project built to use D3D9 - no delay is observed.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Japanese diacritic symbols are missing from the build executable file when building the project
- [Hub] Tutorial Project summaries advise to set preferred Editor to 2019.1 when Hub 2.x does not have preferred Editor anymore
- Tilemap Collider 2D exists when tiles are being deleted
- Using Assert.Inconclusive in editmode stops the running test
- Overriding OnInspectorGUI without EditorGUILayout GetControlRect results in EditorGUI PropertyField invisible/clipped/collapsed