RealDCSpilot

Oh, i didn't mean the expected pixelation of foveated rendering. In the center, which is on full super sampling resolution, the image quality also suffers too due to video stream compression. I guess this is what certain people meant while testing the Pico4 and found it's compression quality not acceptable. If they were using OpenXR toolkit... no wonder. Without any tinkering and plain VD it looks fantastic.

@Peedee Alright, now we are talking. Well, we have almost the same configuration, i can run DCS at 3840x3840 per eye and this should also be possible for you. Try Pico 4 with VD at godlike and SSW always on, force DCS to OpenXR and in SteamVR set SS resolution manually (increase from the godlike preset). Let's see what happens Especially with the new 13XXX CPU series i also recommend Win11 for better CPU handling. Runs like a charm on my end.

Maybe an important info... Just tested OpenXR toolkit with VD streaming on Pico4. While it can help with gaining some more FPS on paper, it also degrades the image quality. This makes sense, because fixed foveated rendering changes how pixels are drawn for each frame drastically and means more workload for encoding and decoding. It shows a lot of compression artifacts, something i hadn't seen before by just using VD at GodLike with SSW enabled.

Yes, with the new version of OpenXR toolkit you can finetune the native OpenXR pipeline and see if it helps you getting a couple more FPS (at least fixed foveated rendering for all supported headsets).

Buying another highres VR HMD will not change your situation. I would consider upgrading your machine instead. A RTX3080, 3090, or 4080/4090 and maybe a new CPU too would open the path for running VD's high quality profiles were compression isn't a problem anymore. Your G2 would also benefit from this. Keep in mind that VR panels always need a higher render resolution than their panel resolution. Both, the G2's and the Pico 4's panels have 2160x2160 pixels per eye and you need to run the game at least at 3120x3120 per eye to meet their target image quality.

Sorry, Open Beta of course...

Since the latest update for DCS this thread might need a little refresh: DCS on native OpenXR runs excellent with Pico 4 over VD with SteamVR. (Currently with custom shortcut and command line parameter-> "--force_OpenXR")

@rosteven1Don't confuse OpenComposite with OpenXR. OpenXR as a VR API is natively built into SteamVR as well. And OpenXR is basically the new standard for every VR runtime. (It already was about time for DCS getting it implemented.)

Don't worry, putting the command line options outside the question marks is fine for making a custom shortcut. The way i wrote it is just the general command line (if you launch DCS from a .bat or simply from cmd.). However, in a couple months we all will never need to look back at this confusion. DCS on OpenXR all the time, plus Vulkan and Multithreading should be the standard way then.

@oldcrusty Please check your terms and context. There is already enough confusion and there is technically no way SteamVR can beat OpenXR. What you mean is OpenComposite or your post wouldn't make any sense. You also can't uninstall OpenXR. OpenXR is a component of SteamVR, it's also a component of OpenComposite in that sense. I can only assume that you actually meant that you were trying to run your G2 over OpenComposite and then compared it to running it with SteamVR. There is still some info missing here, were you running SteamVR with OpenVR or OpenXR? Since the latest hotfix for DCS Open Beta disabled autoswitching to OpenXR, i can only guess the right phrasing of your post should be: "SteamVR with OpenVR beats OpenComposite with OpenXR on my rig" ?? Is that what you wanted to say? For other users it would be more helpful to phrase your VR path correctly (Oculus VR not included): SteamVR -> OpenVR -> DCS (one of the standards before the OpenXR update for DCS) or SteamVR -> OpenXR -> DCS (hotfix after the OpenXR update for DCS, now available through command line parameter "DCS.exe --force_OpenXR") or OpenComposite (with or without the tool kit)-> OpenXR -> OpenVR ->DCS (standard before the OpenXR update for DCS) or OpenComposite (with or without the tool kit)-> OpenXR -> DCS DCS (hotfix after the OpenXR update for DCS, now available through command line parameter "DCS.exe --force_OpenXR") or this is new! Windows Mixed Reality (your G2's native VR runtime) WMR -> OpenXR -> DCS (hotfix after the OpenXR update for DCS, now available through command line parameter "DCS.exe --force_OpenXR") You see, there are these 5 possibilities, but nobody knows exactly what you are trying to say about your findings.

No crashes here with Pico4, VD and OpenXR over SteamVR. Can play for hours and it's running great. Native OpenXR is a great feature for DCS.

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.