H.264 Video is unstable on Quest 3 (black screen/freezing) - No issue on Quest 2
Hello! Our team has been developing a 360 video-based app for Quest (using Unity game engine). After getting Quest 3 headsets, we've discovered evidence that video playback is unstable on the Quest 3, when we had no issues on the Quest 2 with the same APK build. Specifically, the H.264 codec is not stable on the Quest 3 and we are having issues with the video either turning black when paused (via AVPro Exoplayer Unity plugin), or not being able to resume playing after being paused (via the built-in Unity video player or Meta Quest TV app). The H.265 codec appears to work just fine, however we aren't always able to use this format and we want H.264 to work. The issues for H.264 are present both in our Unity app and also in the Meta Quest TV app, indicating this is a hardware/OS-level issue with the decoder for H.264 video only on Quest 3, and not on Quest 2. I have been able to prove this via Android Logcat error messages I have captured while playing video (see below). Below are my observations when testing video playback on the Meta Quest TV app, Unity via AVPro, and Unity via the built-in Unity video player. The below is consistent when using either 8k (7680x3840) or 5.7k (5760x2880) 2D (equirectangular) 360 video at 29.97 fps. MetaStoreHelp or Ryanality could you please pass this important information along to the appropriate engineering teams? *NOTE: I am unable to post the full information in this post because my post gets marked as spam if I do, presumably due to the long length of my post. As a workaround, I have posted the information over on the AVPro Github. Please see here for all of the full information, including Android Logcat error messages: https://github.com/RenderHeads/UnityPlugin-AVProVideo/issues/1660#issuecomment-1762244929Problem with MediaProjection and permission dialog
Hi Im new to oculus development (Oculus Quest 2) and im trying simple app for making screenshots and screen recording. But im having a problem with permission to retrieve MediaProjectionApi I start activity for result, and the standard android dialog for permission shows but, but without allow/deny buttons, so im stuck. This is the dialog, sorry for the phone pic, but build in screenshot does not show this dialog. Found simmilar issue here https://github.com/rom1v/sndcpy/issues/75 but no solution either. My code for showing this dialog. This is in my MainActivity and the testMediaProjectionPermission method is call as onClickListener from a button. ActivityResultLauncher<Intent> resultLauncher = registerForActivityResult( new ActivityResultContracts.StartActivityForResult(), new ActivityResultCallback<ActivityResult> () { @Override public void onActivityResult(ActivityResult result) { if(RESULT_OK == result.getResultCode()) { Log.d(TAG, "Media projection permission granted"); MediaProjectionManager mediaProjectionManager = (MediaProjectionManager) getSystemService(MEDIA_PROJECTION_SERVICE); MediaProjection mediaProjection = mediaProjectionManager.getMediaProjection(result.getResultCode(), result.getData()); Log.d(TAG, "Successfully retrieved mediPerojeciton="+mediaProjection); } } }); private void testMediaProjectionPermission(View view) { MediaProjectionManager mediaProjectionManager = (MediaProjectionManager) getSystemService(MEDIA_PROJECTION_SERVICE); resultLauncher.launch(mediaProjectionManager.createScreenCaptureIntent()); } Any advice would be appriciated. Any kind of workaround or another option to record screen other then the build in caster.
Unity 6000 - Head tracking issue
Hello, After newest version of Unity 6000, i have issue with head tracking. Every time i create new project, import Meta XR All-in-One SDK(Currently 65.0 v, same with 64.0), everything works fine, except head tracking. when i do exactly the same with unity older version (for example 2022.3.15f1) tracking works. there are few things i can mention. during launch, frame rate is like 72 FPS, when normally its 600+ gives two errors and a warning. all i do is install unity editor(right now its 6000.0.2f1), create empty project(Clean project without anything), import SDK and launch. -----------------------------------------Error SerializedObjectNotCreatableException: Object at index 0 is null UnityEditor.Editor.CreateSerializedObject () (at <26627f99a7af447db68cd5961117dc4a>:0) UnityEditor.Editor.GetSerializedObjectInternal () (at <26627f99a7af447db68cd5961117dc4a>:0) UnityEditor.Editor.get_serializedObject () (at <26627f99a7af447db68cd5961117dc4a>:0) OVRManagerEditor.OnEnable () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/Editor/OVRManagerEditor.cs:39) -----------------------------------------Error Saving Prefab to immutable folder is not allowed: Packages/com.meta.xr.sdk.interaction.ovr/Editor/Blocks/InteractableItems/Prefabs/[BB] Pokeable Plane.prefab UnityEditor.AssetPostprocessingInternal:PostprocessAllAssets (string[],string[],string[],string[],string[],bool) -----------------------------------------Warning Your project uses a scriptable render pipeline. You can use Camera.stereoTargetEye only with the built-in renderer. UnityEngine.Camera:set_stereoTargetEye (UnityEngine.StereoTargetEyeMask) OVRCameraRig:EnsureGameObjectIntegrity () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRCameraRig.cs:603) OVRCameraRig:Awake () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRCameraRig.cs:190) Any clue?
Quest Pro eye-tracking not working: "com.oculus.bodyapiservice keeps stopping"
I've recently struggled with the eye-tracking function in Quest Pro. Have followed all the suggestions in this forum and still can't have it work. I have downloaded the latest Movement SDK sample, and configured all settings (OVR camera rig; XR plugin management; Oculus plugin setting; Andriod manifest; Oculus App in windows PC). However, I get the app error "com.oculus.bodyapiservice keeps stopping" on the headset. I can either select close app or app info from there. While the "close app" option lets the scene run, the eye tracking/face tracking is not working. Meanwhile there is no error in the unity editor or debug log. I saw people had similar issue very recently and can't to find a solution. I wonder whether more people are experiencing the same and know what might be the problem? Debug and version info: Unity V2021.3.15f1 Oculus XR Plugin V3.2.2 Oculus Integration v46.0 OVRCameraRig - Quest Features (Eye & Body & Face Supported, tried Required too) OVRCameraRig - Permission Requests on Startup (Body & Eye & Face) Thanks, Shu
OSC/WebSocket/MQTT to Quest
Hi there, I'm trying for a few days to have something working on UE4.27 and I'm hitting a wall. I've made a blueprint where i'm able to receive OSC input data from a remote laptop to a UE4.27 app that then triggers an event (for now print something or play a specific audio cue). It works flawlessly on UE4.27 but as soon as I load the project onto the quest and send that same OSC input data it crashes the app on the Quest 2. I tried different ports, data formats but still the same behavior without much logs to learn from which make me wonder if the Quest forbids such incoming IP communication ... could someone confirm whether or not Oculus Quest accepts remote information (regardless of the protocol used). Maybe I'm missing something in the settings somewhere but I couldn't find much information about it. Thanks for your response
