Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0b9
Issue ID
777030
Regression
No
[VR] Combination of Player settings changes crashes Unity Editor
Using a simple project (probably any project) the Editor will crash if:
1) When the Editor session starts, VR is enabled and default Windows Graphics APIs is selected in Player settings.
2) In Player settings, toggle off VR.
3) In Player settings, toggle off Windows Default Graphics APIs.
4) Add OpenGLcore to the API list.
5) Delete D3D9 from the API list. The Editor crashes.
This set of steps consistently crashes the Editor. Skipping some of the steps or starting the Editor session with different settings often does not lead to a crash. So, this may be a corner case, but it is likely to rankle some of our customers.
I flagged this as not a regression because I can reproduce the crash in Unity 5.4.0b5.
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
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
This is a duplicate of issue #768729