Skip to main content
Up and Coming
July 26, 2014

Oculus Rift DK2 and UE4 4.3:problems with Oculus Runtime 0.4

Hey guys.

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 this 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:
http://static.oculus.com/sdk-downloads/Oculus+VR+Camera+Installer.exe
(Note: you will need to uninstall this 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:
1) Remove or Disable the "Oculus Service Scheduler" from the Windows Task Scheduler: "Start" button -> "Task Scheduler"
2) Switch display mode to Extended mode or uninstall the Oculus Display Driver;
3) Remove "OculusConfigUtil.exe" from Programs -> Startup (For example, C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup).
    This topic has been closed for replies.

    32 replies

    Up and Coming
    July 26, 2014
    Wish you were running an alert system that would email a notification to customers who are monitoring particular subjects, such as conflicts between the Rift and UE4.
    New Participant
    July 26, 2014
    Is this an issue if I am compiling from the master branch, or only the 4.3 stable release?

    When a fix comes out for this, how will it be rolled out? Will I need to pull down the unreal engine master branch and compile that, or is this just going to be a stand alone download for the new plug in?
    Up and Coming
    July 26, 2014
    Can anybody else still download that camera driver?

    I get the following from link:

    <Error>
    <Code>NoSuchBucket</Code>
    <Message>The specified bucket does not exist</Message>
    <BucketName>static.ocul... Installer.exe</BucketName>
    <RequestId>13B248FCB7CBE711</RequestId>
    <HostId>
    n+azuX/UjDCI/yJ0oiI+1ojUWGBbvN8Rxodao1M+YpiooFPPX2GuvaqVVkc1s8J1
    </HostId>
    </Error>
    Oculus Hut - A big fat slice of VR A page I made about surfing the virtual reality web! Janus VR Room 45: janus://zion.vrsites.com/1/45 YouTube: https://www.youtube.com/channel/UCj70pq7hA26fvLv832NmboA A little UE4 experience: Virtual Bard
    Up and Coming
    July 26, 2014
    "huttybangbang" wrote:
    Can anybody else still download that camera driver?

    No joy here, i get a HTTP 404 error..
    Inspiring
    July 26, 2014
    Yeah, the link is borked. I'll get this fixed for you guys.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    artyom17Author
    Up and Coming
    July 26, 2014
    The link is fixed. Sorry!
    Up and Coming
    July 26, 2014
    OK, thank you!
    Up and Coming
    July 29, 2014
    a question, must/can update the firmware if i want UE4 compatibility?

    i prefer compatibility with UE4
    PD: yes my english its bad i known i5-4570 - Shaphire r9-290, win10-64
    Participant
    July 29, 2014
    So recommended path now is to install camera-driver and continue using UE4 until there is a fix - and then install the full package?

    I am guessing the update has to come for UE4 to fix the issue in the end?
    Up and Coming
    July 29, 2014
    Just installing the camera drivers and launching UE4.3 with two 27" 2560x1440 monitors and the DK2 connected to the HDMI we are exploring our world without a glitch.

    We are on Windows 8.1 with an NVidia GTX 780Ti.

    Initially we had three black screens, but unplugging and plugging back in cables and a bit of rebooting, everything just started working. There was no logical order or process I can describe that explains why for about 10 minutes we had black screens and then in a moment, success.

    Loving the DK2, it can only get better from here.