Skip to main content
Participant
February 18, 2019
Solved

Which should I be using now in Unity Oculus Integration, Oculus Utilities, or both

  • February 18, 2019
  • 6 replies
  • 1746 views
I'm kind of confused as to what I need to be using when developing in Unity, as far as I can tell The current Oculus Integration on the Unity Store is supposed to be the combination of some of the SDK downloads here, kind of a single source for all.  When I go through different blog posts or YouTube videos (both official and otherwise for both) there's a lot of reference to Utilities, and the scripts that they reference are not part of the Integration.  Obviously, since utilities are still listed as a download here, I could always just use that, but I also see that it's not going to be updated, only the stuff on the unity store is which is just Integration.  So I suppose I should learn the new stuff, but the materials I'm using to learn with are not "translating" well.
This topic has been closed for replies.
Best answer by mousebear
@MPeters-xw Welcome to the Oculus Developer Forums!

The Oculus Integration package in the Unity Asset Store is what you're looking for, as it now contains all of the packages you need. Previously, these packages were independent (Avatars, Platform, Utilities, Framework, etc.), but now it's been simplified to one package (allowing you to pick and choose what to import).

6 replies

Up and Coming
February 21, 2019
use the integration it has most of the old stuff from what i noticed only difference is they re organized everything into different folders but im also kinda new, so i could be wrong ... but anyway i got a couple objects into unity and im able to pick them up and stuff so im makeing progress ... if you need help on anything u can message me whenever you want
mousebear
mousebearAnswer
Honored Contributor
February 21, 2019
@MPeters-xw Welcome to the Oculus Developer Forums!

The Oculus Integration package in the Unity Asset Store is what you're looking for, as it now contains all of the packages you need. Previously, these packages were independent (Avatars, Platform, Utilities, Framework, etc.), but now it's been simplified to one package (allowing you to pick and choose what to import).
If you need immediate help or want additional support/context on an issue you are having with our platform or integrations: 1. Gather any and all logs , screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.) 2. Please submit a ticket here through the "Contact Us" link (include what you've gathered in step 1). 3. Tag me @mouse_bear once you have done so!
MPetersxwAuthor
Participant
February 21, 2019
@NinjaGaijin could you look over the blog post "Easy Controller Selection" I'm having issues following the directions as typed out with where I can find assets. In particular OVRPointerVisualizer.cs file. I don't see it in the package.

Edited message based on the suggestion below.
February 21, 2019


NinjaGaijin, could you look over the blog post "Easy Controller Selection" I'm having issues following the directions as typed out with where I can find assets. In particular OVRPointerVisualizer.cs file. I don't see it in the package.
"use the little @NinjaGaijin
to summon him"

MPetersxwAuthor
Participant
March 13, 2019
@NinjaGaijin It's been a few weeks since I made this post, I'm still trying to find out what happened to the OVRPointerVisualizer.cs file as described in the blog.  I'm just trying to do some basic stuff here (as I'm newish to the development arena), so the concept of "Easy controller selection" seems like a good way to go about it, just it's not so easy right now.
mousebear
Honored Contributor
March 13, 2019
@MPeters-xw Thanks for your patience with this! There is a Unity Package you can download (split into three parts) that contains this script here: https://developer.oculus.com/blog/easy-controller-selection/
If you need immediate help or want additional support/context on an issue you are having with our platform or integrations: 1. Gather any and all logs , screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.) 2. Please submit a ticket here through the "Contact Us" link (include what you've gathered in step 1). 3. Tag me @mouse_bear once you have done so!