Skip to main content
jrod914
Participant
August 3, 2016

Oculus Standard Package to Unity

I downloaded Oculus's Standard Asset Package for Unity 5 from the Oculus Downloads page and imported the package into my project but when I went to 'run' the project I was hit with an error message saying, "all compiler errors have to be fixed to enter playmode". I imported the package directly from Oculus>Development>Downloads and have not altered them in any way so I have no idea why this error is occurring. When I delete these packages and run an alternate script I've created the game runs just fine. I only receive error messages when I use Oculus's Standard Asset Package. Please help. Any help will be much appreciated.


Ultimately I'm looking to use Oculus's Character Controller in my Unity game in hopes that the Oculus Rift can control the character's movement direction and not just the looking direction.
    This topic has been closed for replies.

    10 replies

    cybereality
    Inspiring
    August 3, 2016
    This should be in the Unity forum in the Developer section (I'll move it). You can switch sections from the drop-down menu on the top right.

    What version of Unity are you using? Did you download the correct package? If for Unity 5, you should use the Oculus Utilities for Unity 5. I don't recall there being any errors.
    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
    jrod914Author
    Participant
    August 3, 2016
    I'm using Unity 5.4.0f3 (64-bit) and I downloaded the Oculus Utilities for Unity 5 v1.6.0
    vrdaveb
    Inspiring
    August 3, 2016
    It sounds like one of your scripts isn't compiling. The utilties compile for me on 5.4.0f3. Can you share %LOCALAPPDATA%\Unity\Editor\Editor.log?
    jrod914Author
    Participant
    August 4, 2016
    Yes @vrdaveb, I've attached the log below.
    vrdaveb
    Inspiring
    August 4, 2016
    I don't see an error in that log, but it does look like you are using Intel HD graphics, which will not perform well in VR. I assume you are building for Gear VR. Can you please send a log where the error actually occurred?
    jrod914Author
    Participant
    August 4, 2016
    I intent to build for GearVR as well as Oculus Rift. I've attached the log with the error below.
    vrdaveb
    Inspiring
    August 4, 2016
    > Assets/Standard Assets/CrossPlatformInput/Scripts/AxisTouchButton.cs(3,19): error CS0234: The type or namespace name `EventSystems' does not exist in the namespace `UnityEngine'. Are you missing an assembly reference?

    This isn't related to VR support. It looks like you are using older Standard Assets with 5.4 and they no longer compile with the new API. Can you delete the Standard Assets folder and re-import the packages you need? Looks like you need the cross platform input package.
    jrod914Author
    Participant
    August 4, 2016
    I don't believe I'm missing any assembly references, but I could be wrong. I just got a new computer and all that is installed on it is Unity and Oculus. From there I imported a project I created on another computer, which used Unity 5.3.5f1. Maybe the problem is coming from creating the project in another version of Unity on another computer? I did delete the standard asset package that came with the version of Unity I got on the new computer and tried to import just the Oculus Standard Package but still had no luck. I've attached the editor log below. 
    jrod914Author
    Participant
    August 4, 2016
    Also where would I need to look to find the cross platform input package?
    vrdaveb
    Inspiring
    August 4, 2016
    > I imported a project I created on another computer, which used Unity 5.3.5f1.

    This is the problem. The "Are you missing an assembly reference" question is just part of Unity's compiler error message.

    > where would I need to look to find the cross platform input package

    See https://docs.unity3d.com/Manual/HOWTO-InstallStandardAssets.html
    Terms & ConditionsAccessibility statement