RealDCSpilot

You can take full control over the desktop mirror. It's all in the options.lua in the savegame folder. Check the ["graphics"] section and set: ["fullScreen"] = false, ["box_mouse_cursor"] = true, ["height"] = XXX, (in case your desktop resolution is 800x600 set this to 512) ["width"] = XXX, (in case your desktop resolution is 800x600 set this to 512) ["aspect"] = 1, Height and width smaller than desktop resolution will prevent the mouse cursor going outside the game window and accidentally click the taskbar or something else. In my case, my desktop height is 1440 and i run the DCS mirror at 1200x1200. Then check the ["VR"] section and set: ["box_mouse_cursor"] = true, ["mirror_source"] = 1, ["mirror_use_DCS_resolution"] = true,

With VD, choose what's best for you. Using Oculus API or not. After the hotfix from today i simply launch the game with the command line options: --force_enable_VR --force_OpenXR I'm using SteamVR and performance ingame is really good on my end.

@Hunter Joker You could try your old config and it should work like before. I'm keeping the new OpenXR path, it runs really good on my end.

A new hot fix got released with setting everything back, but still leaves OpenXR available via command line start option: DCS.exe --force_enable_VR --force_OpenXR

I really get the frustration, but now is exactly the time we were waiting for all these years... I have no doubt you will come back. And i hope you will have a much better experience.

My experience actually got better. VD had some occasional stutters before the switch to OpenXR. Now the visual framerate is pretty stable. Ingame of course, i don't mind loading screens.

@HillmanVD emulates the presence of Oculus's API. That's why it worked this way for you. But i guess VD can't be set to manage OpenXR at the moment, like all the "real" VR runtimes do. For me SteamVR worked right from the start, i even didn't notice that DCS is running on OpenXR now. The only thing i found suspicious was the new position above the jet in the main menu. And my recenter HMD button worked as always.

@VR Flight Guy in PJ Pants That has nothing to do with SteamVR, it's the streaming forth and back from the mobile headset that get's interrupted by high CPU workloads.

@Hunter Joker @Lurker Try to see it as if you were connecting your HMD for the first time with DCS. Uninstall everything that will potentially interfere. There are already reports that reprojection causes problems with WMR headsets. ED needs to sort this out. For now try to find the best resolution setting depending on your system and image quality settings. However, WMR owners might be in a bad spot for a little while. The reasons are quite obvious. For other VR runtimes, most users wouldn't even notice that something is different. Don't give up, there are more changes coming. It's just the start of the transition.

Goodness, what are you trying to make of it now? Read the news, a lot of bad decisions were made by those companies. And ten-thousands of employees have to take the bite for it now.

Yeah sure. I only need to look at what happened to PCVR within the last eight years... A VR headset is a peripheral device and should be nothing else. Like a monitor, game controller or keyboard and mouse. Maybe we should be thankful that Samsung didn't had the idea to open a Samsung games store, with games that only run on Samsung monitors.

Well, you weren't there: Whatever SDK was publicly accessible back then didn't matter. Everything changed way to quickly and wasn't mature enough. Couple months later the situation changed to getting bad for us.

Looks like you weren't there in 2014. When Zuckerberg got the brain fart he needs to wage a war about VR to be able to rule the world of the future.

They only use their ecosystem to distribute the software package, because it's well accepted (and they started 10 years before everyone else thought about distributing software online). From which source you get your VR game is not depending on this.

OpenVR was the first VR API. Valve was already working on VR before Palmer Luckey popped up. If the Oculus thing wouldn't have gone wrong who knows what exercise OpenVR would have become... Well, makes no sense to speculate more about this. The real problem is the disruption that all this early greediness brought for the PCVR market.

@Dentedend10 The "Current OpenXR Runtime" setting tells Windows which "handler" is managing OpenXR. If it's set to SteamVR, SteamVR is the "handler". The problem is that WMR was a bad idea! Valve and Oculus were pretty close at the beginning, OpenVR could have been the unified API for VR and we never would have seen all this chaos. Then Facebook interfered and caught Oculus and thought it would be a good idea to build a closed platform within Windows, looking for domination on this tiny, much to young market. Later Microsoft had the same idea and transformed it's Hololens API WMR into a third VR API also trying to win a war here. They flooded the market with cheap half-assed WMR VR HMDs by Lenovo, Samsung, Acer, HP and more. This coup flopped hilariously, no developer needs a third API to waste more time and effort when he already needs to work for two other APIs. Today, years after this, Microsoft has finally pulled the plug on that idea. And you look at SteamVR in the wrong way, they are the only ones who still try to support as many HMDs as possible while Facebook gives a sh!t. Or are you able to play a Oculus exclusive game by simply starting it for your HP G2? With OpenXR we now have a second chance to get rid of this nonsense.

