@ThorOfAsgard I understand your frustration of being stuck with such issue, I'm/was? in the same situation and as you I was convinced that a rollback to a previous version could help.
Here is how I proceeded to install a previous version, not straightforward though (there might be an easier way but that's the first time I had to do it, so I gathered information and tried):

  • Download Oculus downgrader,
  • Install .NET 6 if you don't have it already,
  • Following Oculus downgrader guide:
    • Run Oculus Downgrader.exe (if the program closes immediately that's probably because you don't have .NET 6. If you have it but still don't run, open a cmd prompt to see a message of the problem),
    • Type n (No) when being asked to log in (I tried to log in first but it didn't work for me - program crash)
    • Then type Y (Yes) to get a guide for retrieving your access token from the Oculus app itself. The steps are well explained in this page,
    • Once you have your token, you must paste it in Oculus downgrader wich will encrypt it (I did it but later when I tried to download a previous version of DeoVR I was getting an error of not being authenticated, but continue to read, there is a solution),
  • Then type 11 to run the Direct execute command,
  • Then open this page listing all the DeoVR versions (the page is quite slow to load),
  • Click on the Download button of the version you want to install. I'd chosen the 13.12.2.1 from Novermber 14, 2023 (you can find the patch notes of all versions and their release date in this page),
  • Copy the command line arguments shown in the dialog in step 2. and past it in Oculus downgrader and hit Enter.
    For me it was d --appid 1004289456346194 --versionid 6524092777699140 --headset rift --token <paste-your-token> (appid is the DeoVR app id, versionid the version of the app to install and I added the token parameter where you should paste your token retrieved previously in the Oculus app otherwise it was still complaining that I was not authenticated despite the previous steps done),
  • Hopefully you will be more lucky than I was because the download failed multiple times for a few missing files, so I repreated the operation a few times (stoping - restarting Oculus downgrader and it finally succeded to download)
  • Then it will ask you if you want to start the "game", answer Y (Yes) then hit Enter if your Oculus app are installed in C:\Program Files\Oculus\Software (this is the default) so it will move the downloaded DeoVR app there:
  • The app will then be located in C:\Program Files\Oculus\Software\Software\infomediji-d-o-o-deovr-video-player where you can find and run the DeoVR.exe file at any time.
  • I had also disabled the auto-update in the Oculus app in Settings > General > Auto update Apps as I was not sure if the downgraded version of DeoVR will replace the already installed one or if it will seat next to it. And I think it was the right move because today when I started the Oculus app it was saying that a DeoVR update was available (13.14.1) from my current one (13.12.2.1).

Hope this can help you!

    DeoVR team is working hard to make things work. We expect seeing improvements with every new release from now on

      RD3ZEN Thanks very much. More helpful than SLR. Making us wait 2 months when they could just give us an older version while we wait is absurd.

        • [deleted]

        • Post #68

        ThorOfAsgard The reason why we are not providing the older version is that we can't vouch for its stability and that all features will work as expected. We understand that this performance degradation issue is causing you inconveniences but like @doublevr said, the DeoVR team is working on fixing it. They used the logs other users sent over to try to replicate it and understand what is happening, but this is something that is quite hard due to a lot of hardware combinations, and not all of them are affected by this.

            [deleted] Its not just inconvenience, its literally unusable with the pixelation. It doesnt matter to me if you cant vouch for its stability as long as i can get something that works to any degree until you guys can get your proper fix. This is pretty simple and it doesnt make sense why not. You may be working on fixing it, but having 2 months of only being able to download, no streaming, is ridiculous and is a perfect reason to give us a temporary fix. How difficult is it to provide a link to an older version. As for hardware combinations, both my 1080 ti and 4070 ti super had the same issue. For about 1 month everything was just slowed down like everyone has been saying, but a few weeks ago it started to pixelate (both gpus) and now its unusable.

                ThorOfAsgard For me, downloading the videos is not a solution either. The "lagging" issue happens whether I am streaming videos or playing local ones.

                    Ryosuke1976 Yup and i have no issue with other players like heresphere and playavr. Im gonna ask if i can get months credited for all this waiting. This is bad customer service with an unusable product.

                      5 days later

                      [deleted] Hello! I saw you have released a new DeoVR version today. Could you possibly let us know if it includes the fix for the issue we are experiencing? Thank you!

                          • [deleted]

                          • Post #74

                          Ryosuke1976 Hey, the team advised installing the latest version and testing if the issue is still present. Again, the team couldn't get to the main cause of these performance degradations but they performed some changes to the code hoping that will resolve the issue you are experiencing.

                          Please do let us know if the issue is still there though!

                              Not fixed at all. It still has horrible artifacting (vertical pixels or lines move when there is movement). Its also still fully using my 4070 ti super. Playing 8k videos in heresphere doesnt even get close to maxing out my GPU. Like 30% or so for 90fps on quest 3 resolution.

                              The one thing i will mention though is when it was fully unplayable with total pixelation i didnt realize i had h.264 selected. When i switched to h.265 the complete pixelation went away, but it still artifacts and maxes out my GPU.

                              I seriously dont understand why you are so hesitant to explain to us why you cant figure out that this problem started as soon as the early december update. This is so obvious that is the cause, whatever was changed in that update. Just roll it back sheesh. Thats the first thing to try.

                              PS: It is still unusable using quest air link (which i prefer for certain things), only virtual desktop makes it work a little bit better.

                              the newest update didn't help. BUT I found something out when I was testing. And it solved the problem for me. It isn't a perfect solution, but it helps for me. To be honest, I found out about this by accident.
                              I tested it again and again and was able to reproduce the issue again and solve it again.

                                well, I know this was very frustrating for all of us, but try this:
                                I took out the battery of one move controller (oculus rift S), because I had to change the battery, I noticed the App runs smoothly, and that fixed the issue pretty much immediately. I didn't even have to restart DeoVR. plugging in the battery for both controllers causes the issue again after 2-3 min playback, then I took one battery out, voila, everything works fine again. controller with inactive mode or sleeping mode doesn't help, I HAD to take out the battery on one controller.
                                I hope this hint helps you and of course the developers to fix this permanently.

                                  Hi,
                                  I just wanted to add my name to the list of people who are currently disappointed by not being able to use Deo VR at the moment. Nothing mentioned above has helped so far. Using an HP Reverb G2.

                                  Seriously, SLR team, i have asked many times and have not received a descriptive response. Why cant you give us an earlier version to use!? (a version before early december, that is definitively when this started, right after that update!!). This is seriously infuriating. And if you cant, can you please tell me, with detailed reasoning, why you cannot?

                                    • [deleted]

                                    • Post #83

                                    Damankogel38 Hey, we've passed this to the devs! What we know so far is that Oculus performed some small changes in their SDK which the team wasn't aware of and they thought it was about the input system but your post can potentially help narrow this down!

                                    ThorOfAsgard As I previously mentioned, we are unable to provide the previous version of the DeoVR app as we can't guarantee stability and that other updates the team implemented in the player would work. I mentioned above on the controller post that this issue was caused by the SDK changes that the team can't fully understand what they were and they implemented some changes with the DeoVR app 13.15 which they thought it would resolve this but it still hasn't so they continued to work on this. I also have to mention that there are a lot of users who are contributing in finding a solution to this and we are very grateful for that as this helps developers a lot, so I would once again ask if you can provide us with any logs from your end other than a spec of a PC that you're using, that would really be amazing.