What's wrong with deovr?

[deleted] @Kieshi

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.

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

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

Cheered too soon, it is crap again.

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

@[deleted] Hello guys. Do you casually have any news regarding this issue? Were the dev team able to figure out the cause? Thank you.

At least for me the bad artifacts are gone after the last update.
I cant really say anything to the problem with the bad performance, because I never noticed it.

Ryosuke1976 Still nothing I'm afraid. I've been passing on all new details that I find and if someone sends them over to me.

Hi,
I changed 2 things yesterday and got the problem fixed for me. I do not know yet which of those 2 was crucial so I will just post both:

1. In Steam I switched the SteamVR version from current version to "temp_v1.27.5" Beta. This was mentioned in some Steam post to help with performance issues in general. You can change the version somewhere in the settings in Steam itself.
2. Inside SteamVR you can downscale the resolution in the options. I set it to 50%. This was also said to improve performance in some post.

Trying these out might hopefully help someone.

Xinffert Hey, this is very useful information, I have passed this to the team to see if this information will help them approach this problem from a different perspective!

@[deleted]

Hello, any news regarding this bug? It's been more than 3 months since I have been paying my subscription (actually, 4 if you count this month too) and I am still unable to use the app. I totally understand you are trying your best to have the issue fixed (no doubt here), but the thing is I am spending money in a product I cannot enjoy and I am beginning to get used to it, so I am also thinking about cancelling my subscription, asking for a refund for all these months and moving on to another provider, or maybe coming back in a future when there is a nice offer (like Black Friday).

I am sorry if this message sounds aggresive, it is not my intention. I am also an IT engineer and I can understand how frustrating can be trying to solve a bug whose cause cannot be found. But I also thought it was fair to let some steam out and letting you know how I feel about this (and I guess I am not alone here).

I hope we can have good news soon. Kind regards.

[deleted] Hi! Thanks a lot for the reply. I am using the DeoVR version from the Oculus Home. Could you please ask the developers if the fix is also valid for Oculus Home users or if I should use the DeoVR version from SteamVR? Thank you!