slughead

@BIGNEWY I think this is still worth DCS looking at in case Meta has decided to make a permanent change. Considering that they forced Steam to change their VR code in the last couple of weeks, I expect they will also expect ED to follow suit as well.

Update: rolling back just the Oculus app solves the problem (i.e. opting out of PTC on the app and not the headset). Using the PTC, the Oculus app was updated to v63 whilst the headset remained v62. I have raised the issue on the atmeta support forum: PTC v62: Oculus app updated to v63 headset update ... - Meta Community Forums - 1152703 (atmeta.com)

That's normal as the second column of 5 LEDs have no function.

Ok. I don't get a GPU driver crash prompt. I don't see DCS screen in the headset - the new PTC has changed this. It now shows all your recently run apps and displays a swirling circle on the ones that are loading. DCS does not remain in the task manager - it is killed automatically or by itself so there is no hung process to terminate that I could see. It would seem that the behaviour for you is a bit different to mine. Maybe because you are using AMD and I am using NVidia. I'll test again later today to see if I can get anymore information out of the system/process.

@SkateZillaI can't work out what you are trying to demonstrate or what you expect the outcome to be as you've not stated what you expect it to be. For sure, I expect Meta's change to affect many applications. For example, they recently made a change that broke SteamVR which was subsequently fixed in a SteamVR beta build.

Are you sure it's not VR only? The latest Oculus PTC is causing DCS to crash just after the splash screen.

I've stopped using QVFR with my 4090. I found it is causing more CPU load than without it and reducing performance. @piolin23000VD sets render resolution for you depending on your choice, e.g. god mode etc. With the Oculus link, you must set it yourself via the slider in the Oculus settings or via the PD setting in DCS. I prefer to set the PD setting to 1.4x and leave the render resolution to 1.0x in the Oculus config. Changing the render resolution in the Oculus setting sets it for all applications using the link whereas setting it in DCS sets it only for DCS. That way I can adjust it per app as needed.

@Flappie no zip files produced. Let me know if there is anything else I can do to help.

Same thing happened with SteamVR and Oculus v62. Steam had to fix it on their end. Looks like we are going to need a DCS side fix before Meta make this a general release. Probably best not to mark this as solved… as it is going to come back when Meta push this out to all users.

I have had this today and thought it was due to an Oculus update. I reverted back from the PTC to normal release of v62 and DCS loaded fine. I haven’t tried again with the PTC version of v62 however my DCS log ended exactly the same as yours has. I raised the error in VR bugs section. 2D worked ok though.

I've just had the latest Oculus PTC v63 downloaded to my Oculus Pro and DCS crashes just at the point when it is about to launch into VR. DCS runs fine when I revert to v62. Is anyone else seeing this? The DCS.log doesn't reveal anything. It's just cut short with no obvious error. If this is caused by some API change on the Oculus end DCS will need to jump on this quickly before the next general release of the Oculus software. dcs.log

The wiki for the tool describes a config file setting to prevent it being exposed to executables of your choice. There is an example already in the config/settings file which you can then copy and apply for dcs. Or you could use this to disable/enable openxr layers completely. https://github.com/fredemmott/OpenXR-API-Layers-GUI

I expect that enabling XMP did more than overclocking the CPU. If you revert the CPU back you probably won't notice any difference.

First post in the thread.

dcs2target has moved from export.lua method to the hooks method. I would suggest you use the latest release of dcs2target as the hooks method will not interfere with other mods that use the export.lua method.

Add another layer of tape. Plus some on the friction shoe. No custom curve. Default settings worked ok for me.

Can you elaborate on finicky? Low friction tape…. Removes any tendency for the throttle to stick making minor movements precise. Combined with damping grease makes it sublime to use. i have lots of the tape if you want some.

That's normal.

https://gprivate.com/68nlt

There are two options in DCS that cause this that you need to disable. It's in the wiki for QVFR.

MSAAx2 has too much shimmer. I switched to MSAAx4 before DLSS came out. I now use DLSS with Oculus render resolution set to 1.0x (as that affects everything) and PD in DCS set to 1.3. It looks ok to me. I matched your settings apart from the sliders which I max out down to smoke density. I cannot hold 72fps whilst turning at corner speed over Cairo. Maybe this isn't a problem for you helo guys. I also don't like buildings popping up like mushrooms. Also clouds lower than ultra shimmer. So I am glad that you are happy with your settings and performance. It's not for me though. I'll stick with ASW kicking in.

Just plonk it in your dcs\bin or dcs\bin-mt folder. You might want to backup the existing one first incase you need to revert.

@YoYo thanks. Your settings have a few things turned down to help you achieve 72fps as I expected compared to mine. Such as visibility range High vs Extreme, Civilian traffic medium vs high, clouds high vs ultra, clutter/grass 300 vs 1500 (all my sliders are maxed out). And other than you are running MSAAx2 and I am running DLSS at balanced we are the same. Although I fly F-16 mainly. I don't think I could drop the visibility range... I prefer that maxed out. Same with the clouds as I am often up there amongst them. I will say though that it would seem, thanks to your input, that I don't need to run QVFR anymore. I guess that many of us just left that on as it did help at one stage. Perhaps the introduction of DLSS has negated the need for QVFR. I certainly prefer not to use it if I can. That also means I can disable eye tracking which saves some battery drain. I'll have a play around with the settings to see if I can maintain 72fps over Cairo as it isn't pleasant having it drop into ASW.

I’ve not seen a way to do it. I believe there is a way to do it via a script in which case you could then use something like autohotkey to capture a keypress of stick button to run the script. Other than that I’d have to check in OTT to see if there is a way in that tool to do it. Out of interest, why do you want to turn it on and off during the sim? Have you considered auto ASW mode?

And your in game settings @YoYo?