UE4 crashes on bootup when Oculus is plugged in

Development Programming & Scripting
1

Hello, I am constantly getting a crash when I try to boot Unreal with Oculus SDK2 plugged into the computer.

I have installed the version 4.4 runtime for windows.
I have UE4 version 4.7.0.

I have an Asus G750JS-RS71 Laptop with latest windows update.
GPU: GeForce GTX 870M
CPU: Intel(R) Core™ i7-4700HQ CPU@ 2.4 GHz
Memory: 11.89 Usable
Resolution: 1920 x 1080, 60hz
driver version: 347.52 (latest)

This has happened for over a month, and I have no idea why. I can’t find anything online about it. Any help would be awesome. FYI. I have done a clean reboot of my computer and re-install of all software already. Still didn’t fix anything and I get the same crash on boot up. If I create a project and then plug in Oculus, it freezes UE4 and then crashes. Uninstalling and going to previous version doesn’t work. Also, When I play the Tuscany demo from Oculus SDK, it works just fine. The error seems to be exclusive to Unreal Engine 4.

Here is the crash report:

MachineId:
EpicAccountId:

Access violation - code c0000005 (first/second chance not available)

OVRDisplay64 + 25145 bytes
OVRDisplayRT64 + 41621 bytes
OVRDisplayRT64 + 22780 bytes
UE4Editor_D3D11RHI!FD3D11Viewport::FD3D11Viewport() + 721 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\windows\d3d11rhi\private\windows\windowsd3d11viewport.cpp:61]
UE4Editor_D3D11RHI!FD3D11DynamicRHI::RHICreateViewport() + 168 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\windows\d3d11rhi\private\d3d11viewport.cpp:461]
UE4Editor_RHI!RHICreateViewport() + 140 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\rhi\public\rhimethods.h:1463]
UE4Editor_SlateRHIRenderer!FSlateRHIRenderer::CreateViewport() + 477 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\slaterhirenderer\private\slaterhirenderer.cpp:266]
UE4Editor_SlateCore!SWindow::ShowWindow() + 215 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\slatecore\private\widgets\swindow.cpp:1087]
UE4Editor_MainFrame!FMainFrameHandler::ShowMainFrameWindow() + 266 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\editor\mainframe\private\frame\mainframehandler.h:205]
UE4Editor_MainFrame!FMainFrameModule::CreateDefaultMainFrame() + 4199 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\editor\mainframe\private\mainframemodule.cpp:202]
UE4Editor_UnrealEd!EditorInit() + 3591 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\editor\unrealed\private\unrealed.cpp:115]
UE4Editor!GuardedMain() + 926 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\launch\private\launch.cpp:133]
UE4Editor!GuardedMainWrapper() + 26 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\launch\private\windows\launchwindows.cpp:126]
UE4Editor!WinMain() + 249 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.7\engine\source\runtime\launch\private\windows\launchwindows.cpp:202]
UE4Editor!__tmainCRTStartup() + 329 bytes [f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c:618]

2

Try using extended mode. It crashes because your laptop don’t have active HDMI display port. means your HDMI Out port is connected to the integrated graphics not the GTX870m. Try running Unreal and oculus on Desktop. I am also facing the same issue with Asus Rog with GTX 860m.

3

So that fixes it, but will I ever be able to get it to be less laggy? As it stands, using this method is incredibly jittery.

4

I am also not able solve the issue. because of that I am using Desktop for the oculus development.

5

I wish I can use a Desktop- but unfortunately, I am using the computer my company gave me for work. We don’t have the budget to buy everyone new computers. I know for a fact that we can use Oculus in Unity3d 4.6 with no problems. It’s odd that Epic hasn’t addressed this issue since I’m sure it’s a problem laptop developers are having. After all, laptop development is becoming more and more common.

I hope Epic can fix this soon.

6

Hello BattlePulse_Ari,

I have been trying to reproduce this on a few different machines and I am still unable to reproduce this crash on our end. I have spoke with a developer about the issue and I have found that it is a known issue that is currently under investigation. I would like to pool our knowledge to further narrow down the specifics of this issue. So to this effect I would like to collapse the threads by redirecting further comments to the original post.

Post here please:

Make it a great day

7

it seems like this is a laptop issue with Optimus. There are no solutions yet, and it’s been awhile. When can I expect any actual answers?

8

Hello BattlePulse_Ari,

As I said the issue is still being looked into and with that being the case there is no current established time frame for the implementation of a solution. Also please be sure to divert any more comments to the thread that is linked above.

Make it a great day