diamond26

@SkateZilla I noticed that the latest version doesn't keep the application settings after restart nullnull

I have to say a big thank you to @SkateZilla for this new version. One week of use and everything works the way I wanted them. I only expect the mods section

I believe all this time we didn't use the right switch for Oculus API Skatezilla mentioned this at some point : if Selection is Oculus API --force_enable_VR --force_oculus_VR By using this switch Oculus API (even outside Skatezilla's app), it works in MT too. Why nobody from ED wasn't able to explain it in the threads complaining about Oculus and MT, it's a mystery. You can check this line in dcs.log : VISUALIZER (Main): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S When OpenXR is active you see it there, when Oculus is active you see the line above. Additionally I use VRPerfkit and when it's working it has the details in its log file.

@Lange_666 I tested it and you are right! Skatezilla's switch for Oculus API works in MT.

That's an interesting finding, as I was also under the impression that MT wasn't available for Oculus API (based on previous testing and all the discussions in the forum) I will test it again later tonight.

You have to use launch with VR ON button not the simple launch button to get OpenXR api to work

Any suggestion on this one?

@SkateZilla UPDATE. 1. OpenXR API works as intended (as long as you use the Launch w VR/ON option) with ST too. 2. If Slots are not populated at start then by clicking Scan in Build Manager it brings them up again. 3. Not sure if it's intended but MT option is ON everytime the app is starting Question: Is it possible to rename Presets as before? Thanks again for this new version!

I was expecting that when you choose OpenXR API in rendering option, you force DCS to run with OpenXR. (Like the switch in the command line) It’s not the case with MT off. OpenXR is possible with ST and Oculus as long as you use the switch

I search registry using the file name of the app. It will bring up DCS updater ones but you only delete those with V2 in the name

The ones related to Updater utility v 2

it seems that the VR Rendering Driver is not working. I choose OpenXR API but the game launched with Oculus (No multithreading)

I had to delete some registry keys related to the new app to make it work again. I now run it as Admin and so far it's working (2 succesful launches). For some reason the VR settings always start at PD 1.3 and the screen resolution always at max despite the different presets setting

Unfortunately is not working out of the box as expected. Crashed in the first try of launching DCS and then wasn’t able to set it up. After crash you need to restart windows to get it to work again. After second crash I can't setup the app anymore

Thank you!

It's definitely more lengthy for me too. Haven't measured the time but the authorisation process is taking longer compared to last OB version

You have to leave dynamic bitrate to default (0) in ODT (since I cannot recall the exact name by heart, try to leave bitrate options to 0 to be sure) to make it work properly. In my case the performance is almost the same as Link. I don't see a reason why QPro will be different with Airlink BTW you don't need the VR enable option if you have the VR setting enabled in DCS

I don't know if you are using MT and if the freezes/crash happen when you put the headset aside but here is what I was experiencing with a Quest2 and how I resolved Another possible reason for the system to crash is a problematic cable. You can eliminate this by checking if crashes occure while using Airlink

More or less yes. You can also check the OpenXR toolkit log where it shows at which resolution it renders. You can also play with upscaling getting even more performance

Unfortunately Quest headsets are sold as standalone VR headsets. PCVR comes as an option. But I use a good cable from these guys and I am extra satisfied. https://eu.vrcover.com/collections/all/products/premium-usb-c-cable-for-oculus™-quest-2-2m

Yes it shouldn’t be good for connectivity (at least the Q2 one wasn’t)

This is not what you want to see when you test the link cable. You should see USB3 and speed above 1.9 gbps. Also when you see these 3 dots, try: disconnect Oculus, power off both PC and oculus and start up again. Sometimes you need to reconnect the Oculus cable on the fly to get rid of this problem. Most times I’ve seen this behavior was when I was switching between different Hz settings (72,80,90) It renders a smaller area on your headset and thus increasing FPS performance. Usually you don’t see the black bars around the image until you hit 0.75 but each individual sees it differently. As with most settings in ODT, you need to put it before you start DCS. To get a feeling what it is just try an extreme figure first like 0.5 (it should look like a tunnel view)

I'm using OTT longtime now but I haven't seen this feature. Where exactly is it?

As a Quest2 user I’ve seen improvement in performance with MT and OpenXR but OpenVR at night conditions is still better.

Hi YoYo, what module your test track uses cause it's asking for activation