dburne

On a sidenote, --force_enable_VR is the same as having the VR option selected on in the game's GUI. If you typically leave that on anyway there is no real need for that argument. You do need of course the --force_OpenXR argument along with the @mbucchia provided wrapper. Thank goodness for his help in getting this solution to us! Does not seem ED has any desire to actually fix this for us so we can have true native Open XR support for our Varjo Aeros.

Wow this new MT has made a huge improvement on Super Carrier Ops using the Hornet. Major improvement!

There again the difference may well be in CPU department. Yes I am running a 4090 GPU but an older i9 9900k CPU with a Z390 MB. Which kind of goes against what Motion Smoothing's purpose is - to get good enough performance at lower frame rates. In my case Varjo's current Motion Smoothing is responsible for much lower framerates resulting in an unpleasant experience. With my current graphics settings in DCS I do much better having Motion Smoothing off. As mentioned perhaps that will change after I upgrade MB and CPU around first of year. As good as I have it looking and running now I ain't giving up any of my graphics.

My main issue with Motion Smoothing is the hit on performance it carries with it. Kind of defeats the purpose of it. Well that is number 1 issue for me followed by artifacting being #2. The artifacting seems a little better but the hit on performance seems about the same to me. I am sure it would be better with a more up to date CPU than my 9900k but I am not going down that road till around 1st of next year.

After spending a couple of days with it I am so loving this update for the MT, I really gained in performance nicely. Please though ED for the love of all that is holy, fix the native Varjo Aero implementation! Currently we have to use a Mod - a wrapper provided to us by @mbucchia to get our Aero to run properly now in DCS. Thanks goodness for his efforts in providing that to us. And with that of course comes trying to keep it running properly through more updates to come. Currently Aero defaults to quad screens in DCS and we have to use this wrapper to correct that. No Aero has 4 screens. Can we please get a fix for this?? DCS should NOT require a Mod to be able to run Varjo Aero headsets in native Open XR.

Running mine no fps lock and no vsysc and am pretty happy. At least so far.

Gave Varjo's Motion Smoothing a shot earlier today with the MT version of the game. It was better , but still lacking for me. I am averaging between 70-90 fps , usually around 80-90 and to me the experience is better still with Motion Smoothing off. Maybe I will check it again around 1st of next year when I get a new motherboard and CPU.

Yes you undo Steam VR by selecting Open XR in Varjo Base...

Insure you have the nomenclature correct in your shortcut properties. For instance mine is "D:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR but I have mine installed on Drive D. Also note there is a space between the last quotation mark and first dash.

So far I have been extremely unimpressed with Varjo's Motion Smoothing. Don't think I have tried it running in DCS - MT yet, may have a look at it tomorrow. I am still quite amazed at the performance I am getting in DCS with my Aero now with the MT version.

Why do you say it is bugged? Seems ok to me but I would not know how to tell if working properly or not anyway.

You may well be right I really am not sure.

Congrats!!

Certainly yes just uncheck Open XR in Varjo Base, it will revert back to Steam VR. However ymmv, as @Supmua mentioned might cause issues with running MT. I personally have not tried it as I am pleased with Open XR running with MT. As I use Point Control on each index finger that would be out of the question. Only running MT version in Open XR now and going forward, unless DCS and/or Varjo find a way to screw even that up. This needs to be fixed so our Aero's have full native support in DCS.

Having to use a Mod to disable quad view for Varjo Aero in DCS is ludicrous. I am very grateful to @mbucchia for providing this as I guess if not for that we would be screwed. Strange how this used to never be an issue but it sure is now. I do not know who that is on, most seem to think DCS, but someone needs to get this addressed!!

Wow almost looks like a GPU going bad, that would be scary to see. Luckily I always have Motion Blur off.

Are you overclocking the cores on that 9900k cpu? I run mine at 5.1 Ghz and combined with my 4090 GPU saw a nice improvement running the MT version.

You are most welcome, have fun!

I got little better results with HT on running MT.

We Aero owners have an issue in DCS, the Aero is seen as a quad view headset. To best of my knowledge no Aero's are capable of quad view. We have to rely on a wrapper - a Mod - provided by @mbucchia to be able to use our Aeros properly in DCS. Is there anything you can do on your end to alleviate this pain for us? DCS is about all I do with my Aero and this is a royal pitb to constantly have to be staying on top of. It did not used to be this way, not sure what changed along the way. Thanks for any consideration in helping us address this.

It should only take a few minutes...

No reason for it not to work - don't give up you can get it! Trust me if I can make it work, you sure can.

Your a little behind. Look a few posts up, have solved this already. Culprit was Open XR Toolkit, once I fully nuked it everything was fine again. I must have somehow got a setting changed in there that it did not like. Thanks,

You should run the Aero natively in Open XR whilst also utilizing the new Multi Threading executable. No need for Open Composite any longer, DCS Open Beta natively supports Open XR. 1st, you will need the wrapper supplied by @mbucchia to disable the quadviews the Aero defaults to. Follow the intructions on where to drop the files. Then just create a shortcut to your DCS.exe in the bin-mt folder. Place this shortcut on your desktop. Amend the DCS Shortcut you just placed on desktop for the target line to read: "D:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR Note after subsequent updates to Varjo Base the above will need to be repeated regarding disabling the quadviews. Note replace D with your corresponding drive/directory. Note there is a space after .exe" before the two dashes. I won't be of any help regarding the reshade.

I spent a few hours after updating today with my Aero and am extremely pleased! Previously i was locking fps to 45 with vync in VB, I disabled that and then saw my biggest gains. I was seeing some framerates hitting between 80-90 fps consistently. That along with Hyper Threading enabled in my bios made a world of difference. I was flying a campaign mission over Normandy that was particularly busy and very demanding, and got very good performance in it now. I am one happy camper after this update. Running the Open Beta MT via Open XR along with Open XR Toolkit. I did not do any testing with Steam VR nor Steam VR's Open XR. Happy with what I have.