Skip to content
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

Closed
TonyViT opened this issue May 6, 2015 · 3 comments
Closed

Source solution Unity scripts issue #25

TonyViT opened this issue May 6, 2015 · 3 comments
Assignees

Comments

@TonyViT
Copy link

TonyViT commented May 6, 2015

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?

@zachkinstner zachkinstner self-assigned this Jun 1, 2015
@zachkinstner zachkinstner added this to the Near-Term milestone Jun 1, 2015
@zachkinstner
Copy link
Member

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 .meta files for the Hover VR DLL files. As a quick workaround, please copy the DLL-related .meta files in the latest release package and paste them into your project.

It's probably a good idea for me to include these .meta files in the repository itself, so that developers who are creating builds don't run into this issue. By the way -- the release builds (linked above) should provide the files you need in case you don't need to perform these builds yourself.

@TonyViT
Copy link
Author

TonyViT commented Jun 1, 2015

Ook :)

Have a nice day :)

Il 01/06/2015 15:05, Zach Kinstner ha scritto:

Hi @TonyViT https://github.com/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
#21).
If so, the solution for this is related to the |.meta| files for the
Hover VR DLL files. As a quick workaround, please copy the DLL-related
|.meta| files in the latest release package
https://github.com/aestheticinteractive/Hover-VR-Interface-Kit/releases
and paste them into your project.

It's probably a good idea for me to include these |.meta| files in the
repository itself, so that developers who are creating builds don't
run into this issue. By the way -- the release builds (linked above)
should provide the files you need in case you don't need to perform
these builds yourself.


Reply to this email directly or view it on GitHub
#25 (comment).

@zachkinstner
Copy link
Member

Great! I'll keep this issue open for now, as a reminder to include those .meta files in the repository.

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants