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]

    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]

            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.

            Thank you for your feedback guys!
            We are working on the issue, but it is not reproducing on most of our headsets/PCs with similar graphics cards, which makes the issue even more annoying.

            @ThorOfAsgard are you using SteamVR or Oculus Store version of the app?
            Is it the same in both apps?

            @RD3ZEN nice workaround, but for us rollback is not an option.

            Also if you are using Quest headset over Link or Rift with SteamVR please make sure OpenXR runtime is set to Meta Quest both in Oculus Home app and SteamVR settings.

            Hey guys. To gather a bit more structured information could you please answer the following questions?
            This would help us dig deeper.

            • Graphics card, driver version
            • CPU
            • Windows version
            • Headset
            • Runtime (Oculus Home, SteamVR)
            • Connection type (Oculus Link, Air Link, direct connection (in case of Rift or WMR))

            Oculus Store

            • Version of Oculus Home
            • Oculus DeoVR version
            • Which OpenXR runtime in Oculus Home (Settings -> General -> OpenXR Runtime). Must be Meta Quest Link.

            Steam Store

            • Steam DeoVR version

            • For Quest Link, Air Link, Rift, Rift S: SteamVR "Current OpenXR runtime" must be set to Oculus

            • For WMR: SteamVR "Current OpenXR runtime" must be set to SteamVR

            • Add a screenshot of windows Task Manager when the problem occurs, especially GPU section.

            • When it happens?
              a. When you start the app
              b. When you start the app and start watching videos
              c. When you start the app and browse videos
              d. When you start the app, take headset off then back on

              4 days later

              Although the latest Deovr update is not available at my Steam, the performance today was back to normal.

              Hello!

              @iddqd I will try to answer your questions:

              • Graphics card, driver version: NVidia Geforce GTX 1060, Driver version 551.61
              • CPU: Intel Core i7-7700HQ CPA @ 2.80 Ghz
              • Windows version: Windows 10 22H2
              • Headset: Oculus Rift S
              • Runtime (Oculus Home, SteamVR): Oculus Home
              • Connection type (Oculus Link, Air Link, direct connection (in case of Rift or WMR)): direct connection

              Oculus Store

              • Version of Oculus Home: Meta Link App Version 62.0.0.235.346 (62.0.0.235.346)
              • Oculus DeoVR version: 13.15
              • Which OpenXR runtime in Oculus Home (Settings -> General -> OpenXR Runtime): Meta Quest Link.

              When it happens? --> It seems to happen after some minutes running DeoVR and watching videos (not always the same fixed period of time).

              When the issue happens, the CPU seems to go nuts (100%) according to the Task Manager.

              BTW, just in case it could be important, my PC is connected to internet by Wifi (Wi-Fi 5 802.11ac).

              • [deleted]

              Ryosuke1976 Hey, this has been passed to the team and they are looking into it! Appreciate the insights!