Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums will be revoked at the discretion of Oculus staff.
New to the forums? Click here to read the How To guide. -- Developers click here.

Upgrading Oculus Utilities from 1.22 to 1.30

konzeptzweikonzeptzwei Posts: 9
NerveGear
edited October 2018 in Unity Development

Hello there!
I have some issues with my old Oculus integration and I want to upgrade to the newest version via the unity asset store. I already tested the new integration in a clean project and realised that the folder structure seems to be different than the old one. Everthing is now stored in the Oculus folder and not anymore in different OVR folders which is quite neat BUT i wonder how i am supposed to upgrade my old project without problems.

Thanks for your help!
Christopher

Comments

  • imperativityimperativity Posts: 3,587 Valuable Player
    edited October 2018
    @konzeptzwei

    Thanks for tagging me. Yes, we introduced a new folder structure for this integration some months back for practical reasons more than anything.

    We have exact documentation here detailing the steps you need to take to upgrade your version of Oculus Utilities. Let me know if you encounter any issues in proceeding.
  • konzeptzweikonzeptzwei Posts: 9
    NerveGear
    well quite frankly i don't get the documentation exactly. i have the folders but the content i have to delete isn't there.

    Folder

    Content to Delete

    Assets/Plugins

    Oculus.*

    OVR.*

    Assets/Plugins/Android/

    *Oculus*

    AndroidManifest.xml

    I have none of those subfolders/ files in their respective folders...

    I have folders in the assets folder like: OculusPlatform, OVR, Ovr Avatar, Ovr Harness and OVRInspector that do not get adressed at all in the documentation you're mentioning.

    now i am even more confused. it's late in germany and i wonder what i don't get?


  • EtienneArchambaultEtienneArchambault Posts: 2
    NerveGear
    I just want to add my voice to this question since I have the exact same question! I think the documentation requires some updates. t seems to predate the now obsolete file structure.
    Thanks for addressing this!
  • imperativityimperativity Posts: 3,587 Valuable Player
    @konzeptzwei

    @EtienneArchambault

    Let me reach out internally and see what guidance I can offer and for insight on documentation updates to reflect this new structure.
  • konzeptzweikonzeptzwei Posts: 9
    NerveGear
    edited October 2018
    i (we?) would really appreciate that. development is pretty much coming to a halt right now...
  • konzeptzweikonzeptzwei Posts: 9
    NerveGear
    any news on the issue? to clarify my "old" installation was oculus utilities version 1.22 so just tell me what i have to do to update to 1.3X!

  • EtienneArchambaultEtienneArchambault Posts: 2
    NerveGear
    @imperativity
    sorry to stack the flags, but clarification on this front would be really appreciated!
  • imperativityimperativity Posts: 3,587 Valuable Player
    @EtienneArchambault
    @konzeptzwei

    I've reached out internally for guidance on addressing this but have not received an exact solution to this issue. I am going to try and reproduce this behavior myself next week once I'm back from Unite LA. Thanks for your patience here.


  • konzeptzweikonzeptzwei Posts: 9
    NerveGear
    @imperativity any news? it's now over three weeks...what's going on? I really need to upgrade NOW! If there is NO way to upgrade I will do the implementation from scratch which will burn a lot of time but it's better than to be in this limbo state! so please come back to us and give us a strategy here!
  • imperativityimperativity Posts: 3,587 Valuable Player
    @konzeptzwei

    I've just made two internal tasks to address this issue. I could not manually migrate from a 1.22 project to the newest structure as our previous download link for it is redacted from our downloads portal. I'm going to have our documentation team look into addressing this immediately. Thanks for your patience here.
  • konzeptzweikonzeptzwei Posts: 9
    NerveGear
    hello there! any news? do i have to send you the 1.22 project so that YOU can check it out? just drop me a line...

  • Bucket-HeadBucket-Head Posts: 6
    NerveGear
    I'm having similar issues. New projects have Oculus Utilities 1.31, however, in my old project I'm stuck at 1.29. Perhaps the reason may have to do with the Oculus Integration package we are using. The new projects are using the latest Oculus Integration, but my older project is based on an older version. I need to find out how to upgrade to the latest Oculus Integration; simply re-importing it didn't work. I'm going to open a new thread to ask how to upgrade a project to the latest version of Oculus Integration. 
  • btelmanbtelman Posts: 2
    NerveGear
    edited December 2018

    I was able to get it a build to the device from 1.21, but it shows a black screen before the splash screen and is spamming logs about this.

    "W/TimeWarp: WarpToScreen: Nothing valid to draw"

    Running an empty scene in the same project does the same thing.

    Running a new project with only Oculus Utilities works with the same unity version.

    Upgrading project to 2017.4.X (2017.4.15f1 specifically, but any 2017.4 might do it) makes the current project with issues work again with minor issues.

    Old setup
    Unity v2017.3.0f3, Oculus Utilities v1.21.0, OVRPlugin v1.21.0, SDK v1.1.11.0
  • btelmanbtelman Posts: 2
    NerveGear
    edited December 2018
    Was able to replicate my issue in a clean project with 2017.3.0f3
    Import Oculus Utilities from here
    https://developer.oculus.com/downloads/package/oculus-utilities-for-unity-5/1.21.0/
    Import Oculus Platform from here (Might not be needed, but is what I used for testing)
    https://developer.oculus.com/downloads/package/oculus-platform-sdk/1.20.0/
    Make sure to select Oculus as VR SDK

    Once imported into the new project, build and run a sample scene on the device to make sure it works (Oculus Go is what I used)

    Now upgrading.
    1. Close Unity
    2. Delete all files in the Assets directory
    3. Open Unity
    Import latest Oculus Integration from Asset Store (1.3.2)
    Restart editor after upgrade like it asks

    Build and run the sample scene now.

    Unity never shows the splash screen, remaining black, and the home button has to be spammed to exit the app.

    If I should post this elsewhere, let me know.


  • konzeptzweikonzeptzwei Posts: 9
    NerveGear
    @btelman
    I think you have a different issue and probably you just should post as a new one?

    actually this thread was just about upgrading a legacy installation with different folder structure to the newest unity-asset–store-only integration.
  • konzeptzweikonzeptzwei Posts: 9
    NerveGear

    Hello there!
    I have some issues with my old Oculus integration and I want to upgrade to the newest version via the unity asset store. I already tested the new integration in a clean project and realised that the folder structure seems to be different than the old one. Everthing is now stored in the Oculus folder and not anymore in different OVR folders which is quite neat BUT i wonder how i am supposed to upgrade my old project without problems.

    Thanks for your help!
    Christopher

    @NinjaGaijin
    hello there! @imperativity never helped us on this issue and now I have to get on your nerves. do I have to submit a ticket for this? 

Sign In or Register to comment.