Baldrick33

In my experience, developers write chapter and verse when they want to explain why things are taking longer than expected. So I look at the lack of info on the core stuff as a positive! These things go to the wire, it is too early for a definitive list of what's coming in March, we just need to be patient (yeah right!)

In my case I had SteamVR set to a custom (lower resolution). When I first tried OpenXR I thought the image was great but the FPS had dropped. Then I realised the default resolution in OpenXR was much higher. Once I set it to the same then all was good.

@Tomcat388th If you use motion reprojection you will also need the Toolkit version 1.2.4 to enable it to work with the native DCS OpenXR

Are you using motion reprojection without using the OpenXR Toolkit 1.2.4?

Unfortunately for us I think mainstream tethered dedicated PCVR devices are an unlikely direction for new development, the Rift and Quest is a good example, with the former obsolete. Tethered PCVR is seemingly becoming a more niche, enthusiast product with the pricing to go with it I am afraid. I hope I am wrong though!

I think much the same. The VR division was a tiny little experimental offshoot. All the big companies wanted to keep a toe in the water, games were initially ahead of commercial use but I would guess their focus is squarely on the commercial market now. The G1s were notoriously unreliable - I had four plus a cable under warranty so I doubt they made much profit if any. The later G2s supposedly fixed the issues but I still see lots of cable issues on forums. For me in the UK, HP have been great at swapping stuff out though it is clear speaking to the support guys the VR stuff is a real niche for them to deal with and most VR enthusiasts will know a lot more about them! If HP are looking to tighten belts then consumer PCVR would seem a rather obvious casualty unfortunately for us.

The WMR OpenXR reprojection and SteamVR reprojection are subtly different. Some prefer the SteamVR version which can now use the OpenXR runtime since we have native OpenXR support in DCS.

As mentioned it provides yet another option, SteamVR motion reprojection with OpenXR and the toolkit options.

I had a similar problem with a well know race sim. It was the only thing that would crash my PC and the logs showed an nvidia driver issue. I was convinced it was the sim but it wasn't a problem experienced by others. Eventually I accepted it was my PC - the race sim was just the trigger that pushed it over the edge. It was a while ago, I think I ended up reinstalling Windows but it may be fixable by trying the post above yours.

I have several Arduino devices. Windows frequently swaps their IDs around - especially if I disconnect or add one. Using Joystick Gremlin it is possible to edit the profile xml file in a text editor and switch the device ids around. This only needs to be done once rather than for each module. e.g swap the following ids <device device-guid="{42D97A40-DDEC-11E9-8001-444553540000}" label="ARD 4" name="Arduino Micro" type="joystick"> <device device-guid="{B98437C0-1FF5-11EA-8001-444553540000}" label="ARD 2" name="Arduino Micro" type="joystick"> I stopped using Joystick Gremlin some while ago after having a few issues with vJoy. I now use JoyPro exclusively to manage DCS controls. It has a great feature to swap devices when Windows decides to change the ids. https://github.com/Holdi601/JoystickProfiler

I don’t believe you could make another game have native support for OpenXR by copying the dll. You would still need to use OpenComposite as far as I know.

The OpenXR Toolkit now includes a fix for motion reprojection with DCS in native OpenXR mode:

My apologies, I thought it was connecting wirelessly as you mentioned using Virtual Desktop. It is over two years since I experimented with the Quest2, so I guess Virtual Desktop is required to stream the video via USB? I know things have moved on and many use a Quest2 with DCS now, I just recall it was quite a faff at the time - I also tried the official Oculus cable and returned it as I had more success over WIFI and also came to the conclusion I wouldn't use it for PC games. Good luck with the Pico. My point was that it adds layers to the process of getting DCS to connect to the device. That doesn't mean it is a bad experience just that it may require more fiddling and more stuff to keep on top of than other headsets, rather than plug and play.

