Has the Open Beta Just Switched to OpenComposite?

[Taz1004]

For my Vive Pro, SteamVR detected the latest DCS as new game.  I had to reset all the settings like resolution, motion smoothing etc.  Good thing is OpenXR toolkit now works for SteamVR.  I personally am getting much better performance with sharper image.

[andyn]

26 minutes ago, Baldrick33 said:

That is how it worked prior to the update. It now starts up in OpenXR without replacing openvr_api.dll

Without .dll replacement it starts in SteamVR even with this patch; with .dll replaced it starts in OpenXR. No OpenComposite switcher shenanigans. WMR set as OXR runtime. Ran slow repair with extra file removal, as always.

[Baldrick33]

Just now, andyn said:

Without .dll replacement it starts in SteamVR even with this patch; with .dll replaced it starts in OpenXR. No OpenComposite switcher shenanigans. WMR set as OXR runtime. Ran slow repair with extra file removal, as always.

Curious as many who used SteamVR now find it is not using it.

In my case I didn't replace the dll and it starts in OpenXR - not SteamVR which the Stable 2.8 version does. It just doesn't work with motion reprojection any more...

[YoYo]

23 minutes ago, Taz1004 said:

For my Vive Pro, SteamVR detected the latest DCS as new game.  I had to reset all the settings like resolution, motion smoothing etc.  Good thing is OpenXR toolkit now works for SteamVR.  I personally am getting much better performance with sharper image.

No, the picture for me is worse from now. I had better sharpness with ReShade, a lot better that with OpenXR Toolkit with FSR 100% (which I know very well, I use it in MSFS). Its a step back if we are talking about sharpness thanks to external tools according me. It may take some getting used to, but I rather regret the change.

Edited January 25, 2023 by YoYo

[Gryzor]

How I can use reshade in 2.8.2 ??? I used to sharpen in RV. DXGI.dll don´t work anymore... please help

[Burt]

Disabled Motion Repo and getting increase fps and actually runs great it’s just the slight judders I dislike. 

[maxTRX]

1 hour ago, Baldrick33 said:

Curious as many who used SteamVR now find it is not using it.

In my case I didn't replace the dll and it starts in OpenXR - not SteamVR which the Stable 2.8 version does. It just doesn't work with motion reprojection any more...

Well... I always thought my communication skills were lacking. C'mon ED

I was a happy camper in SVR with no 'composites', tool kits, replacement dll's, reshades, whatever.  I have a decent rig and the only adjustment I made was 200% resolution multiplier for DCS. No AA of any kind. Aniso x16 in DCS.  Ran very smooth in SP (I don't do MP currently)  FPS 50 ~ 80, well 90 looking at the sky hehe.

When I fired up DCS after today's update, I noticed a popup message on my WMR window, telling me that without OXR 'some' games might not play correctly... hmm. There was a 'Fix it' button next to it so... I fixed it, lol.  Basically, the SVR box disappeared and I wasn't able to adjust anything. The sim started though and looked good. Smooth and fast. I was intrigued tho' and decided to force it back to SVR in the developer options. After the restart... looked good for a few seconds then micro stutters started. Every 10 secs or so.  I can run modest FPS but the stutters drive me nuts.  Went back to OVR and decided to stay there for now. No stutters, FPS the same as before. I'm still running w/o any AA. Looks good but yea... slight shimmers.

I'm not going to d/l any extra stuff for now.  I like to fly, not stare at FT graphs and spreadsheets. I admire people that have patience for all this. I'm just not one of them.

[NatoAviator]

@YoYoDitto on Reshade hands down, with SteamVR Reverb G2, best clarity and colours...now Zip, it don't work.

SAME also with the VRK kneeboard app v 1.0, which was native to Steam...

TBH, I really don't grind on ED, but there comes a point when the community needs to be given a heads up on O.B updates...they seem to be rolled out without any measureable VR Q&A.

[MorrisTheCat]

