Solved : No "Package for Oculus Mobile Devices" under Project Settings

LordHar · April 30, 2019, 10:54am

Hey,

I’m using Unreal Engine v4.22.1 wanting to develop for the Oculus Go, following https://developer.oculus.com/documen…-the-oculus-go

At step 13 there is no 'Package for Oculus Mobile Devices" fold to be found.

Having skipped this step, when I build for the headset I get a ‘Launch Failed’ with the following errors:

LogPlayLevel: Error: ERROR: Stage Failed. Missing receipt ‘E:\Visual Projects\Unreal\Unreal Projects\TestCase\Binaries\Android\TestCase.target’. Check that this target has been built.
LogPlayLevel: BUILD FAILED
PackagingResults: Error: Launch failed! Missing UE4Game binary.
You may have to build the UE4 project with your IDE. Alternatively, build using UnrealBuildTool with the commandline:
UE4Game <Platform> <Configuration>

SO yeah, noob in the house. Any help would be very appreciated.
Thanks in advance guys.

Ben_Cykyria · May 1, 2019, 10:42am

The fold should be empty at first. Did you double check “click the “+” to add a new element to the array and select “Oculus Go / Gear VR”.”
Sorry I know this is obvious if you have tried already, don’t have any other idea right now.

If you do not see the fold at all, try clicking the little triangle (arrow) in the middle at the end of the APK Packaging section.

LordHar · May 1, 2019, 11:35am

Thanks for responding,

I’ve attached a screenshot of the options I get. No option for Oculus Go present.

LordHar · May 1, 2019, 4:05pm

Small update : Selected ‘Daydream 3.3 DoF’ and succesfully build and deployed on the Go. Now I don’t know if this is optimal, but it is a start

Ben_Cykyria · May 3, 2019, 7:57am

That’s really strange.do you use the Launcher version of the engine or do you use the custom Oculus branch?

anonymous_user_b580d703 · May 3, 2019, 8:21am

Launcher version, what could be causing it to disappear I wonder

LordHar · May 3, 2019, 8:34am

I’m doing nothing fancy, just build from within the Unreal Editor.

VictorLerp · May 3, 2019, 2:48pm

The GoogleVR options are for Daydream and Cardboard. I believe you’re supposed to use this checkbox for Go/Gear/Quest in 4.22:

ChipironBoy · May 5, 2019, 10:50am

Hello! I have the same problem. I don’t have the option “Package for Oculus Mobile Devices” and i neded for upload app to oculus platform i think. I tryed with v.19 and v.22 version of UE but the option not apear. Some news for this? Ty!

LordHar · May 15, 2019, 10:18am

I finally figured out what went “wrong.”

The version I was using was version 4.22.1 whom I got directly from the Epic Launcher. Turns out, this version hasn’t got the latest Oculus plugin updates.

So if you want to build the latest / working version yourself you have to :

Download and install Visual Studio 2017 (not 2019)

When installing check the C++ and .NET options

Make a Github account.

Follow these steps :
https://developer.oculus.com/documentation/unreal/latest/concepts/unreal-building-ue4-from-source/

Building can take a couple of hours, and when you run the executable it will be stuck at 45% for a short while, doint things in the background.

VictorLerp · May 22, 2019, 9:09pm

4.21 and 4.22 both support Oculus mobile (Quest and Go) natively. Oculus keep their own branch with a more up to date version of their plugin, but that gets merged into our engine updates at frequent intervals.

anonymous_user_23fd35bd · May 23, 2019, 12:05am

Thank you for information.

What does that mean for the development set up ?
I have ue 4.22.2 and the problem described here by LordHar still persists.
Is there another way to fix this instead of compiling the source code ?

Thank you in advance !

anonymous_user_a95cbb2b · May 23, 2019, 7:19pm

I’m trying to distribute to Oculus Quest and I can’t find “Package for Oculus Mobile Devices” . I need to target Oculus quest. Any suggestions.

ChuckDurham · May 23, 2019, 11:13pm

So VictorLerp, if we just checkbox for Configure the AndroidManifest for deployment to Oculus Mobile, we can skip the Oculus steps in the tutorial (assuming they are using the Oculus build of Unreal), I am using 4.22.2

rasamaya · May 29, 2019, 12:09am

cdraptor and mateo-spectra
see post 8, thats basically the only thing you need that deviates from the oculus-unreal guide. It works fine without compiling a new version of the engine.

anonymous_user_a95cbb2b · May 29, 2019, 2:00pm

I checked the box for Oculus deployment. See image attached. But when I am packaging, the manifest get v1 signing scheme instead of v2 signing scheme. I want to know how to make it use v2 signing scheme for Oculus Quest.

anonymous_user_8f87bfcf · June 18, 2019, 11:28pm

I am getting the same issue as the original poster. Also, I am trying this on a Mac.

anonymous_user_886519d51 · July 8, 2019, 3:54am

It

It sounds logical, but I was faced with this unexpected dumb problem. Why would they have such a long path it it doesn’t work?! I’m using a 64 bit machine btw.

anonymous_user_886519d51 · July 9, 2019, 8:17am

I found out that you need to install this in a short path within Windows. Mine wasn’t that complicated, but I guess you really name to make sure is close to the drive root folder

matty_matt_mattmatt · July 27, 2019, 11:01am

anyone know how to get this working because the new quest update doenst work with my app anymore with the method in step #8