diamond26

I have a 3080 12GB and Quest2 (details in my signature) and I'm happy with performance. Either on 72 or 80hz. In difficult maps, like Normandy 2 over Paris or London or South Atlantic over towns, ASW kicks in without many artifacts. In MP scenarios depends on how heavy the server is, situation is a bit different but in any case I'm always able to keep FPS above the minimum of half requested rate (36fps for 72hz or 40fps for 80Hz)

This is the latest from ED

Things are very simple. Try to run MT without or with any argument you prefer, if you see in DCS.log anything other than OpenXR then you have your answer. By OpenVR I mean the Oculus native API. In ST regardless of having Oculus running as the OpenXR runtime you can have either Oculus native API when you don’t have any arguments or OpenXR if you use the OpenXR argument. In MT you can’t have this option.

Unfortunately as I am using MT, OpenVR ( or native Oculus API) is not compatible with MT. With or without command line, MT runs OpenXR, which of course is fine for Meta Quest headset but is limiting the options.

To my experience this is the case. No OpenVR for MT How do you run OpenVR with MT?

Just default now. I'm also thinking about QPro, so this discussion is really interesting. Currently using Q2, I'm surprised that default encode bitrate is not giving you worst visuals compared to 350 or more. In Q2 there is a clear difference to the worst if I use the default option (more blurry). While Airlink requires default to work properly.

From a Quest 2 user ( I believe the software is the same). I have hand tracking enabled, so need for controllers, Then I touch the point on the bottom bar where the battery icon is (that has a tooltip saying quick settings) . That brings up the option to connect to Link. After that I launch DCS from PC ( not from the link inside headset)

eager to hear your detailed analysis on the use of QPro. These discussions have been really made my wallet worried

I wonder if you really need a supercomputer to drive a QP given that the resolution is not much different to Q2

Thanks for looking into it. My presets are 01 for desktop, 02 for SP, 03 for MP. This is from my laptop setup where I noticed the problem. DCS Updater Utility.log dcs.log Options.lua.Preset01 Options.lua.Preset02 Options.lua.Preset03 Options.lua

Unfortunately though, regardless of the option selected nothing changes.

So that means that the old app is not usable anymore for preset loading.

Hi @SkateZilla Since the last update (Normandy one) I cannot make use of the presets although the presets are there and initialy it seems the utility loads them. DCS Updater Utility.log

I guess it's because Normandy is an update to the non available any more Normandy 1944

Which version of SW you have updated to? I’m in v50 on both Oculus app and headset, no issues

Until ED fix the issue is the only option in my case.

Try this

For Quest you can try the adaptive option for ASW in OTT

There are so many good stuff in this new version but the most improved one seems to be the presets setting!! (if I understand the picture correctly) Can't wait to test it in action

Fantastic!!

More or less yes. OTT is used as a front-end app of the Oculus Debug Tool that comes with the Oculus Software when you buy a Quest 2 or Quest Pro headset. Among other stuff it also does Supersampling which helps improving clarity in the headset and, as mentioned by Nodak, helps with upscaling technics to improve FPS without sacrificing clarity. The main factors in buying a VR headest (IMHO) are: 1. Budget 2. Use (standalone, PCVR, both) 3. Technical characteristics (lenses, resolution, FOV) 4. Display port connection or compressed image over USB or wifi. and the list and discussion can go on for ever

You better open a new thread to avoid derailing OP's thread on Quest Pro

when you say native what exactly you mean, because OTT supersampling is not native. My understanding is that native is only the one in Oculus app that ends up to 5408x2736. But yes all these testings are subjective

I’m a Quest2 user and I wondered if you have tried using upscaling (NIS) through OpenXR toolkit and resolution override instead of OTT super sampling. It works better in Q2 ( in my case) As an example I use 3020x3060 as override and 135% upscaling (OTT SS is at 0) Also try Turbo mode on Interesting to hear your results

Do by any chance have Motion Blur enabled?