Huge performance drop when switching from Rift S to Quest 3

[Qcumber]

19 minutes ago, Lange_666 said:

But it does work so why not using it?

How do you get link cable to work through vd? Doesn't it need third part software? 

[Lange_666]

Worked fine with my Pico, can't remember the details, returned the Pico more than a year ago.
Since i have a DP connected headset, i uninstalled everything regarding VD.

[Qcumber]

1 hour ago, Lange_666 said:

Worked fine with my Pico, can't remember the details, returned the Pico more than a year ago.
Since i have a DP connected headset, i uninstalled everything regarding VD.

VD does not support cable link as meta have not released the coding. The only way to connect via a cable now is by an ethernet adaptor which only helps with regards poor WiFi connection. 

[DST]

Okay, the solution I found for myself was to set "45 Hz" in ASW Option in the Oculus Tray Tool. Then I set framecap of 72 in Nvidia Control Panel, and now I have that smooth performance again that I enjoyed in the Rift S. With a framerate of 36 and ASW enabled works better for me than everything else. I know a lot of folks here always turn ASW off, but I´m afraid with my graphics card I still need this crutch, otherwise I get stutters all around. Open XR Toolkit unfortunately provided no big difference, with "Turbo mode" on I got also stutters, but in a somehow "different" way, it´s hard to describe but still way worse than with ASW on.

I also have DLAA as anti aliasing, makes picture quality a bit blurry, but thats ok, I can live with it. The same with the artifacts that ASW create sometimes (this is a bit more visible now due to better Quest 3 Displays I guess), but overall image quality is still improved compared to the Rift S. I guess I can live with that for now.

But thanks again for all the advises.

[Tomcat388th]

I know that you have a Q3 but here are my Oculus Debug Tool settings that I use with my Q pro if they will help any

J