Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
bcoyle's avatar
bcoyle
Adventurer
7 years ago

Oculus GO | build & run, black screen

Not sure what to do - I've been trying to build and run some basic scenes that come with the Oculus Integration package and every time I get a black screen. Several home button presses will pull me out of the demo and then I can proceed back into the unknown sources application which just goes black again. No apparent issues during build...

If I hit the play button I'm able to preview the scene on the Rift fine.

I also tried using side-loader software from Headjack to install the .apk onto the GO, but again it launches a black screen.
Oculus Go
Unity

7 Replies

Replies have been turned off for this discussion
  • citizen12's avatar
    citizen12
    Protege
    7 years ago
    I find that with every new version of Unity I need to go through a short checklist to make sure that I can build and run a trivial Unity app on my Go.

    1.  Create a new Unity 3D project (do not use LWRP).
    2. Import the Oculus Integration 1.32 Asset Store asset.
    3. Make sure your Player settings are correct for Go.
    4. Add the Oculus/VR/Trivial scene to your Scenes in Build.  Select Android, specify ASTC textures, Gradle.
    5. Build and run.
  • bcoyle's avatar
    bcoyle
    Adventurer
    7 years ago
    @citizen12
    You think I should download the latest Unity? Currently I've been using 2017.3.1p4 - hmm. I like your checklist. Pretty sure I hit most of those on the checklist, as I did create a new project for testing Oculus GO, and ran through all the Oculus guides on settings for Unity/Android setup. At least I think I hit it all...

    Maybe I'll get the latest Unity and run through it again. Hoo boy.
  • citizen12's avatar
    citizen12
    Protege
    7 years ago

    bcoyle said:

    @citizen12
    You think I should download the latest Unity? Currently I've been using 2017.3.1p4 - hmm. I like your checklist. Pretty sure I hit most of those on the checklist, as I did create a new project for testing Oculus GO, and ran through all the Oculus guides on settings for Unity/Android setup. At least I think I hit it all...

    Maybe I'll get the latest Unity and run through it again. Hoo boy.

    All I can tell you is that I am actively working on a Go-based project using 2018.3.0f2 and that checklist was the first thing I checked.  FWIW I am using Single-pass rendering. 

    Good luck!
  • BisiteOculus's avatar
    BisiteOculus
    Explorer
    6 years ago
    Here somebody with the same problem, I will say something if I get this problem solved
  • JayWSloat's avatar
    JayWSloat
    Honored Guest
    6 years ago
    I experienced this recently and it was quite frustrating. What helped me sleuth the issue down was manually running a command from a terminal to install and run my apk file. In this mode, when the running of my apk failed, I could see the status it returned, and quickly determined that the cause was that a version number of a previously installed "DeleteMe.apk" was higher than the version I was currently trying to push onto it. Raising the version number caused everything to work in my case.

    >adb devices
    List of devices attached
    1KWPH810068137  device

    adb.exe -s "1KWPH810068137" install -r "Z:\Unity_Projects\OCULUS_GO\Sofa\Temp\DeleteMe.apk"
    adb: failed to install Z:\Unity_Projects\OCULUS_GO\Sofa\Temp\DeleteMe3.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]

    -Jay-


  • Sethius's avatar
    Sethius
    Explorer
    6 years ago

    Unfortunately, I am still having my issue and I have no idea how to even start sleuthing it out. It is very similar to what you described "black screen after launch" however I can hear the audio from the game playing. Another difference is that if I deploy it as a side-load then it works correctly, it only fails in this manner when I try to install it as an alpha build via the marketplace.

    Does anyone have a suggestion as to how I can try and figure out what the problem is? Is there a tool I can run to listen to/print out any errors that might occur during a run of a non-sideloaded install?

    -Rob