I am not sure how you inferred that from my post. I have no knowledge of all those assumptions. As you say the issue isn't the headset per se, it is the apps. The more steps you have to take to get the output from DCS to the headset (and include WIFI routers and PC networking in all that) the greater the potential for one of those steps causing issues and needing troubleshooting or tuning. Which is my point and comes with the territory of connecting a standalone device wirelessly to a PC. Stuff will change and unfortunately will sometimes make things worse. The roll back is a good shout. OpenBeta will regularly change - we literally demand it daily! Using Skatezilla's app is the easiest way and you simply pick which version you were most happy with.

I do, courtesy of Chuck's A10 Guide! If you haven't seen it I highly recommend it (along with all his other ones) https://chucksguides.com/

VR users on these forums have been crying out for native OpenXR support. ED were responding to customer demand in my view. I don't know much (or anything really) about the Pico but the hot fix reverted to using either the opencomposite or SteamVR method as before for WMR devices (without manually adding the switch) Personally I think the Pico is a brave choice for running DCS. It is pretty much brand new and as a standalone headset adds software layers to get connected and opens additional world of potential WIFI networking issues. We have a family Quest2 which for curiosity I got working with DCS and Medal of Honor (PC version) . I ended up using an access point I used in another part of the house and reconfiguring it to exclusively run with the Quest to get Medal of Honor working decently. Once I had done that I tried DCS but compared with my Reverb G1 it seemed a poor second. I get that standalone headsets are great at what they do and for standing and moving games they are the best choice but for PC connected seated games like flight and race sims they are a compromise and fiddling about with virtual desktops, wifi settings, side loading unsupported third party apps etc are all part of the process of getting them to work well. It doesn't mean it shouldn't be possible to have a great experience with it and DCS but I think expecting it to be plug and play and work great is a big ask.

@Thinder I understand the frustration and passion. VR has been so tantalisingly close to being damned near perfect since I got my Reverb G1 three and a half years ago. The pace of headset development, PC hardware to run them at higher resolutions and for applications to be optimised to run VR just seems to take an age. Yet that isn't untypical for what is a pioneering technology. That is still how I see VR, we are pioneers and with that comes a layer of complexity and continual change to make it better. That can be frustrating. A few times I have tried going back to monitors, even got Opentrack working with my VR headset perched on top my head to consider purchasingto a trackir type solution but each time I realise VR has hooked me. I go back to VR and the wow moment is there again! I am grateful for ED providing the level of support they have, though I yearn for engine improvements to improve performance which can't come fast enough. I see ED and the community needing to work together and this last week has been a testament to that. We can't expect developers to support every combination of hardware and software that make up the current VR options, especially with so many third party options needed to get standalone headsets working with PC apps. Yes, ED did muck up with the lack of communication that OpenXR was coming, worst still making it default albeit for a day. That message has been driven home enough. Going forward I still expect to be in a state of flux. OpenXR will continue to develop, the tools for VR will get ever more sophisticated, the number of headsets will increase, the tuning that comes with initial implementations of multithreading and vulkan and so on. I can't see a simple plug and play for any headset on the market for the forseeable future. It is going to take some work by the user to get the best out of (or even make it work) for some time.

I had a very similar issue with a G1, it started with Half Life Alyx and after 10 mins or so one eye of the headset would go grey then come back intermittently. It turned out to be the cable and HP replaced it under warranty. Touching wood, the same G1 is working perfectly with DCS and native OpenXR support.

Good news, great community, simply amazing help from @jonsky7

What do they say about a week in politics? It seems an eternity in the DCS World!

Glad you got it fixed, well done for persevering!

Anything in the log file? Edit: what does it show for the OpenXR runtime in OpenXR Tools for Windows Mixed Reality?

Not sure I understand that. The 22, 30 & 45 reprojection have all worked in OpenXR & DCS since the initial opencomposite release. 22 isn't great but 30 is very playable - almost indistinguishable from 45 in my experience with WMR & G1

@markturner1960 it is hard to tell from the image but are you sure you have two dashes before each switch in the command line? A repair will overwrite the dll but I am not 100% sure that it is necessary.