Forum Discussion
Many import errors in Unity 2018.3 with Oculus Integration 1.40 (Porting a project to Quest)
I'm trying to get an existing project running on the Quest, so I'm pulling in the latest Oculus Integration from the Unity asset store, and I'm getting a number of errors in the Avatar/Samples/SocialStarter folder (see below):
https://imgur.com/a/JWFwgdA
I can get the project to build by deleting the scripts for that sample, but if I do so, my simple test scene with the OVRCameraRig (set to Quest) and a few props fails to build, with these errors:
https://imgur.com/a/9dIWugi
The most notable error seems to be an argument out of range exception for "length" in OVRADBTool.cs:124
This leads me to believe that something more fundamental is wrong and deleting the scripts that are throwing errors is just papering over the issue. I've reinstalled the oculus integration several times, and rooted out all the old oculus files (the old lip-sync standalone folder, the stuff in plugins, etc) to make sure there aren't old resources hanging around messing things up. No dice.
Any idea what might be causing this issue?
Thank you,
Andre
https://imgur.com/a/JWFwgdA
I can get the project to build by deleting the scripts for that sample, but if I do so, my simple test scene with the OVRCameraRig (set to Quest) and a few props fails to build, with these errors:
https://imgur.com/a/9dIWugi
The most notable error seems to be an argument out of range exception for "length" in OVRADBTool.cs:124
This leads me to believe that something more fundamental is wrong and deleting the scripts that are throwing errors is just papering over the issue. I've reinstalled the oculus integration several times, and rooted out all the old oculus files (the old lip-sync standalone folder, the stuff in plugins, etc) to make sure there aren't old resources hanging around messing things up. No dice.
Any idea what might be causing this issue?
Thank you,
Andre
1 Reply
Replies have been turned off for this discussion
- Looks like I was able to hack it by preventing the line in question from throwing an error, and it successfully builds now, but that does not seem like a... robust solution to the problem.
