Search Issue Tracker
Fixed in 5.5.1
Votes
0
Found in
5.5.0b5
Issue ID
834072
Regression
Yes
[OpenVR] app built and run with d3d12 crashes on start
standalone players that use OpenVR and D3D12 settings crash when launched. Here's a call stack I grabbed:
> d3d12Test_debug.exe!OpenVR::Initialize(struct UnityVRDeviceSpecificConfiguration &) Unknown
d3d12Test_debug.exe!VRDevice::Initialize(bool) Unknown
d3d12Test_debug.exe!VRModule::StartRenderingToDevice(void) Unknown
d3d12Test_debug.exe!PlayerLoadFirstScene(bool) Unknown
d3d12Test_debug.exe!PlayerWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,char *,int) Unknown
d3d12Test_debug.exe!memcpy_s() Unknown
kernel32.dll!BaseThreadInitThunk() Unknown
ntdll.dll!00007ff870065e91() Unknown
also have a crash dump at https://oc.unity3d.com/index.php/s/JpeuhPUNKzxEdgi
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment