Late to the conversation but wondering if someone could help with this problem: I’m able to get templates to run on the gear vr however the image is not stereo’d
Any ideas? 4.7 Preview 8 gear vr plugin enabled, checkbox ticket, osig file in place (I assume it would not boot in gear vr without that)
Starting any app I see the “please insert into your gear vr headset” dialog upon doing so it loads but no left and right image - only one full screen image which I only saw what was going on after chromecasting first.
For anyone having trouble with deploying to gear vr. Build a 4.7 engine from github. I do not believe preview works and a common thread that I see everyone having issues with deploying is that yall are using preview. Build from github and all your gear vr dreams will come true.
I made a tutorial of the instructions provided by JJ Hoesing, and also included enabling USB Debugging on Note 4, and using your PS4 Controller on Android as an Input Device. I’m so pumped!
Yes I’m having the same issue, everything seems to be installed properly, I tried adding a console command to the level blueprint of “stereo on” but that made no difference. And adding Low Persistance Mode causes the game to just hang (Black screen).
I got this to work with 4.7 stable/binary. You still have to create a C++ project and there are minor differences from the video above and the semi-official instructions from the Page 1. I went with those.
I don’t have a Galaxy GR but tempted to order one. Is it possible to deploy to the Gear via the official 4.7 release without having to build a 4.7 engine from Github first?
You’d be surprised at how quick and easy it is to get your 4.7 build up and running. I haven’t seen posts by anyone suggesting the non-source build works with GearVR. Try giving the build a shot and follow the instructions exactly and you should be up and running very quickly.
Honestly I couldn’t say. For UI you can use UMG to place UI in the world but I haven’t figured out how to interact with it yet (also last I checked it was flipped vertically on the Gear but Epic is looking into that). Otherwise 3D assets just seem to work. When working with GearVR using the Mobile Preview is extremely because it gives you an idea of what complex shaders will approximately look like on the Gear if they even work. I wasted tons of time initially building and deploying only to find certain shaders weren’t working, tweaking and trying again. The DK2 supports pretty much all shaders on the PC but mobile is quite different and the mobile preview is a huge time saver.
I’m not having any issues (outside of the known ones…) with the non-source built 4.7 release downloaded from the launcher. It looks like some C++ is still needed to get the plugin to enable. You can just add a C++ class if you are using a bp based project. Also, don’t forget to create the assets folder with your sig file.
I’ve never created a C++ class in the browser. What does it need to be called & where does it go? And how do you create an assets folder from a “sig file”?
So I still haven’t gotten past the No Stereo View. Part. But in the hopes of good karma coming back to me, so you go in the editor to “File>Add Code to Project” then you get the choose parent class dialog, choose “None”, hit Next, Name your class something, I typically use “MyEmptyClass” so that if I stumble across it, I remember that it’s supposed to be empty. Then hit Create Class. and it should start setting up the class and compile the executable. If you have Visual Studio or XCode installed. If it comes back with success which it should you’re all set, you have converted a blueprint project to have C++ elements, you can continue to use BP to do all your scripting, just now it’s aware of other third party plugins when compiling. (Gear VR is such a device).
The assets folder you have to make, so you navigate to the Unreal4.7 folder not your project folder, then, \Unreal4.7\Engine\Build\Android\Java, and create a “assets” folder in there, and then put the .sig file you get from oculus’ web site, in that folder. It’s sort of a device authentication key file. If you have multiple Gear Vr’s I’d assume you have to put one file for each device ID in there.
Is there anything I have to worry about regarding 2D assets such as sprites and UI when using VR?