Search Issue Tracker
Not Reproducible
Votes
0
Found in
4.5.2f1
Issue ID
626081
Regression
No
Editor crashes in DirectX 11 mode when GPU doesn't support DirectX 11
Graphics card doesn't support DirectX 11, only DirectX 9 and DirectX 10. Editor is being launched in DirectX 11 mode and crashes immediately with such output in the log file:
(0x7102EA84) (nvumdshim): (filename not available): OpenAdapter10 + 0x6854
(0x71035032) (nvumdshim): (filename not available): OpenAdapter10 + 0xce02
(0x6B97F12F) (d3d11): (filename not available): D3D11CreateDeviceAndSwapChain + 0x1b7f8
(0x6B969107) (d3d11): (filename not available): D3D11CreateDeviceAndSwapChain + 0x57d0
Workaround is to use -force-d3d9 argument when launching Unity.
Command line examples:
http://docs.unity3d.com/Manual/CommandLineArguments.html
This issue might be by design, but Unity editor shouldn't crash at all, even when GPU doesn't support DirectX 11 mode;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment