Forum Discussion
UE - Quest - Can't Launch on Quest [SOLVED]
Hi, So I followed all instructions (carefully couple of times already) as in official documentation how to setup for Oculus Quest for UE4. However Im unable to launch on Quest: When I g...
Ok, somehow I got it working. Here are some of the steps I performed:
1) Reinstalled again Oculus ADB Drivers, restart Windows (still couldn't see Quest in Launch).
2) Launch > ProjectLauncher > Quest device and pressed Launch. The build started... and errored out on Android NDK (I had it setup earlier with SetupAndroid.bat, so I assumed it knows what it's doing. I guess not).
3) Googled a bit and just changed the NDK path from:
C:/Users/<user>/AppData/Local/Android/Sdk/ndk
to
C:/Users/<user>/AppData/Local/Android/Sdk/ndk/21.1.6352462
4) In ProjectLauncher I pressed Launch (for Quest). Then it errored out on JDK, that my JAVA_HOME path is not setup correctly.
5) I've looked what my JAVA_HOME path is, and it was "C:\Program Files\Android\Android Studio\jre" so I replaced it with JDK path (in UE4).
6) At this point I've closed ProjectLauncher and noticed that I can Launch on Quest (without going to ProjectLauncher). So I'm not sure which step actually helped. But it's working now.
1) Reinstalled again Oculus ADB Drivers, restart Windows (still couldn't see Quest in Launch).
2) Launch > ProjectLauncher > Quest device and pressed Launch. The build started... and errored out on Android NDK (I had it setup earlier with SetupAndroid.bat, so I assumed it knows what it's doing. I guess not).
3) Googled a bit and just changed the NDK path from:
C:/Users/<user>/AppData/Local/Android/Sdk/ndk
to
C:/Users/<user>/AppData/Local/Android/Sdk/ndk/21.1.6352462
4) In ProjectLauncher I pressed Launch (for Quest). Then it errored out on JDK, that my JAVA_HOME path is not setup correctly.
5) I've looked what my JAVA_HOME path is, and it was "C:\Program Files\Android\Android Studio\jre" so I replaced it with JDK path (in UE4).
6) At this point I've closed ProjectLauncher and noticed that I can Launch on Quest (without going to ProjectLauncher). So I'm not sure which step actually helped. But it's working now.