UE 4.26.0 - Oculus Quest 2 - Project launches (kind of) OK, doesn't start on Device

I also can not get the game to Launch from UE 4.26 to Oculus Quest 2. I am testing with the default VR template. Just a black screen, it doesn’t look the game actually launches. I see no errors or warnings. 4.25.4 worked fine.

*Edit - The above issue was because I forgot to enable Android SDK Writing License or whatever when I created a new project for migration. It still crashes on load unfortunately.

LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 0 failed (-1003)

^^^ That and something about the Steam VR Chaperone not happy.

Oh and intermittent between those there is the Android Gradle error. This one is easily solved by deleting the Android files in the Intermediate folder. Then back to all the other errors.

I understand that you don’t get the error messages for materials not found. This might mean that you are a tad closer to a solution. It still won’t find some materials without adding their directory specifically, but that may be a macOS quirk.

At first, 4.26 wouldn’t open a copy of my 4.25.4 project at all. It would crash at 95%. I got it to open by creating a new project in 4.26.0, gutting it of everything and then migrating my whole project (from the top content folder) to that new project.

With the new project that I have created for testing, I can now create a widget and a stereo layer in it and have it to launch correctly in 4.26.0. What it wouldn’t want to do earlier (crash upon opening) was to to deal with an imported widget that had bindings and scripts attached.

It just tells me that it can work, but it’s an ordeal.

I wish the packaging process was more robust in general. Packaging to VR is even more fragile than usual (which is already extremely fragile). About a third of my time is spent kicking the packaging process until the game gets out running. If I ever am able to expand as a game company, my first hiring will be someone to manage the packaging process so I can continue developing while they hash out the onslaught of stupid little issues keeping the game from packaging/running. I wouldn’t of guessed that would be the case. /End rant

I finally launched to Oculus Quest 2 from ue 4.26. I have been able to launch (successful 4 times now) after unplugging a Collision Enabled node. I had a sphere collision and a node simply turned the collision from off to on using Set Enabled Collision (Query Only). Unplugging that node allows me to launch, plugging in the node causes the launch to quit a second or so after launch with the following errors:

LogPlayLevel: Error: 12-29 10:55:42.256 16266 16300 D UE4 : [2020.12.29-18.55.42:256] 0]LogStreaming: Error: Missing Dependency, request for /Script/SteamVR.SteamVRChaperoneComponent but it hasn’t been created yet.
LogPlayLevel: Error: 12-29 10:55:42.256 16266 16300 D UE4 : [2020.12.29-18.55.42:256] 0]LogStreaming: Error: Could not find class SteamVRChaperoneComponent to create SteamVRChaperone_GEN_VARIABLE

LogPlayLevel: Error: 12-29 10:55:44.619 16266 16424 D UE4 : [2020.12.29-18.55.44:619] 0]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 0 failed (-1003)

I have no idea what the connection is between the collision and those errors (or if I am mistaken somehow) but as of now I am launching.

Im not sure why that error is triggered with the Collision Enable node, but I believe that error is because of the steam references in the Motion Controller Pawn. I had to removed any blueprints referencing steam to fix something like that.

Update, I am getting the Accessed None Steam VR Chaperone error again. Sometimes it pops up and sometimes it doesn’t. I know SteamVRChaperone is a component in the motion controller but I don’t know why it gives me the error when it does or why it doesn’t when it doesn’t. Sometimes it crashes when overlap collisions are spawned, sometimes it crashes a second after the game starts and sometimes it works fine.

After deleting the SteamVR component, I can get into the game but am crashing on any spawning of overlap collisions. It does not appear to be related to a widget but I can’t verify that for certain now. This set of errors occurs when a collision overlaps:

LogPlayLevel: Error: 12-29 20:09:49.938 20176 20242 D UE4 : [2020.12.30-04.09.49:938] 31]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 0 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.941 20176 20242 D UE4 : [2020.12.30-04.09.49:941] 32]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 1 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.945 20176 20242 D UE4 : [2020.12.30-04.09.49:945] 33]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 2 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.954 20176 20242 D UE4 : [2020.12.30-04.09.49:954] 35]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 3 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.957 20176 20242 D UE4 : [2020.12.30-04.09.49:957] 36]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 4 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.966 20176 20242 D UE4 : [2020.12.30-04.09.49:966] 37]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 5 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.971 20176 20242 D UE4 : [2020.12.30-04.09.49:971] 37]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 6 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.978 20176 20242 D UE4 : [2020.12.30-04.09.49:978] 39]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 7 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.983 20176 20242 D UE4 : [2020.12.30-04.09.49:983] 39]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 8 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.986 20176 20242 D UE4 : [2020.12.30-04.09.49:986] 40]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 9 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.991 20176 20242 D UE4 : [2020.12.30-04.09.49:991] 42]LogHMD: Error: FOculusHMDModule::GetPluginWrapper().BeginFrame4 10 failed (-1003)
LogPlayLevel: Error: 12-29 20:09:49.999 20176 20242 D UE4 : [2020.12.30-04.09.49:999] 43]LogHMD: Error:

*Update: a slightly older version of the same project is launching without error in UE 4.25.4. I am gonna rebuild back to where I was in the 4.26 copy. The collision overlaps that appear to crash 4.26 work fine in 4.25.4. I also get no warnings or errors about the SteamVR Chaperone even though this older file has it in.

