UE4Editor_Core!FDebug::AssertFailed()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\core\private\misc\outputdevice.cpp:440]
UE4Editor_D3D11RHI!FD3D11DynamicRHIModule::FindAdapter()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\windows\d3d11rhi\private\windows\windowsd3d11device.cpp:367]
UE4Editor_D3D11RHI!FD3D11DynamicRHIModule::IsSupported()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\windows\d3d11rhi\private\windows\windowsd3d11device.cpp:187]
UE4Editor_RHI!PlatformCreateDynamicRHI()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\rhi\private\windows\windowsdynamicrhi.cpp:81]
UE4Editor_RHI!RHIInit()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\rhi\private\dynamicrhi.cpp:172]
UE4Editor!FEngineLoop::PreInit()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\launch\private\launchengineloop.cpp:1456]
UE4Editor!GuardedMain()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\launch\private\launch.cpp:114]
UE4Editor!GuardedMainWrapper()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:126]
UE4Editor!WinMain()
[d:\build++ue4+release-4.12+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:200]
UE4Editor!__scrt_common_main_seh()
[f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:264]
kernel32 ntdll
Forgot this from the top of the crash reporter:
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\Build++UE4+Release-4.12+Compile\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 804]
Array index out of bounds: 1 from an array of size 1
you might want to add a little more detail as when does this happens? is this random? is this when the game is playing? does this happens after you delete an Enumerator and are still trying to access to it? it looks like the engine is trying to access a deleted element that is still being used somewhere.
After installing a fresh version of the engine and on preview 5 this is happening… after launching the engine from the launcher it crashes at 0%. I was able to use the previous preview versions before preview 5 I believe. I did two things the first was importing fbx from blender with apex cloth from the nvidea clothing profile tool, and the second I believe I may have installed a piece of software (think it was a visual redistributable) when opening up a project could have been 4.12 preview 5 or a 4.11 project it was so routine I didn’t really think about it until after the engine started crashing. I also deleted the project that is no longer opening unfortunately so I can’t share it to see if anyone could determine what is happening from the project…
I would like to add that I have also completely removed (deleted the folders and files after uninstalling as well) the engine and reinstalled it and verified it several times, I even tried opening with just the engine selected and no other options but the same thing keeps happening.
This crash is related to a driver issue. Ensure that you have updated your graphics card drivers. If they are up-to-date, please provide your DxDiag so that I can take a look at any other potential hardware conflicts.
Thank you
Try updating your Display Link drivers. You can perform a google search for them and grab the latest. This crash has been known to be related to issues with Display Link drivers so this may resolve it.
downloaded and installed the drivers but to no avail 
And to be honest I don’t think I ever needed or had any reason to download that software.
Downloading that software has resolved the same issue for other users in the past, which is why I suggested it.
I’ve also seen another user experiencing this issue who states that “Disabling “OVRServiceLauncher.exe” in windows services fixes the crash”.
Also, are you using any external plugins from the Marketplace or otherwise?
Ovrservice launcher might work, I will try when I get off work. I think the Oculus software did open up the first time it started crashing come to think of it!
That was it! I totally forgot that the rift turned on after that update… I just brushed it off like I had accidentally left it on or something.
Thanks!!! (I should have posted on here sooner lol)
So Sean Flint’s source was right, I needed to disable OVRserviceLauncher.exe in windows services
“Disabling “OVRServiceLauncher.exe” in
windows services fixes the crash”.
Glad there’s a workaround for launching the UE4 editor. Is there a bug report for this? Because of this I can’t seem to test VR projects with the Oculus in the editor with 4.12. 4.11.2 works without issue.
After disabling the ovrservice and launching the 4.12 editor (as of today) rift turned on and the oculus launcher opened upon launching a 4.12 project and is working as expected. (maybe a restart helped?)
Your sure you did nothing else besides restart? I still cannot get Oculus and any versions of 4.12 to work because of this crash. Killing the oculus launcher service and server in my task manager allows me to use 4.12, but oculus and 4.12 won’t work together for me.
I had already posted my issue before finding this thread. Will link this thread to it. I’ve also included my dxdiag, msinfo32, and zipped crash ue4 crash log. If anyone has further info on how to fix this issue, and not just get around it by disabling oculus service please let me know.