dburne

This is what I have: Will delete and try again to see if new file generates, InstanceExtensionsWrapper.log

This is so very strange. After some more fiddling around with it here is where I am: Regular Steam VR works fine. Steam VR's Open XR runs fine. If I try to launch in native Open XR using the wrapper for the Aero, it now launches but only on desktop and only minimized on desktop. Can not un-minimize it on desktop and no mouse control. Have to end DCS.exe with task manager. Going to try a repair of DCS and try launching it in native Open XR before installing the wrapper. Interesting note just had a look in the Varjo OpenXR folder and this time it did not create an .original file after inserting the wrapper - odd. Ok now it is back to crashing when trying to launch in Open XR again. Time to throw in the towel on this one, and just run it in either Steam VR or Steam VR's Open XR. I am at a total loss on why it is not running in Open XR natively any longer. I am sure it is somehow related to the wrapper I was using to get it to run properly in my Aero but I can not figure out what it is. All I know is now I can no longer run DCS in native Open XR with my Aero. I hate it as I got to see some better performance with it when it was working for me.

Ummm no, not sure about that one... I switched back to Steam VR and it is working fine, just for some reason Open XR no longer working and causing DCS to crash upon trying to launch it. Edit: It won't launch in VR in Steam's Open XR runtime either, it does launch but to 2d desktop not VR. Currently only regular Steam VR (Open VR) is working properly. Very wierd. So I have tried: Removal of the Mbuchhia wrapper and repairing DCS. Removal and clean install of Varjo Base. Seems somehow for whatever reason running this wrapper for Open XR has really changed something on my end today and no idea what it has changed. It has been running fine the last three days or so without any problems. At least I can still fly DCS in Steam VR but I was really enjoying the added performance Open XR brought to the table.

Just tried a clean install of Varjo Base software 3.9. Still no go. I am dumbfounded on this one.

A few days ago I made the change to using the Open XR Wrapper for my Aero supplied by Mbucchia and been running DCS great. A little bit ago it crashed, and now I can not get DCS to launch again using the Open XR wrapper., I tried a repair of DCS and installing the wrapper again, and still DCS will not launch. Each time I try to launch it I get the below error message, and after clicking ok it just drops back to desktop. Any ideas?

It releases on March 24th. Looks to be interesting, shame they did not include a native display port connection. Not sure why so many of these "hybrid" developers just refuse to include a standard display port.

Hmm pretty sure MSFS only has native Open XR support ?

Pretty sure Open XR via Steam VR has been in there a while now, under Developer section I think. At least I know I have been running Steam's Open XR with DCS for a while.

I think we need more acronyms for VR...

Good quality metric allen wrench set is a must have for these great boutique flight gear hardware. My CM3 stick Base did come with two allen wrenches but I tossed them aside as I prefer my own.

No need to store in a closet, demand is pretty high on Virpil products currently and doubt you would have any trouble selling it and getting most of your money back. You might even ask Virpil about a return. Well in the flight sim boutique hardware lineup, we have Virpil, VKB, and WinWing. I have experience with both Virpil and VKB and consider both to be very good, WinWing I have no experience with at all.

Specs in sig. Basically 4090 GPU, Intel i9 9900k at 5.1 GHz., 32 GB 3200 MHz cl14 ram. I saw a nice increase going from 3090 to 4090 GPU.

I absolutely love my Aero and have been running it solid since Jan 2022. Have had to deal with support on an apparent dead Link Box, they had a replacement Link Box and Cable to me in 2 days ( shipped from the US support site) and have been rocking along ever since without any hiccups and that was several months ago. Granted I am techically out of warranty period now so no idea how out of warranty support might be. I can tell you to be safe going forward I ordered another new Link Box and Cable to have as a spare. I am retired and use it every day so I don't like down time lol. About all I do with this is DCS as well. You will need to do some tweaking to get performance acceptable but man when you do it is gorgeous. Downside is audio and needing to get Steam Trackers. I use the Index trackers that came wtih my Index kit, and earbuds I have plugged into my Creative DAC.

I suggest just using the debug tool to fix the cross eye alignment and then using Steam VR to get your feet wet with the headset first. No need to make it more complicated than it needs to be for a first time user. One can always explore some of these other options laater when more familiar with the workings of the headset.

Firstly, follow the instructions in the first post of this thread to take care of the cross eye alignment. Pay no attention to the WMR comment.

Why not just use the passthrough feature on your Quest 2 when needing to look downwards? I thought that feature worked pretty well now.

Too much fricition in trying to use them , which is why I went back to Steam VR and that can be complex enough for new users. This is why VR in it's current form will never reach mass adaption. I just hope it remains enough for companies like Varjo, Vive, Valve, etc to continue to produce headsets. Seems there are a lot of cut backs going on right now which is concerning but with uncertainy it is understandable. Hopefully the new Play Station VR2 with it's eye tracking and foveated rendering will help entice other game developers.

No.

Thanks for the feedback, yeah for VR's sake I hope Sony continues on with it. Would be very good for the industry.

Traiter!!

Well that about settles it for me then - their Motion Reprojection increasing the GPU frametime that much kind of defeats the whole purpose of reprojection imho. I may check it out once it is released into the wild but doubt I will care for it. I will stick with my 45 fps locked non motion reprojection settings.

Ditto. Get rid of all you can of WMR unless you plan on continuing to use the Reverb. Set Steam VR in the Advanced Settings to be the Open XR runtime. I put a shortcut on my desktop to DCS.exe and named it Open XR with the following: "D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_OpenXR ( obviously I have DCS on my d: drive in this case). Note there is a space between the last quotation mark and the first -. So when I get ready to fly, I launch Varjo Base. Then Steam VR from within Varjo base on desktop. Then the above mentioned DCS shortcut that I created on my desktop. Once DCS is loaded up I put my Aero helmet on and off I go.

Yep still running it at 5.1 Ghz on all cores and a 4090 GPU which really helped in DCS. I have upgrade plans for around turn of the year. No desire to any sooner. I am fine as long as I limit my Normandy exposure lol. Could have sworn I have seen others with the same complaint over the last while but I could be wrong. I put this 9900k z390 system together in Jan of 2019.

Sounds like you and I have very different experiences on these maps in VR. I had very little trouble running 45 fps in my Aero on the Channel Map, major issues trying to do it on the Normandy map. I also had always heard the Normandy Map was brutal in VR... Can't explain why, but that is the case on my end.

That was my beef with the initial beta release. Taxed the system too much just to use it which kind of defeated the whole purpose in having it.