Rift S owners who had the Displayport issue and FIXED it: How?
Picked up a Rift S recently and it refuses to work because of the well-known displayport issue. I've already submitted a ticket, but I thought I'd try to gather info from the community as to which fixes worked and which didn't. The specific issue I'm talking about is where after connecting the Rift S, both connections will seem OK for a few seconds, but then the Displayport disconnects and you're left with one of these status screens in the Oculus app: There's plenty of speculation as to the cause of this issue and no official word from Oculus as far as my research goes, the most likely culprits seem to be a power delivery issue where the headset is drawing too much power for the USB port to keep up (which, for some reason, causes an issue with the DP connection rather than the USB one), a bad cable, or a software/firmware issue caused by the 2019 update that brought Facebook integration to the Oculus app (this is, again, pure speculation, but there are a few articles that suggest these issues became more prevalent when that update dropped) The behavior is the same for every "plug-in procedure" as Oculus describes it: Connect the USB3 cable, wait 10 seconds (the LED between the lenses goes from off, to amber, to white, and stays there- nothing from the displays themselves), connect Displayport. Here's everything I've tried so far, collected from forums and other sources: Rebooting Reinstalling Oculus app Disabling power-management USB suspend options Disabling USB suspend on USB devices through Device Manager Updating video drivers Reinstalling video drivers Reinstalling video drivers using DDU and Safe Mode to fully wipe the previous driver Running C:\Program Files\Oculus\Support\oculus-drivers\oculus-driver.exe , which starts silently and doesn't pop up any kind of status window, which seems like a bad way to design software but whatever Connecting the headset through every available USB 3.0 and USB 3.1 port on my computer, using the proper "plug-in procedure" each time Connecting a single monitor through HDMI rather than Displayport or DVI Disconnecting all other non-essential USB devices Checking the seating of the connectors on both the computer side and headset side Checking the integrity of the cable, connectors, and headset, for kinks/frays/etc Unplugging audio devices from the headset Here's what I've seen online, but haven't been able to try yet: Using a dedicated, powered PCI-E USB 3.0 card, specifically the Inateck KT4001 as (apparently) recommended by oculus support Using the above card but with different drivers (the ones that come with it, the ones Windows installs automatically, whatever "Fresco" drivers are, etc) Using a powered USB 3.0 hub Replacing the cable Replacing the GPU Replacing the entire headset Replacing the entire computer The fixes I haven't been able to try seem hit-or-miss, though the PCI-E card seems to have worked for some. So here's my question to you, Rift S user who's fixed this issue: What did you do? What has worked out for you? If your headset worked and then suddenly didn't, do you remember around what time it happened or what you did around that time? If your answer is "I stopped using a cable extender" or "I stopped using a mini-DP to DP converter" or whatever else, that answer doesn't apply to this issue. This issue is specific to the Rift S in its intended setup, with no dongles or adapters involved. Once again i've already submitted a ticket and am working through the issue personally, this isn't me asking for solutions, it's me asking for experiences from people who had this issue and got it fixed.
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.
