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.
How to do permanently turn off the guardian system in Oculus Rift S
Hi There has been a problem that guardian would not permanently turn off the guardian(disable boundary) system in Oculus Rift S. I have been trying to turn off the guardian system in all the time,but guardian will be active again although in the settings its still set at disabled. So I had to reset the protection system and disable it again. Recently I have found many reasons for his appearance, because we really want to find a solution .For example: 1)Change the intensity of the light. 2)Change your surroundings (more people is possible). 3)Restart the pc,and so on. There are too many uncontrollable factors, I want to achieve a fully automatic system, instead of manually setting it up again and again. Because there are security protections in reality, I am not worried about the harm caused by shutting down the protection system. I believe we have done a good job.However, the guardian system is leading to this trouble, which we constantly check whether the protection system is active.Of course ,it is unnecessary labor. I have contacted oculus, but there is still no solution.Unable to Enable Rift S Developer Mode
Hello, I am having serious difficulty enabling developer mode on my Rift S Device. I have attempted to search for solutions but insofar have been unable to find any. My developer account is verified. The device is plugged into both USB and HDMI and is fully operational. I have updated the mobile oculus and facebook apps on my phone, and am able to see the Rift S in devices, but there are no options to enable developer mode. I have also used the desktop app similarly to no avail. Is there something I am missing? Please let me know if you have had similar issues or if I am completely missing something. Thank you.RIFT S VIDEO CARD COMPATIBILITY
I just got done with tech support and was informed that my video card is not supported and that is why I have been experiencing freezes and getting the error message that says my computer doesn't meet the updated requirements. I just built this rig 6 months ago and bought the rift S about a year ago so i only have about 6 months use of it. Will there be an update for more supported cards? Ryzen 5 5600X AMD RX 6600 XT 16 GB ram Windows 10
Rift S or Quest 2 for development?
My original Rift is very outdated 😄 Looking at moving forward, would you get Rift S for dev, considering there are going to be a lot of people that still have them, or would you bite the bullet and move to Quest? How long before Meta decides to just change and leave all the devs behind again? Seems a bit unstable to use Meta?Update project in QT 5.4.1 from Oculus DK2 to Oculus RiftS
Hello, I am having trouble updating a project in QT 5.4.1 to use the Oculus RiftS instead of DK2. I already installed the new Oculus SDK, but then I am getting syntax errors in the mainwindow.h (.cpp) and ovrinterface.h (.cpp). If I try the old (year 2012) Oculus SDK's the RiftS is not initilized. Which is clear, because there is no RiftS in the old OVR_Capi.h. Is it even possible to quickly add the Oculus RiftS, or do I have to change the whole project? Maybe some of you have an advice where to start? Thank you!! G007
