As many of you recently figured out DK2 and UE4 4.3 do not work together if Oculus Runtime 0.4 is installed.
We apologize for the mess. I want to confirm that UE4 4.3 is indeed DK2-ready. The problem is the new 0.4 Runtime that unfortunately is incompatible with 0.3-based apps for now. We are working on resolving issue right now, as well as preparing a new integration of UE4 and Oculus SDK 0.4.
As a workaround for now - you should not install 0.4 Runtime while you use UE4 4.3. Instead, you’ll need to install a DK2 camera driver, download link: static.oculusvr.com/sdk-downloads/Oculus+VR+Camera+Installer.exe
(Note: you will need to uninstall driver later when you decide to switch to 0.4).
If you already have installed 0.4 Runtime then you may either uninstall it and install the camera driver from above, or you need to disable the OVRService by performing the following steps:
Remove or Disable the “Oculus Service Scheduler” from the Windows Task Scheduler: “Start” button -> “Task Scheduler”
Switch display mode to Extended mode or uninstall the Oculus Display Driver;
Remove “OculusConfigUtil.exe” from Programs -> Startup (For example, C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup).
I really hope SDK 0.4 (or better, if 0.4.1 fixes DK2’s issues, black smear, judder, chromatic aberration), makes it into UE4 update 4.3.2 or 4.4, whichever is next… It’s no fun to always be a version or 2 behind the good bug fixes…lol
I use the 0.4 SDK but before running the Editor stop the wscript.exe process and the OVRService_x64.exe process.
That seems to work in couch knights and my own project fine.
Nothing on GitHub either, the runtime doesn’t seem to have been updated on any branch there so we shouldn’t get our hopes up just yet. Its a matter of time, maybe they are waiting on a more stable Oculus driver as well for the next update (0.4.1 anyone?)