Skip to main content
Baashaas
New Participant
September 10, 2014

Updated to Unity 0.4.2 package and Headtracking stopped

Hi,

I imported the new Unity 0.4.2 SDK package into my scene and my headtracking and positional tracking stopped working. I did not change anything in my scene. Also the camera won't turn on anymore. Every other demo works perfectly fine. I tried restarting the Config app. Did not work. I tried several things in the last couple of hours but im clueless. Does anyone know what the problem is?
Thanks in advance

Edit: I fixed it
    This topic has been closed for replies.

    8 replies

    cybereality
    Inspiring
    September 10, 2014
    Can you try deleting all the Oculus stuff from the project and then reimporting the new package fresh?

    Also, check that the DLL is in the correct folder (not in /Plugins but in /Plugins/x86_64).
    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
    bdeschryver
    Up and Coming
    September 15, 2014
    Cyberreality,

    are you talking about the OculusPlugin.dll that is in the _Data folder after a Unity build?
    So it has to be moved from inside the Plugins folder to a subfolder named "x86_64", right ?
    cybereality
    Inspiring
    September 15, 2014
    Yeah, that's usually a good thing to try. The Plugins folder should not have any DLLs inside, only in the sub-folders.
    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
    bdeschryver
    Up and Coming
    September 16, 2014
    Cyberreality,


    if I do not have the oculus dll in the correct subfolder, does it mean I am using an outdated version of Oculus SDK/unity integration ? or is this a current bug ?

    What I did is create a subfolder called 'x86_64' and copied the dll in there (so that I have it in the root and subfolder also), I think that is the best solution.
    molton
    Up and Coming
    September 16, 2014
    Still having problems? Try deleting the OVRPlayerController prefab instance in your Unity project and import a new instance of the updated prefab in its place. Solves all types of problems for me.
    bdeschryver
    Up and Coming
    September 16, 2014
    What do you called the "updated prefab" ? I was always using SDK0.4.2, so I guess I am fine, no ? (and SDK0.4.2 seems to place the oculus plugin dll in the incorrect folder still..)

    Thanks
    molton
    Up and Coming
    September 16, 2014
    I'm saying after you update the unity integration the actual gameobject in your Unity project that is originally from a prefab under assets/OVR/prefabs might not be updated with the new Oculus integration just because you import it. I usually have to move my child objects that are in the ovrplayercontroller out of the ovrplayercontroller and delete the gameobject, then re-add the ovrplayercontroller prefab from the assets/OVR/prefabs folder in the project view and put my other objects back. But if you're in 0.4.2 and it's working I wouldn't do that.
    bdeschryver
    Up and Coming
    September 29, 2014
    "cybereality" wrote:
    Yeah, that's usually a good thing to try. The Plugins folder should not have any DLLs inside, only in the sub-folders.

    Cyberreality,

    I did a brand new Unity 4.5.2.f1 project with the SDK0.4.2 downloaded from the dev website just a moment ago, and just dropping an OVRCharacterController.
    When I build a DX9-x86- PC build, I get a 'Plugins' folder with the DLL but no x86_64 subfolder.
    How can you explain this ? I looks abnormal but I am using the latest SDK, a fresh and clean project and Unity 4.5.2f1... what is wrong in there ?
    Terms & ConditionsAccessibility statement