-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source solution Unity scripts issue #25
Comments
Hi @TonyViT -- I'm sorry for the delay. GitHub didn't send an email notification for this new issue. Currently, I'm still developing the Hover VR project with Unity 4, but I have experimented with building it with Unity 5. I also had to workaround the Oculus issue you mentioned. Aside from that, I've been able to both build the project for Unity 5, and also to use the released build of the project in Unity 5. The "missing script" issue sounds similar to an issue discussed in the "migration guide" ticket (#21). If so, the solution for this is related to the It's probably a good idea for me to include these |
Ook :) Have a nice day :) Il 01/06/2015 15:05, Zach Kinstner ha scritto:
|
Great! I'll keep this issue open for now, as a reminder to include those Thanks for your interest in the project, and of course, I'm always curious to see what developers are building with it! (And as a side note, developers can refer to the licensing details regarding Hover VR usage.) |
Don't know if it is a known feature or a bug, but...
I downloaded source code from this repository and built the c# solutions. When I opened the Unity project with Unity 5 64bit, two errors popped out: it is a known Oculus bug for Unity5 (fixed in the latest release) inside file OVRMainMenu.cs... so i fixed the file (the known workaround is change World in WorldSpace in the two error lines).
Then the project built... but demo scene did nothing... so I checked... and all the objects in every scene have "missing script" reference for the hovercast scripts. Maybe all .cs scripts files should be copied somewhere else?
The text was updated successfully, but these errors were encountered: