Forum Discussion

Zeldrid's avatar
Zeldrid
Honored Guest
6 months ago

Screen tearing starting suddenly when connected to pc via link cable (Quest 3S)

Been playing Into the Radius 2, and I've been having to play via the (Meta) link cable as using a wireless connection is another problem in of itself. 

I'll be playing the game and without warning I'll just get the most ridiculous screen tearing, I'm talking horizontal, pixelated square lines that fluctuate and change position, cutting off vision while straining my eyes. When its really bad a whole portion of the screen will become pixelated, imagine the kinda lines you got on the old block TVs from back in the day, but horizontal. 

It stops the moment I stop streaming, which is fine if I want to play a game natively on the Oculus, but the vast majority of my games are on Steam, and so it's basically making the headset useless for me, as I can't actually play any of the games I want.

I've checked the cable, it's absolutely fine and a cable test told me it's working as it should, my PC is more than capable of running these games (and was doing so without issue until the last couple days), going into passthrough and back does not work, and all my drivers and app versions are all up to date.

At this point I feel like I have tried every single thing I can, and I have trawled through so many forums and websites but nothing has worked.

software
Troubleshooting

5 Replies

  • pine.kyne's avatar
    pine.kyne
    Honored Guest
    6 months ago

    I've had this on my Quest 2 since v76. They've refused to officially address it and I've tried a lot to fix it on my end. Going as far as to buy another USB-C ribbon cable and install that. It's not your cable, it's not the USB-C connector, it's their firmware.

    • MetaStoreHelp's avatar
      MetaStoreHelp
      Community Manager
      6 months ago

      Hey there, thank you for contacting Meta Quest Support! 

       

      We understand that Quest Link issues are holding back your Metaverse experience, and we're keen to help sort out your performance problems! First of all, please ensure that your headset's software, Quest Link app, and PC drivers are up to date, as each update will come with it's own fixes and may help with your software issues. 

       

      If you have completed all of your updates, and the problem is persisting, please try the following process to see if this helps! 

       

      1. Start the Microsoft Services Console (Start → Search → services.msc) .
      2. Find "OVRService". 
      3. Right-click "OVRService", select "Properties", and find "Startup type" in the General tab. 
      4. Select "Automatic (Delayed Start)" from the drop-down menu. This option will make Windows wait until all services set to "Automatic" are started before starting the OVRService service. 
      5. Wait 2-3 minutes, click the "Apply" button, and then click "OK".
      6. Restart your PC. 

      We hope this helps, but if the problem persists, we recommend getting in touch with over Private Message as we'll need to gather some more details about your PC build, and we can see what options are available!

      • pine.kyne's avatar
        pine.kyne
        Honored Guest
        6 months ago

        Okay, so... first off OVRService is not the name of any Windows service... There's Oculus VR Library Service and Oculus VR Runtime Service.


        Oculus VR Runtime Service was originally set to automatic and I set it to manual because I am sick of the invasive run all the time route Meta has taken. I humored this step since I already knew this wouldn't affect the tearing/stuttering in the slightest. The client will maybe always start on launch as opposed to it sometimes going into an infinite loading loop now, but it sure as hell did not resolve the tearing/stuttering. Second, even if this does have any affect on the UNRELATED link launch issue, why is this change not even in the PTC for link?

        And third... There's no way in hell I am doing private messages with support. Either you tell your entire community how to resolve issues in these threads, or I ain't communicating with support at all.