Print strings are causing crashes for me in 4.26 on Oculus Quest

A victory and a defeat (but the concern I expressed at the top of this thread is solved).

I can now launch with UE 4.26.0 on the Quest 2. It is stable (stereo layers included). What solved the issue may not be necessary in a future release. It could well be a solution for me alone. I have no external reference apart from what I read in the usual forums.

I identify three factors in my solution :

  1. I have to include “OculusVR/Materials/” in the Project Settings > Packaging > Additional Assets Directories to Cook". This may be unique to my setup. I will not investigate this further unless it turns out to be a problem again in the future.
  2. Stereo layers and widgets must not be components of the Pawn. Again, I suspect this is some peculiarity of my setup. Widgets and layers as Pawn components worked fine in 4.25.4. It helped advancing toward a solution in this process because it was possible to see something in the Quest 2 after moving widgets and stereo layers in a separate BP. It is not said that I could not move them back in the pawn structure now that the whole thing seems to be fixed. I won’t try to see anytime soon unless it is needed. I suppose it would work now, but that’s nothing empirical or scientific.
  3. I have to use the Project Launcher and set Build > Shipping instead of Development. I believe Build has to be selected in the upper right corner of the section as well (not Detect automatically – I can’t be sure it’s optional but it works when set at Build). Launching from the toolbar icon will go all the way, but instantly crash in the Quest 2.

So, this is what it takes for things to work for me with UE 4.26.0 and the Quest 2 on (macOS 10.15.7 – Android Studio 3.5.3 – Xcode 12.3).

Now, the defeat :

  • The morning following the preceding finding of a solution, the Quest 2 display went black. Tried everything. I’m waiting for Oculus to fix this and it doesn’t seem like it will happen fast. But, that’s another story and I will post about it in the proper Oculus forum.


Hi guys,
can someone kind would share a simple scene converted /built to apk? I would like to test an apk that works for sure with my Quest 2.

Thank you.

Nemsi! This thread is not a good place to ask that question. Tea For God by void room

I was able to resolve this by disabling print strings (Console command ‘disableallscreenmessages’ on begin play will do the trick) (cheers xadamxful) - Might be related to Stereo Layer weirdness upTheo is mentioning.(Print strings happen on their own layer)


I’m new to the Q2 and starting my tests with the template project and on 4.26 experiencing the same issue (issue being 3 looping dots with a black scene).
Trying a few things now and will report back with results.

Worst case I guess I’ll test on 4.25. Something has to work…

I’ll also add that I can’t seem to use the “Launch” feature to deploy and run with the device connected to unreal. It never finishes the “Building” state and gets stuck trying to open the activity it seems. Anyone know anything about this? I’ll probably start a new thread on it if I can’t get anywhere.


Quick update and something odd.

I made a new VR Template build on 4.26 set up everything but decided to leave Mobile HDR checked.
The template worked, I could mess around in the motioncontroller map.

Then I decided to uncheck Mobile HDR, restart editor, and try again.
Looping 3 dots.

Then I tried to check Mobile HDR, restart and still had looping 3 dots.

Perhaps something that 4.26 does isn’t really doing a good job with the restart there but still just making sense of this.


Due to a mistake on my part for packaging to the wrong folder, I had used the build that had Mobile HDR disabled.

In short, keeping Mobile HDR enabled allows the unreal VR template to run well on the Quest 2 with no looping dots and a black screen.

That said I haven’t done further testing with print screen but might be related.

Also might be worth checking out some Oculus Specific VR samples since they recommend turning Mobile HDR off.

Hello, I stumbled upon your discussion because I had 80% of your issues for some days until I solved for my Quest 2! I followed step by step this tutorial:

Have to say that worked on a blank project, so… I guess my answer won’t be so useful if you have an entire game ready :frowning: sometimes I recover much of the work by migrating the maps in a new project.

Hope you all solved your packaging errors in the meanwhile

Have same issue on 2.26 , every screen debug message like (Print string, show fps or load level with not builder light map “light map needs to be rebuilt”) immediately crush game. This error on quest and quest 2 same.

Looks like a bug has been submitted - Oculus Quest Crash after I call "Print String" node - UE4 AnswerHub (the picture on the answerhub thread might help Shardfer with his game getting crushed)

Hi, I have similar issue, got a Q2 try to use it on 26.1 I have a project which runs good in 25.4 but when I move on 26 I get the 3 dots and grey screen when it runs there is no errors in the log. I try to play with the sdk version number the build setting and I got it to run in with different setting but I always get the grey screen with all of those. I’m using a Mac, but I don’t see that causing issue with previous version. Dose anyone find a solution yet?

1 Like

Hi, I’m getting that exact message in device output log when my project fails to launch.

#00 pc 05dc65e0 /data/app/com.YourCompany.FouTwoSix-0VUUJ4peETxbWVN9b9xarQ==/lib/arm/ (TRefCountPtroperator=(FRHITexture2D*)+40)

Do you have any idea what is causing this?

I keep getting the error listed at the top here: [4.26] Cannot package for android - #7 by Svit_Drift_M

I have updated my Android Studio (API 29) as is the suggested answer but it didn’t help

Hey all, I have had issues with the 3 dots in the past, Always seemed to be some kind of missing texture or material being the cause. For me WorldGridMaterial missing from being cooked was the cause of my game never making it. If in doubt make a new blank level and set that level as the Startup/Boot Level and see if you can get past the looping dots.