cancel
Showing results for 
Search instead for 
Did you mean: 

OVRInput namespace not found in Visual Studio project but compiles and runs just fine

Anonymous
Not applicable
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 7

Anonymous
Not applicable
*bump*

mkirgul
Level 2
*bump*

Dimapolkjui
Level 2
*bump*

Anonymous
Not applicable
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.

Anonymous
Not applicable



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?

Rwkeith
Level 3
*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.

CDawes
Level 4

What fixed the issue for me was: Edit -> Preferences -> external tools -> regenerate project files.