Unreal Won't Launch To Oculus Quest 2 Without Restart - unreal-engine4

I'm using Unreal 4.26.0 and I finally got it to launch to my Oculus Quest 2. However, it doesn't always launch the latest version.
So, I might make a change, build the project, then launch the app on the Quest via Launch => Quest 2.
Eventually, it starts running on the headset, but often it doesn't have the latest changes. If I shutdown Unreal, then restart it, it does get the latest version.
How do I consistently have it launch the latest version of the app? Is there some formula for getting it to properly copy over during launch? Thanks in advance.

I did find the solution... just in case someone else has this same problem:
I did not have all the environment variables set correctly for Android/Java. I had to make sure all these were set:
JAVA_HOME
ANDROID_HOME
ANDROID_TOOLS
ANDROID_PLATFORM_TOOLS
ANDROID_NDK_HOME
So, after making sure each of those were specified, I also had to put each into my $PATH.
I should also note that I'm using Unreal 4.26, Android SDK 10, and Android NDK 22.0.7026061. These aren't exactly what the directions call for, but the directions are a bit old. These are (mostly) the newest versions as of this writing.

Related

Freeze on Copying APK file

I created a new empty project, switched platform to Android and started Build and Run. But when it comes to "Copying APK File to device" it just freezes and I have to restart Unity.
I installed Android SDK & NDK tools just before that (through Unity Hub). Android Build Support was installed by me manually a while ago so it was visible as installed in Add Modules window. I did not do any changes to the project. The most interesting thing is that the apk is built in my Builds folder. Not sure if it works though.
I am using Unity 2019.1.0f2. The device Android version is 9.0 (API level 28) and the minimum API set in Player is 16, so the problem should not be with API.
Does anyone know possible reasons for it?
Try to turn off the following setting on your android device.
Settings -> Developer options -> Monitor apps installed by ADB
This setting(if turned on) will ask a verrification if you want to install the app. It feels like this cuts off the connection with unity which causes it to get stuck.
Unplugging and replugging the device seems to work aswell. In case of big projects this is anoying tho since if you are to quick it will just say it lost connection and it will ask if you want to reconnect, which in turn causes the same problem.
This is the only answer that worked for me:
https://answers.unity.com/questions/1248123/build-run-apk-freezes-on-pushing-content-only-one.html
In short, Player settings -> Publishing settings -> Split application binary
First of I would ask you on what computer did you run this on? (performance wise)
Second you can just copy the .apk file to the phone and install it there. If you got to where it prompts for copying to android your apk file is fine and built.

This app is incompatible - on installing apk build on unity

When I run my game through Unity Remote 5 it works well, but when I build the apk and try to install it on my device, it shows app is incompatible, I have tried changing many settings in player settings section but nothing worked for me. What can be done with this problem?
I am using unity 2017.3, the Android version on phone is 7.0 (Nougat) (I also tried on oreo but didn't work either), minsdk version in player settings is set on the marshmallow and target SDK version is on highest installed.
I have had this problem before. Maybe you can try removing the app you just have installed and trying to install the new version.
But you should complete your question with more information as someone comented.
Hope it works!

Unity Hololens project missing SDK (that is certainly installed)

I made a stackoveflow account just to post about this since it's been bothering me for 3 days time (tinkering after work so not much time every day). And this is my first post so please be forgiving if I break a few rules :)
My problem is that after I have installed and configured everything and I have followed the official guide I get these errors thrown by VS
I have researched as much as I can and still nothing. Things I have tried:
Reinstalling VS
Reinsatlling and manually installing the Windows 10 SDK
Adding all the sdk folders to the Path Env. Variable
Rebuilding the project
Building a new project
Changing the version of the UWP
Has anyone else had this issue or know a way to fix it? I really want to start developing for MR after doing a ~10 page documentation on why its the most promising technology...

Unity crashes on Launch

I have installed latest version of unity(5.6.0f3) from https://store.unity.com. Every time i try to launch the unity I get unity bug reporter window popped up.I am not able to create a new project or use unity. I uninstalled latest version and installed unity 5.3.5f1 version. But still I am facing the same problem.
Maybe memory problem in your pc, try to end task of anything running even google chrome (because it takes a lot of memory) and then run Unity as administrator.
It can be also that your windows is 32 bits and you wanna run Unity3d 64 bits.
I hope this helped you ;)
I also faced the problem like this.
In my case this bug reporter appeared when I tried to open the "unity-3d-simplefps-master" project downloaded from GitHub.
So I renamed the source folder name and I just avoided this bug reporter.
Best wishes!

Unity3D is crashing when hitting play – and when Oculus is on

I am using Unity 5.2.2f1 with the Oculus Rift and Windows 7. Everything was working well till... one hour ago. I first ran a build that played smoothly. I then moved away from my computer; when I came back, it was shutting down. Upon turning the computer back on, Unity started to crash anytime I hit play and the Oculus is on. If the Oculus is turned off before I start Unity, everything works perfectly. This is the link to the Unity Editor log.
This is part of the log, where the crash happens:
Completed reload, in 0.636 seconds
Initializing Unity.PackageManager (PackageManager) v5.2.2 for Unity v5.2.2f1
(...)
Native extension for OSXStandalone target not found
Native extension for WindowsStandalone target not found
Native extension for LinuxStandalone target not found
Native extension for WebGL target not found
Native extension for SamsungTV target not found
Native extension for Tizen target not found
Native extension for Android target not found
04/22/16 19:07:47: [CAPI] LibOVR module is located at C:\Windows\system32\LibOVRRT64_0_7.dll
(Filename: C:/buildslave/unity/build/Runtime/VR/Oculus/VRDeviceOculus.cpp Line: 46)
Crash!!!
SymInit: Symbol-SearchPath: 'C:/Program Files/Unity/Editor/Data/MonoEmbedRuntime;.;C:\Users\vcladmin\Documents\maze;C:\Program
(...)
#Programmer, I have used System Restore as you suggested.
The suggested restore point was at an install of "Dell update", right at the time of the crash. Proceeding with the restore, I realized that the NVIDIA driver was being restored from an old version (266), to the newer version (358) (that's the version I need to make the Oculus work). After the restore everything went back to normal. Then I tried to install Dropbox. After the install, the computer turned off again and, like before, once restarting, the Oculus was not working anymore. I checked the Oculus setup and it said it needed a new NVIDIA driver. So something is happening that makes the NVIDIA driver go from 358 to the old one. I don't understand why. What would you suggest?
A friend told me that probably the "Dell Command update" thinks that the new NVIDIA driver is the wrong one, so it restores it to the old one every time it updates. We have disabled automatic Dell Command updates.
Thanks for the help.