Skip to main content
smittyncrew
Participant
June 12, 2024
Solved

Oculus Rift controllers not working in-game after update

6/11/2024, allowed Meta Link to update on my PC for my Rift CV1.  Everything still works until I get into a game.  Once I enter the game, the Touch controllers are not detected when moving, and in the game they are at ground level and will not move.  The Oculus button still worked, and I could use the controllers to select quit app, but they will not move while in a game.  So far I re-installed Oculus, but did not delete all the hidden files.  I updated my Nvidea drivers to the latest 555.xx version. 

    The1stDarkLordMorgothAnswer
    Honored Contributor
    July 8, 2024

    Hey guys! Sorry for the delay in getting back with you. I've been working with the engineering teams trying to get a solution for this issue. HOWEVER, I do want to let you know I've been passing as much information as I can to the them, as well as the workaround that was provided by @8aron. If your issue has been resolved with their method, I advise other users to try this as well. If you're worried about having to do it for every update, I confirmed with the teams, and they told me you can turn off automatic updates for your Rift device. All you need to do is follow the steps below:

    • Go to Settings > Developer > Allow Automatic Meta Quest Link Software Updates > Toggle Off.

    After doing this and following the workaround, you shouldn't have to worry about your headset needing to be updated.

    I've also been asking teams for an official solution from them regarding this issue. I'm not sure when they will be able to get back to me with additional progress updates. Since there is only so much information that I can relay from here on the forums to them. I strongly recommend continuing to submit bug reports and be as detailed as possible with the reports. Even if you think the information that you provide for them might not mean much, any detail that they're given can be of great help to them. I hope this information helps!

    Peace is a lie, there is only passion. Through passion, I gain strength. I gain power. Through power, I gain victory. Through victory, my chains are broken. The force shall free me.
    View in thread

    222 replies

    Show previous replies
    ingefors
    New Participant
    June 22, 2024

    Same problem here, Original Oculus Rift.
    Started right after Meta Quest Link update.
    Controllers don't work in Gorilla Tag and Rec Room, can't move at all.
    They do work in Robo Recall, Oculus first contact, The Wizards.
    Specs:
    Windows 10, Intel Core i5, 16GB RAM, GeForce 1080

      KizKat
      New Participant
      June 22, 2024

      Same issue here (Beat Saber), again after the most recent update 1 day ago. Oculus Rift, Windows 10, AMD Ryzen 9 3900X, 64GB RAM, GeForce 2080. Hope the issue is fixed soon!

        jumpinghungarian
        New Participant
        June 22, 2024

        Just chiming in to add to the pile of users having this issue. So far I've only noticed it with Beat Saber and Rumble, seemingly after the most recent update.

        Hope it gets fixed soon!

          8aron
          Participant
          June 22, 2024

          Here are some steps to hopefully fix everyone's issues. 

           

          Step 1: Download and Set Up Oculus Tray Tool

          1. Download the Oculus Tray Tool.
          2. Set it up and go to the Service & Startup tab.
          3. Stop the Oculus service.

          Step 2: Access and Download the Oculus Runtime Fix

          1. Go to this Reddit post about the recent Oculus VR bug fix.
            • If the link doesn't work, search for "Recent Oculus VR bug DCS Reddit" in your web browser. It should be the first link that appears.
          2. In the Reddit post, click on the purple link titled "oculus-runtime".
          3. This will take you to a Google Drive page. Click on oculus-runtime on the top left of the screen and then click Download.

          Step 3: Extract and Replace Oculus Runtime Files

          1. Extract the downloaded .zip file.
          2. Go to your current Oculus runtime folder. The default file path is:
            C:\Program Files\Oculus\Support\oculus-runtime

          Step 4: Backup and Replace Runtime Files

          1. Move all the files from the current runtime folder into a backup folder.
          2. Copy all the subfiles from the extracted folder (oculus-runtime-20240621T015429Z-001\oculus-runtime) into your Oculus runtime folder.

          Step 5: Restart Oculus Service

          1. Start the Oculus service again using the Oculus Tray Tool and pray it works.

           

          Full disclosure I did run the original steps through chat gpt to help cause I'm not that good at writing instructions. Hope this helps you guys! Please reply if you need any help. 

            Thiagohatake
            New Participant
            June 23, 2024

            I did the procedure and it fixed the problem for me, thank you very much

              NizzleOne
              New Participant
              June 23, 2024

              yup my rift cv1 is broken also, no games recognizing the controllers, they are immobile on the middle of the playspace

                Kerelo
                Participant
                June 23, 2024

                8aron's method works. Meta is truly incompetent trash. What a joke of a company. 

                  haoest
                  New Participant
                  June 23, 2024

                  on the contrary, now you need to dig into your wallet for a newer headset.

                  Kerelo
                  Participant
                  June 23, 2024

                  I resold a quest 2 because it's inferior to the cv1. I can use my superior hmd just fine now, no thanks to meta. 

                    smittyncrewAuthor
                    Participant
                    June 23, 2024

                    If anybody can tell me how to upload to Google Drive or something, I would be willing to post up the one or two files you need to replace.  I just used my CV1 tonight, again, in Walkabout.  It still works.  I suspect that since I only replaced the one or two files mentioned previously, Meta thinks my software is up to date and has not updated again.  The one file for sure is LibOVRRTImpl64_1.dll   I was rushed so I replaced LibOVRRTImpl32_1.dll as well.  Nexusmtz narrowed it down to the first file, but I did replace both.  Let  me know if you all can't find the files.  Sounds like somebody put the entire oculus-runtime folder on Google Drive somewhere.  If you can get that, just pull out the two files listed and try replacing them in that folder (program files/oculus/support/oculus-runtime   If you have time to test it, just replace the LibOVRRTImpl64_1.dll file first. 

                      wogsta100
                      New Participant
                      June 23, 2024

                      Having exact same issues. Been playing Golf Plus consistently for a few weeks. Took 4 days off and now find I cannot play it. Finding it to be the same for all of my other oculus library games. Controllers work perfectly fine in the menu, and register all hand/finger movements. 
                      In games hand don’t even register. Very dissapointing that the update wrecked my ability to play VR. 

                        NizzleOne
                        New Participant
                        June 23, 2024

                        Yeah I was pitching in so meta gets off their ass and fixes it, but I intended on doing the fix on page 7 and now that I have, I can confirm that it works and I can play every game again. Thanks 8aron, and thanks to the universe that someone actually had a backup version on a Google drive.

                        universe 1 / meta verse 0

                          621Lunatic
                          New Participant
                          June 23, 2024

                          Does anyone have a fix for this nonsense or do we have to wait for meta to get off there ass and patch this trash update

                            Show more replies
                            Terms & ConditionsAccessibility statement