- Home /
Oculus Integration v1.39 and Unity 2019.2.0f1
A couple weeks ago I built an APK for Oculus Quest using Unity. It was a build of the Oculus Integration package’s SampleScenes. This build worked, it was rather buggy but it worked.
Then a few days ago they released a new version of Unity (2019.2.0.f1) and a new version of Oculus Integration (v1.39). Since the updates, I have been unable to get the new versions to create a functional build. I can output an APK using the Oculus Integration samples, but it does not run properly. When I load and run the APK on the headset It opens and runs the first scene (StartScene) with no problems but when I try to open the next scene it crashes.
It’s important to note I have touched none of the code. I started with and empty 2019.2.0f1 shell set up for android and VR. Then I downloaded and installed theOculus Integration Package v1.39 from the Unity Asset Store. I simply took the sample scenes provided by Oculus and loaded them into a build. I had to adjust the Player Settings but one would think this should work. I had it working a few weeks ago.
Also the test build I did for Oculus Integration, that worked and was on the headset, no longer functions properly at all. I did not reload it or touch this file in any way.
I feel Like I’m missing something. But what?
Answer by Spookytooth3D · Oct 15, 2019 at 02:16 PM
I am having a similar issue where none of the sample scenes from Oculus Integration allow for the controllers to work as expected. In fact, they are not even showing up. I know they are being tracked as they can break the planes of the virtual barrier. My hunch is that the latest firmware update from Oculus has changed something that is breaking the Oculus Integration functionality. Hopefully someone will get to an answer on this quickly.
I could not get the newest version of Unity (2019.2.6f1) to work with the Oculus (1.40) set up. I had to use the previous version of Unity (2019.2.0f1) in order to build a functional Quest project.
There is a new version (1.41) of the Oculus Integration Package out today (Oct 15, 2019) That may solve the problem (I have not tested with it yet):
https://assetstore.unity.com/packages/tools/integration/oculus-integration-82022
I'll give that a try and repost here. Thank you!
So, long story short... on both $$anonymous$$ac and Windows systems, using previous versions of Unity, the latest Oculus Integration tools appear to not be working properly.
On my $$anonymous$$ac, I am using 2019.2.0f1 with Oculus Integration 1.41. This does not work currently with out of the box configurations. (sigh)