RealDCSpilot

You should simply forget about this. You accumulated a lot of false muscle memory and have to get rid of it. Start fresh like it's a completely new DCS helicopter module (which it basically is now). For the first time in 7 years this thing acts like a heli and i highly doubt that the engine is to weak. However, FFB trim is still badly broken, i hope this is going to be fixed quickly.

Simply turn off MSAA completely and work with higher resolutions (Supersampling). See how your system can handle resolutions over 3Kx3K pe eye. MSAA is a stoneage method, very inefficient and demanding. I'm also eagerly waiting for DLSS as the next feature to tune performance and image quality.

@Gunfreak Hi, this problem is totally on Brunner's side. There are only buttons in the grip, all the decoding has to be processed by the controller board and software in the base. In my case i have used my 50CM2 grip on a VPC base and now on a VPforce Rhino and never had such a problem. However, Virpil's grips do go through iterations with internal changes. A 50CM2 from a couple years ago isn't internally the same like a 50CM2 from 2023, because they also go through optimization processes. So Brunner has to re-evaluate the latest versions and tweak their drivers.

This is the worst "procedure" i've ever seen. It's totally wasting ressources with launching a VR app (Steam VR Home) and use it to launch another VR app (the wired PCVR version of Virtual Desktop on SteamVR) to finally start the VR game you want (DCS). It's much better to go this way, to directly(!) launch DCS MT with SteamVR: 1. check SteamVR settings, if Steam VR Home is enabled -> set disable. Now SteamVR should only show the 360° environment with the ground grid on start. 2. bring up the SteamVR dashboard and click the second button on the bottom left that says "desktops". 3. simply click the DCS shortcut you prepared for running multi threading and VR (wherever you placed it, on desktop or in the start menu) @Thinder Your CPU clock speeds at 3600 MHz look very odd, maybe the worst clock speeds i've ever seen on a 5800X3D. They should be much higher under load. As others and myself already assumed in other threads, there are certain things pretty messed up and not working well on your system.

@Sabre @Koziolek The news about Pico and OpenXR support is only about native OpenXR API support for standalone Android VR apps and games. You can ignore this. In PCVR mode the VR runtime on the PC manages which API is getting used and SteamVR as a runtime, can do both, the OpenVR API and the OpenXR API. This works for a couple of years already. In SteamVR settings, you can check if SteamVR is set to do that. It shows "Current OpenXR runtime: SteamVR" if everything is in order.

@solidusfoxPlease consider marking your topic as solved if you found a solution.

You mean the G2 and it's WMR runtime has motion reprojection issues with OpenXR. I'm on a Pico 4 with Virtual Desktop and it's SSW reprojection system works flawlessly.

@propeler Is your USB network connection also set to be a private network in Windows?

MT with OpenXR over SteamVR running fine here. I use a shortcut with the line "...your path...\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR First i start SteamVR then i click desktop mode on the dashboard and launch DCS with the shortcut. Be aware that OpenVR as an API is EOL, same with Oculus's LibOVR. OpenXR will be the one and only VR API in the future.

@crispy12 Yes, runs nice and no crashes so far. Just take the casual route, make a shortcut with the bin-mt path to DCS.exe and with the OpenXR command line. Start VD as usual, start SteamVR, click desktop mode on SteamVR's dashboard and launch game via the shortcut. Keep in mind that DCS is in a big transitioning phase (from ST to MT, OpenVR and OculusVR to OpenXR, from DirectX11 to Vulkan...). At the end it will be running OpenXR, Multi-Threading, Vulkan and DLSS and so on by default.

MT with OpenXR running fine here over SteamVR. Be aware that this is a transition phase, everything performance related will change completely. We now got Multi Threading, later we also get the switch from DirectX11 to Vulkan and DLSS too.

Best thing is, we also will get DLSS and Vulkan on top of MT...

Yes, should work for most situations. But for some games it's safer to make sure SteamVR is already running before starting them from any location. (This way you'll prevent SteamVR initializing later then the game expects it up and running. Simply use the shortest way as long as it works. In a situation where it doesn't work anymore, you still have the "longer" route as an alternative.)

Are you kidding?? Are we supposed to look and search elsewhere in this forum to find any context you are talking about? Buried in a post from mid january in /General Off-Topic Discussion/ PC Hardware and Related Software ??? Goodness... And what are you talking about a loss of visual quality by an update?? There was no such thing introduced with the latest updates. Most of the time i absolutely don't get what you are talking about, besides some strange obsession with derailing threads. What's pretty obvious, with problems you might have, is self-inflicted user errors.

Where?? Please don't clutter the thread with any more misinformation or missing information. I hope you get the point that Pico Streaming Assistant and Virtual Desktop are 2 separate ways to do VR streaming. @ECTAE a 5800X3D and a 4090 are a perfect combo for VR at 3Kx3K per eye. If you have a Wifi5 or better router in the same room, you should be able to run a Pico 4 at it's best capabilities that will definitely surpass the Rift S in visual quality.