I spent all afternoon thinking the problem was my computer when DCS kept crashing in the menu or the mission load screen.  I went through reversing a whole lot of changes I made to my setup and even did a windows restore...of course that was all pointless and a waste of time because as you've all described above the issue was the update.  I mean, it's great and all that they've integrated WMR headsets but some heads up would've been nice and even some info to let us know to turn off Motion Reprojection to avoid the crashing.  

With that said though, I cannot fly anymore without reprojection.  The stuttering is too much on my system.  If I had advance warning I would not have updated...

Anyway, hope they'll implement reprojection soon but I have my doubts as they've taken this long to get basic WMR integration. I will hold of on any new module purchases or pre-orders until then.  Honestly, DCS was working fine before this update.  I had no issues copying over the dll file after an update in the past.  Would have much preferred that over the state it's in now...

[Dentedend10]

I don’t use OpenXR but use SteamVR

Today’s beta still works for me. Although when I launch DCS the VR view is way above the menu. I have to recenter. Also, the controller bindings are not quite working with my G2 controllers.

I have motion smoothing on in SteamVR

[MorrisTheCat]

Thanks Denteded10.  I haven't used SteamVR for DCS in over a year.  I found OpenXR to run much smoother.  Maybe SteamVR has improved in the last year or so and worth a try again?

[Thinder]

I just had a heated argument with a member of Steam VR support here is the story: I flew DCS/Mirage F1 without any problem in both solo and multi-missions with the following combo.

Pico4. Streaming Assistant. Steam VR Beta.

I've recorded all my flight tests with it, both with Mirage 2000C and F1, it wasn't perfect due to settings needing fine tuning but it worked, but a few days ago, previous to DCS update, I started to experience a few issues such as the F1 missions starting in map (F10) again, not being able to go back to cockpit view.

I did send a ticked to DCS support and their solution worked for a little while, also switching to DCS Beta had something to do with it, but then Steam VR started to raise a hell of a mess in the combo, starting without command, even without Streaming Assistant ON, and shutting DCS down when I try to close it,

Steam support always come back with the same excuse "Pico 4 is not supported" apparently they know little about their own software, they are in full denial and refuse to aknowledge that it actually worked, I recorded several VR videos to prove it, Mirage F1, Mirage 2000C, F-15, while testing settings for my new GPU.

Now it's getting worse: The F-5 also is not supported but I was able to fly it for a short while before the update, the Mirage 2000C also seems to experience some issues, so I wonder really if developers of both Steam, Open XR and DCs care about it at all.

We're looking at alternative solutions to Steam VR, because obviously they are unwilling to even try to figure out if something have changed from their side.

Pico doesn't offer much of a solution either, they have their own version of Virtual Desktop in store, which I purchased but am unable to use because it requires a Streamer App which doesn't offer the option to open the game, although I'm looking for some lucky breakthrough there too...

What a mess, still working at it.

And... BINGO.

I managed a flight test in the F1.

First I reinstalled Pico's recommanded Virtual Desktop streamer  and I already own their version of Virtual Desktop (available in their App store), then reinstalled Steam VR Beta and when I was in the room, I started the Virtual Desktop app on screen, it was that of Steam but I managed a bad run (no command settings such as AF etc) in the F1 mission Interception.

Edited January 26, 2023 by Thinder

[lvnona69]

9 hours ago, parxuk said:

Got it running but trying to fly is useless.

Despite my PC not being awful, I always needed to force motion reprojection to on. Without it or on automatic, even with low settings on maps (especially Syria) the outside is blurry when looking around and would give me a headache. Tried 60HZ but it hurts my eyes.

Now I can only force it to auto in order to get DCS to run, and performance is bad and game unplayable for me in VR.

I've been waiting for a push to give Falcon BMS a go (now it supports VR) and I think this is it. 

Same here - I had with Motion Reprojection ON smooth 90fps air and ground and now it is UNPLAYABLE! Specs - 12900KF, 3090, 32gb DDR5, High Settings, VR G2

[Thinder]

1 hour ago, lvnona69 said:

Same here - I had with Motion Reprojection ON smooth 90fps air and ground and now it is UNPLAYABLE! Specs - 12900KF, 3090, 32gb DDR5, High Settings, VR G2

They will eventually sort it out but if you can't wait, try my Steam solution. Steam VR Beta.

I'm editing the video of the last VR test on the Mirage F1EE.

Normally I shouldn't be able to fly it because the F1s are not supposed to be supported by Steam but two things stroke me during this test flight:

First, the quality of the image is better than what I had previously, although I realized my mirror reflection was off, no jerkiness, missed frame and a much higher level of details in the replay, the image on the Pico was also better, I'm still trying to figure out what I've done to get this to work this way.

I'll post the HD upload as soon as it's done for you to see for yourselves, I know many of you guys don't have the dog's b@ll@cks for system but this solution is an alternative if it stays stable, until we can find better, for the Pico4 user it's a good one.

 

Edited January 26, 2023 by Thinder

[Baldrick33]

1 hour ago, Thinder said:

They will eventually sort it out but if you can't wait, try my Steam solution. Steam VR Beta.

I'm editing the video of the last VR test on the Mirage F1EE.

Normally I shouldn't be able to fly it because the F1s are not supposed to be supported by Steam but two things stroke me during this test flight:

 

Steam VR beta has always been available for the standalone version of DCS so I am not sure what you mean?

[Thinder]

9 minutes ago, Baldrick33 said:

Steam VR beta has always been available for the standalone version of DCS so I am not sure what you mean?

The F1 is not supported by Steam VR and from all the test I conducted with Steam VR Beta, this one is the best with no jerky head movements, clear vision of the environment at lower altitude higher level of details and clarity, in short, way better than the usual Steam VR performance.

I'm starting to think that the other apps might have something to do with it, because normally I had a refresh rate 20Hz lower than that of what the Pico could take, no such problem here apparently, and I'm running DCS Beta.

 

Edited January 26, 2023 by Thinder

[Elidji]

I use the G2 and my game still use SteamVR.

Do I have to do something to use OpenXR ?

Edited January 26, 2023 by Elidji

[Baldrick33]

8 minutes ago, Thinder said:

The F1 is not supported by Steam VR and from all the test I conducted with Steam VR Beta, this one is the best with no jerky head movements, clear vision of the environment at lower altitude higher level of details and clarity, in short, way better than the usual Steam VR performance.

 

SteamVR is a separate program from the Steam version of DCS. It is used by many headsets. For example my Reverb uses SteamVR via the WMR for SteamVR bridge. This is independent of any VR program running on it. So since I got the device in 2019 SteamVR (and SteamVR beta) was the only way to run VR with DCS standalone. Only recently has OpenXR become an alternative option.

It is often confused that SteamVR and the Steam version of DCS are somehow intertwined.

2 minutes ago, Elidji said:

I use the G2 and my game still use SteamVR.

Do I have ton do something to use OpenXR ?

In the WMR portal you should be able to change the OpenXR runtme to WMR.

You may need to download the Microsoft OpenXR Tools for WMR from the Microsoft Store if you don't already have it.

[YoYo]

What is strange and incomprehensible to me is the fact that there was no official information about it, not even in the changelog. 

The change is huge and requires some procedure for DCS to work again. From what people are reporting here, the problem is Oculus and Pimax, which has now started requiring SteamVR, while WMR and Reverb owners should now use OpenXR (forced by a dll change).

This causes a lot of frustration as some DCS stops starting, freezing when loading missions (while loading map), or slows down to menu to slides show. On the other hand, for people with Pimax stopped working reprojection (perhaps also people with Oculus). For me, on WMR and OpenXR, reprojection works without a problem but not from the beginning.

This causes a lot of frustration and the change should be officially announced with instructions on what to do. I spent an hour or more wondering what was going on (of course like most I thought the patch broke my DCS due no any info about changes for VR users). I repaired the DCS and finally got to the options in SteamVR (only this is required: settings > advanced options (hide tab) > deafult setting "set steamVR as OpenXR runtime") and it gave me a solution to make DCS work properly with OpenXR now. But this requires instructions on how to proceed, not making such a final change without even mentioning it in the changelog.