It drives me a bit nuts how people throw around the words and mixing stuff up adding more to the confusion. Let's try to clear this up: - VR runtimes and VR APIs - SteamVR can do OpenVR and OpenXR. Oculus can do LibOVR and OpenXR. Windows Mixed Reality can do WMR and OpenXR. (Microsoft couldn't find an additional name to distinguish between their VR runtime and VR API) :P 1. DCS now talks OpenXR 2. Before the latest patch DCS could only talk OpenVR (SteamVR's native VR API) and LibOVR (Oculus's native VR API). 3. DCS never could talk WMR, the Windows Mixed Reality API by Microsoft (Sadly HP chose WMR as main VR runtime for the Reverb series, here starts most of the trouble...). 4. Microsoft made a very bad "WMR for SteamVR plugin" so that WMR headset owners would be at least able to play VR games over SteamVR and it's OpenVR API because nobody really made VR games for WMR. This WMR plugin is basically a very underpaid translator, talking OpenVR to WMR, a bad choice of middleman software for popular headsets like HP's Reverb series. 5. So for DCS that means - it talked OpenVR to the WMR for SteamVR plugin wich translated everything to WMR. This wasn't working very well. Thank you Microsoft (good that they now finally stopped this). So OpenComposite came in for the rescue. It translates everything from DCS to OpenXR, the only other VR API that WMR understands. And OpenComposite put a lot of tuning options into it to compensate WMR performance troubles. It is the better translator. 6. OpenXR was developed by Khronos Group to end this mess - One API for ALL! 7. Guess what, SteamVR can also natively talk OpenXR. Oculus can also natively talk OpenXR. 8. OpenComposite is not OpenXR. Sadly a lot of people, mostly HP Reverb owners, refer to OpenComposite as OpenXR. That's not correct. It's also unfair to blame SteamVR for having bad performance if you plug a WMR headset to it via the inferior "WMR for SteamVR plugin". 9. For DCS now everything is about to change! SteamVR native HMD --> Oculus native HMD --> OpenXR --> DCS WMR native HMD --> No more translators needed, finally. Each VR runtime has OpenXR included for quite some time already. If you have a myriad of VR tweaks installed, especially if you were going the OpenComposite route, just start fresh. Step by Step. In the coming months a lot is going to change. Most guides are already deprecated now. Especially for DCS and VR and HP Reverb owners. (And no, DCS bought on Steam doesn't mean you have to use SteamVR. Steam as a shop and SteamVR as a system component are completely different things. You can now use DCS standalone or DCS from Steam with every VR runtime that is compatible with your VR HMD.)

It's native OpenXR, OpenComposite's workaround is deprecated now. All VR runtimes should be able to connect directly to OpenXR now, some still might have troubles (Pimax and Co.)

@VR Flight Guy in PJ Pants @NatoAviator Try to get rid of any additional tweak first. Basically start with vanilla DCS and your VR runtime only. SteamVR with VD (VR Flight Guy) or plain WMR (NatoAviator). This will continue in the next months, because a lot will change. Most of the known tweaks will get old and deprecated.

Two things, one is in your dcs.log, there should be a line with "INFO VISUALIZER (Main): LAUNCH IN VR : SteamVR/OpenXR : oculus" and the second is that when you start DCS and land in the main menu, you will be positioned quite high so that you are looking across the wing of the jet in the hangar. From there you simply press your VR recenter button and your height should be set right in front of the menu.

@VR Flight Guy in PJ Pants Pico is running fine. Virtual Desktop runs it emulating a Quest HMD. The DCS log says "INFO VISUALIZER (Main): LAUNCH IN VR : SteamVR/OpenXR : oculus" which is exactly what you want to have. Since VD's reprojection system runs on the headset, no problems! People mix up to much about SteamVR and OpenXR! SteamVR is just a runtime, OpenXR is an API. SteamVR was never the source of trouble for WMR headset users, it was the half-baked WMR for SteamVR plugin by Microsoft. OpenComposite was basically made for bypassing this terrible WMR plugin. The whole thing was just a failed attempt by Microsoft to establish a third VR market platform. But luckily no developer really cared about WMR as an API.

@Assamita On VD's Discord they say you have to disable energy saving options and factory reset the device. The issue came for some people after the 5.3.2 update.

It's my 7th HMD since 2016 and the one with the fewest inconveniences...

For "UI Layer" i have bound 2 HOTAS buttons on my throttle grip to left click, right click and one encoder dial of my throttle grip to mouse wheel forward and mouse wheel backward. Gives you all the same functionality like with a mouse and no need for running extra mapping software. Yes, they will continue to work. Other people also use classic trackball devices as alternative to binding mouse buttons to HOTAS. I believe there is even a binding somewhere to hide and unhide this cursor. Have to search for it again...

The trick is to give VD some time in Wifi first before switching Wifi off in the headset. VD makes a copy protection check over internet once it started, so it needs Wifi on the headset for a small amount of time.