At step 3 - are you talking about this app? https://store.steampowered.com/app/382110/Virtual_Desktop/ @Thinder Are you aware that everybody in this thread and the whole VR section is always talking about the standalone "wireless" version of Virtual Desktop? Which has to be started on the headset itself and connected to the free "Streamer" app running on Windows? https://www.vrdesktop.net/ Running Pico's Streaming Assistant to run Steam VR to then get the desktop version of Virtual Desktop running to run DCS is total nonsense! You either run DCS via Pico Streaming Assistant and SteamVR or you use the much better alternative with Virtual Desktop ON YOUR PICO 4 to connect to your PC with it's streaming app and run SteamVR and then DCS. And we are all talking about Virtual Desktop here because it offers much better quality and tweaking options! About your FACTS: everybody here and in the whole world would really like to know how you achieved real 180 FPS in VR in DCS. Like in this video you posted. It runs with terrible stuttering but shows 180 fps which also makes no sense. PD setting at 1.6 ... Wtf? So please enlighten us?!

To put it more simple: The news is irrelevant for PCVR. It's about using the OpenXR API on Android devices. On PCVR the Pico 4 already supports OpenXR enabled games via SteamVR. Also does the Pico Neo 3 Link. By connecting to SteamVR as the VR compositor, everything OpenXR related is managed by SteamVR (works flawless, mostly you won't even notice). As you may have read on other threads, don't mix the real OpenXR (the API) with wrapper tools like "OpenComposite" and "OpenXR toolkit"...

Maybe better to remove this because of no relevance. This simply means that standalone app development for the Pico headsets and Android OS can be done with the pure OpenXR API. The SDK is actually available since October last year. (https://developer-global.pico-interactive.com/sdk?deviceId=1&platformId=1&itemId=7153484514247917573) OpenXR on PCVR (Windows) is something different than OpenXR on Android. For PCVR simply use Streaming Assistant or Virtual Desktop over SteamVR to have full access to native OpenXR apps/games on Windows.

You have to restart DCS everytime you change the resolution in SteamVR or you won't see any impact. While running 3120x3120 you should see fps at something in the mid 70's, on 3820x3820 something around 60 fps (with my ingame settings of course(!)). However, 3120x3120 looks pretty good already! The thing is, with SSW enabled and locked at 45 fps you have the performance headroom to invest anything above 45 fps into higher resolutions per eye or maybe turning on MSAA again. And SSW is definitely needed to keep the experience stutter free. I'm sooo curious about what will be possible with DLSS!

I guess since the Oculus runtime is just emulated by VD, there is no other "handler" than SteamVR for OpenXR available on the system. That's why DCS's native OpenXR won't work. If SteamVR is installed it sets itself automatically as the OpenXR handler and VD needs to use it. Which honestly doesn't make any difference on my end. It runs perfectly here. Can't wait for the next DCS update.

Try these settings in your options.lua as a baseline: In VD set the ultra preset (3090) and turn SSW to always on. In SteamVR set resolution from auto to manual and experiment with resolutions around 3000x3000 per eye.

I ran my Pico 4 and VD via USB cable for a little while a couple months ago. The only benefits are a stable 1200 Mbps connection and maybe a little less latency. But after getting 3rd party accessories to mod the Pico 4 (Logitech Chorus) i went back to more convenient usage with Wifi connection and the USB-C cable on the power adapter to keep charging the HMD for longer sessions in VR. But for people with an older router, low Wifi quality or with a router not in the same room, the USB-C connection might be the best alternative solution. However, you can also connect a Ethernet-to-USB-C adapter to the Pico 4 and achieve the same thing.

@Phantom_Mark 1. get a USB-C 10G cable (USB 3.2 Gen2) / WLAN still needed for the startup copyright protection check of Virtual Desktop 2. Enable Developer Mode: Go to Settings > General > About -> Then scroll down and click 7 times on 'Software Version' 3. install the settings.apk https://drive.google.com/file/d/1PUTpT9boTKssDXQ2qUCLxOKM3LPxQtlA/view 4. Enable USB tethering via the settings app on Pico 4 5. Check Windows network settings for the new ethernet connection and set it to "private" 6. launch Virtual Desktop on Pico 4 and VD Streamer on Windows (WLAN still active on Pico 4 !!) 7. Let VD connect like usual via WLAN, wait a couple of seconds and then switch off WLAN on the Pico 4 VD should now automatically switch to the USB network connection... Steps 1-3/5 only need to be done once.

@propelerIf you want to put it in a shortcut, the line must be "X:\DCS World OpenBeta\bin\DCS.exe" --force_OpenXR The command line option after the quotation marks. You can also make a simple .bat file with: DCS.exe --force_OpenXR

xD yeah, a lot of his "FACTS" do not make sense... Unless he is from the future and already plays DCS with multithreading, DLSS and Vulkan. By the way, you can also use USB-tethering with Virtual Desktop. Works pretty seemlessly and gives constant 1200 Mbps. About OXR Toolkit, yeah. If you still have a cable VR HMD it can help to improve performance. But with a wireless headset, especially fixed foveated rendering seems to degrade compressed streaming quality a lot (also found this by testing MSFS2020 - got 10 fps more but clearly visible compression artifacts in the image center).