Skip to main content
Fredrum
Up and Coming
October 31, 2016

Trouble getting build for Dashboard working!


Hi All,

I am trying for the first time to upload a basic temp version to the Dashboard and am having trouble getting it to work.

I can see it in my own Oculus client under Library -> Not installed. But it has a cross over it and says 'Not Valid' and I cannot make it install or run.
Probably just some beginners mistake but I cannot figure out what.

I am also unsure whether its because I have not done the entitlement check setup correctly or if it is due to something else.



What I did was:

1. Using Unreal 4.13 on Windows 8.1 I added the 'Online Subsystem Oculus' plugin that was visible by default.
(ie I did not use any downloaded OSS dll's or source at first.)

2. Added a 'Verify Entitlement' blueprint check in my currently only maps Level Blueprint. (for now)

3. I added these lines to the DefaultEngine.ini file
[OnlineSubsystem]
DefaultPlatformService=Oculus

[OnlineSubsystemOculus]
bEnabled=true
OculusAppId=<xxxxxxxxxxxxxxx>    // Using the ID I got from the Dashboard

4. Uploaded zip and filled in the executable name in the browser dashboard.

5. Waited. It seemed to go through the steps ok without errors or warnings.
But I cannot get it to launch from Oculus home.


Does anyone know what I have missed?  Is it true that I shouldn't need the OSS dll's+source now that the plugin comes by default through the Epic engine version?


Cheers
Fredrik
This topic has been closed for replies.

4 replies

brianjew
Participant
October 31, 2016
Hi fred,

On step 4, do you recall which Channel you uploaded to?  There should also be a "Subscribed Users" for each channel.  Did you add yourself to the Subscribed Users for the Channel that you uploaded to?
FredrumAuthor
Up and Coming
October 31, 2016
Hi Brian,

I just 10 minutes ago tried to add myself as Subscribed User and I also Rebooted my machine and then the game had changed in the Oculus client to show the down arrow icon and the text Install!  Great.7
edit:  I used the Alpha channel btw.

But as I clicked to install it did at first seem to run through and do it but at the very end it errored out and asked me to contact Support.

One fishy thing was that the install size, as estimated by client app tile was much bigger that it should have been.
Also that wrong size matched closely the total size of the entire folder in which I kept the .zip file containing the unreal build.

Is there a rule of where I need to keep the .zip file relative to the original local Build directory?


EDIT:  Ok now I'm getting somewhere. I don't know which of the following fixed it but I got it to install.
- I moved the .zip out of the build folder itself.
- Re uploaded this.
- On the oculus app tile icon I did RMB + Details and then from there 'Install'. (as install from the down arrow icon still gave me error)

Now it is crashing out but I think that might have to be due to the entitlement check maybe. I will check on that now.

EDIT2:  Yes it seems like it was the entitlement check that made it crash so I disabled that blueprint node for now. Only select people will have access for now anyway.

But please if anyone can tell me why what I described in my initial post didn't make it work, I'd be very grateful.

 
Cheers
Fred



brianjew
Participant
November 1, 2016
Sounds like you are getting closer.  Is there a stacktrace of the error you are seeing with the blueprint node?  Also could you send a screenshot of how you have the verify entitlement blueprint node set up?
FredrumAuthor
Up and Coming
November 2, 2016

I have been on this most of today and I think I just figured out that it wasn't the entitlement check that caused the crash.

Funnily enough though it was a 'Get Orientation and Position' I had left in one of the Animation Blueprints that caused the crash.
It's odd because that node has been there for months and not caused any problems (even if it was a crappy temp solution) but today it definitely caused those crashes. I just tested repeatedly.

I haven't updated the Unreal version or anything else major so I'm not sure why there's this sudden change in the workings of that node there.

Anyway I think I'm good for now!

Cheers
Fred
Terms & ConditionsAccessibility statement