Get Oculus Identity returns No Logged In user
I try to get my ID with GetOculusIdentity node but it fails and prints out LogOnlineIdentity: Warning: Oculus: Failed Oculus login. Not currently logged into Oculus. Make sure Oculus is running and you are entitled to the app. Also tried Get Oculus ID and it also returns No logged in user I run Verify Entitlement before and it succeeds, I have the correct appid of my game in my DefaultEngine.ini and the account passes authentication9.4KViews4likes14CommentsOculus Quest 1 not generating rec.upipelinecache file
Hello, I'm trying to implement ue4's native PSO system into my project. Right now it won't cache and generate the rec.upipelinecache file nor it's associated folder CollectedPSOs. Even when I manually create the CollectedPSOs folder. I've followed UE4's own tutorials for Gathering PSO Data and Enabling PSO Caching. The only deviations have been the Gathering PSO Data's step 5, where I select Android and Android_ASTC instead of Android and Android_ETC1. However nothing I've tried so far has resulted in the rec.upipelinecache file generating in my Quest's folders. Is there something these two tutorials neglected to mention or do I need something else to set-up the PSO caching? Is it even possible on the Oculus Quest? Here are the links to the aforementioned tutorial pages: https://docs.unrealengine.com/en-US/SharingAndReleasing/PSOCaching/GatheringPSOData/index.html https://docs.unrealengine.com/en-US/SharingAndReleasing/PSOCaching/EnablingBuildingPSOCaching/index.html5.2KViews2likes6CommentsUE4 + Quest : FPS drop when running a release version of the app for the second time
The first time a shipping version of the app is launched, everything runs fine and we're hitting 72fps on the Oculus Quest. However, immediately after a restart of the app, there's always a consistent drop in framerate (~10fps lost) This seems to happen only when we create a release version for distribution, and not when we build a regular shipping build. Has anyone else noticed this happening ? FYI we're running the Oculus branch of Unreal Engine 4.22.1 Quest build settings for Arm64+ES3.11.3KViews2likes2CommentsUnreal bugs/errors with Rift/Go/Quest and their status
I've made a list of current bugs/errors encountered in Unreal when developing for Rift / Quest / Go. Some can be somewhat fixed / avoided, some are still very present. I encourage people to add to the list or bring their solution. Would be great also to have input from @NinjaGaijin and @Ross_Beef on their possible ETA or resolution. ;) This is up-to-date with latest Unreal (4.22.2) Oculus integration found on github, dating back from June 7. There it is: 1. Retrieve Oculus ID and Verify Entitlement fail on Go/Quest a. STATUS: can be fixed by changing a line in OculusIdentityCallbackProxy.cpp. See at the end of list for complete solution. b. Reference: https://developer.oculus.com/bugs/bug/2343978258981741/ 2. Entitlement fail on Quest if no access to Quest API a.STATUS: can be fixed by commenting out a line in OculusMobile_APL.xml. See at the end of list for complete solution. 3. PlayDynamicForceFeedback has errors when nativizing assets a. STATUS: can be fixed by changing \Engine\Source\Runtime\Engine\Classes\GameFramework\PlayerController.h line 1053 private to public, because 'PlayDynamicForceFeedback' is a private member of 'APlayerController', for reasons unknown b. Reference: https://answers.unrealengine.com/questions/831405/playdynamicforcefeedback-node-in-420-fails-to-cook.html ; 4. Oculus Go/Quest : No VOIP / or no LipSync with Oculus Avatars a. STATUS: NOT FIXED b. Reference: https://developer.oculus.com/bugs/bug/471102320355137/ ; c. Background infos: Android only allows access to the microphone from a single process. This wasn't an issue when networking avatars previously, as the mic input wasn't being used. But with the expressive update, we specifically need to run the mic through the OVRLipsync plugin to generate blend-shapes and drive the mouth shapes. Trying to hook up the mic to both VoIP and Lipsync therefore causes an inevitable race condition. The loser gets a bunch of zeros. So either there's no networked audio, or no blend-shapes. 5. Multiplayer Oculus Avatar is broken with official Oculus Avatar Plugin a. STATUS: NOT FIXED b. Use our in-house patched plugin/template, or use Photon Engine 6. Oculus Rift / S: Enabling Splash in Project Settings / Oculus Settings crash when loading next level a. STATUS: NOT FIXED b. Use blueprints to Set and Show Splash Screen 7. Stereo Layers are transluscent in ES3.1 (Oculus Go/Quest) / Vulkan (Oculus Quest) a. STATUS: NOT FIXED 8. Performance issues when a Render target is added to Spectator screen (VR) in a packaged game a. STATUS: FIXED IN 4.23 b. Reference: https://issues.unrealengine.com/issue/UE-70352 ; c. IN 4.22, don't use Spectator Screens, or use them only in editor: 9. Cannot access Oculus Quest platform features a. STATUS: You have to be greenlighted by Oculus before doing so or Oculus Business users will have access to Business Suite Q3-4 2019 10. When a stereo layer is present rendering a widget it cannot be destroyed. a. STATUS: NOT FIXED b. Reference: https://answers.unrealengine.com/questions/829084/stereo-layer-isnt-destroyed-on-end-play.html ; c. Avoid using stereo layers if you need to destroy them 11. Quest: Oculus Avatars and Oculus Audio use 32-bits Android libraries (armeabi-v7a); no arm64 librairies available a. STATUS: NOT FIXED b. Use 32-bits librairies on Quest if using Oculus Audio and/or Avatars3.5KViews2likes11CommentsError when trying to build for Quest using OSS Oculus and always leads to crashes.
I'm using Unreal 4.26 binary from the Launcher, and every time I try to build my app with OSS Oculus enabled I get the following error; To me it seems like it's always running the Windows version of the OSS and not the Android version, even tough I specify the build to be for Android_ASTC. This error does not stop the build process and a package is made, I can run it on my Quest, but it always crashes on start. If I remove the OSS it works perfectly. I'm working on a multiplayer project so the OSS (Online SubSystem) is needed. I tried changing the code and rebuilding the OSS Oculus removing all the "#if PLATFORM" to try and force it to always use Android but had no results. Any help guys?847Views1like1CommentStereo Layer Transparency broken for UI Widgets on Quest
To improve the quality of our in game UI, we recently moved it from world space widgets to Stereo Layers. However, transparent Stereo Layer have black backgrounds on the quest where it is supposed to be transparent. After setting up the stereo layer, so that it gets live textures from the Unreal UMG system, the transparent parts appear black on the Quest. So here how it looks on the Quest: And how it looks on the PC with oculus link and VR preview in engine (this is how it is suppose to look): The issue only pops up with Live textures, if I place a sprite with alpha channel as the texture, it is displayed correctly with alpha blending. One thing we have already tried is creating the render target in C++ and ensuring that the clear color has the alpha of 0, so (0,0,0,0) and the format supports RGBA. We are on Unreal version 4.25.3 on the Oculus Unreal Branch built from source. Any tricks to get this working? Thanks for the help! Daniel5.3KViews1like5CommentsOculus quest multiplayer for UE4
Hello, i want to develop oculus quest multiplayer app, with the sessions, host and listeners. How i should to develop multiplayer with Oculus SDK? Coz in the steam, i can find a lot of tutorials how to connect SDK, how to do a host or listener, via blueprints (it's great and easy) c++, and other parts. It's will be good to have tutorials how setup Oculus SDK (i think from Oculus UE4 version) how to do a multiplayer setup with oculus documentation, a simple multiplayer project or video tutorials (will be the best for UE4 devs, coz we like blueprints and visual parts) it's will be helpful.1.1KViews1like1CommentFix for Quest packaging Oculus Integration 1.39
I put it in another post but to be clearer: Use the following manifest changes: Also since Oculus integration 1.39: 75Hz is not available with Oculus Quest, only 60 and 72Hz; this bug has been introduced in Oculus plugin 1.39 and is not yet fixed466Views1like0Comments