Forum Discussion
Anonymous
5 years agoOVRInput namespace not found in Visual Studio project but compiles and runs just fine
When I import the Oculus integration asset, code completion for the OVRInput namespace does not work ("the name OVRInput does not exist in the current context" in Visual Studio). Yet I can play and build just fine. It's almost as if the Visual Studio solution at the root of the project is not the same as the one Unity uses to build. Is there a way to fix this?
7 Replies
Replies have been turned off for this discussion
- Anonymous*bump*
- mkirgulHonored Guest*bump*
- DimapolkjuiHonored Guest*bump*
- AnonymousFor those still struggling with this problem, it turns out that it was an issue with that particular version of Unity and how it generated solution files. What are the odds? It was fixed in the next release. Current versionsof Unity should no longer exhibit this.
- Anonymous
BartronPolygon said:
For those still struggling with this problem, it turns out that it was an issue with that particular version of Unity and how it generated solution files. What are the odds? It was fixed in the next release. Current versionsof Unity should no longer exhibit this.
It still does :/ I'm running the latest 2019.4.14f1 and the issue is still there...The OVRInput.cs is clearly in the Oculus folder from the Oculus Integration package. Do you have to make a reference to it in your script? - RwkeithExplorer*bump* Using VS Code and Unity 2019.4 release. Compiles fine, but shows reference error.
Edit: It comes and comes. Sometimes when I open another script it'll give reference errors and sometimes it won't. - CDawesProtege
What fixed the issue for me was: Edit -> Preferences -> external tools -> regenerate project files.
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 8 months ago