Unfortunately, in this case, ED presented itself as an unprofessional company, suddenly introducing such a significant change without any communication, prior notification and providing a solution. Again, it turns out that VR users are basically omitted in thorough tests and diagnosis . It wasn't a nice move.

Edited January 26, 2023 by YoYo

[Baldrick33]

4 minutes ago, YoYo said:

What is strange and incomprehensible to me is the fact that there was no official information about it, not even in the changelog. 

 

It is a massive change to how VR works in DCS. Incomprehensible to me too!

[Mars Exulte]

13 minutes ago, YoYo said:

What is strange and incomprehensible to me is the fact that there was no official information about it, not even in the changelog. 

 Yeah, I'm not one to rag them, but this clearly created unholy hell for a lot of people and was not officially notated until less than twenty minutes ago with a sticky finally... nearly a full day after release. Seriously, nobody thought a fundamental change like this needed to be communicated ahead of time? I wonder if we'll discover MT and Vulkan suddenly appear and people's rigs inexplicably stop functioning @@ It's just dumb.

[some1]

As mentioned in the other thread, it's possible to bring back the old native support for SteamVR using command line parameter. Good that it was left as an option, at least for the time being.

1 hour ago, SPAS79 said:

Just do a shortcut like 
Start DCS.exe --force_enable_VR  --force_steam_VR
that should fix it. 

[Thinder]

10 minutes ago, YoYo said:

What is strange and incomprehensible to me is the fact that there was no official information about it, not even in the changelog. 

The change is very permanent and requires some procedure for DCS to work again. From what people are reporting here, the problem is Oculus and Pimax, which has now started requiring SteamVR, while WMR and Reverb owners should now use OpenXR (forced by a dll change).

This causes a lot of frustration as some DCS stops starting, freezing when loading missions (while loading map), or slows down to menu to slides show. On the other hand, for people with Pimax stopped working reprojection (perhaps also people with Oculus). For me, on WMR and OpenXR, reprojection works without a problem but not from the beginning.

This causes a lot of frustration and the change should be officially announced with instructions on what to do. I spent an hour or more wondering what was going on. I fixed the DCS and finally got to the options in SteamVR and it gave me a solution to make DCS work properly with OpenXR now. But this requires instructions on how to proceed, not making such a final change without even mentioning it in the changelog.

Unfortunately, in this case, ED presented itself as an unprofessional company, suddenly introducing such a significant change without any communication, prior notification and providing a solution. Again, it turns out that VR users are basically omitted in thorough tests and diagnosis . It wasn't a nice move.

 

Just imagine getting a Pico 4 not supported by Steam to run with an incompatible module in DCS Beta and you'll have an idea of the state of confusion I'm in...

There are solutions up there and I'm constantly looking for them, from my humble PoV, some apps are kinda mixing together to get the result I had, I'm thinking about the pico version of Virtual Desktop which kicks-in before I start that of Steam in the room and/or OpenXR which says it doesn't detect my Pico while Windows 10 Pro does.

In short, when it comes to VR Apps, it's a magic roundabout and developers are just behaving like you said, unprofessionally.

[YoYo]

5 minutes ago, some1 said:

Start DCS.exe --force_steam_VR

tested yesterday, it doesnt work for me after yesterday's patch. OpenXR works always, not StemVR. The only difference is that it doesn't kill the process but an error occurs. But I see longer line, that I was tested (I can try it) "--force_enable_VR  --force_steam_VR " .

Edited January 26, 2023 by YoYo

[some1]

Hmm, the command line options works here. I even got the vrperfkit working.

1 hour ago, Baldrick33 said:

It is a massive change to how VR works in DCS. Incomprehensible to me too!

Just the fact that turning reprojection on completely breaks DCS now shows you how little attention and testing was involved.

Edited January 26, 2023 by some1