Baldrick33

Mine didn't work. Though after renaming my Saved Games\DCS.openbeta folder and doing a slow repair (to see if I got any better performance with MT) it now does!

Works fine with OpenXR (Reverb G1) but SteamVR crashes using the bin-mt exe dcs.log-20230310-160804zip

I think they are just showing an example of the command line. I see no reason why "C:\DCS Open Beta\bin-mt\DCS.exe" --force_enable_VR wouldn't work for example

Looks like it is happening! Open Beta Public testing build Current version number: DCS Open Beta 2.8.2.35759 Next update: Planned 10th March 2023 ( subject to change )

It would have been December 2020. I recall it being a bit of a faff, I think I had to sideload virtual desktop, was probably running at a lower refresh back then too. Given I already had a G1 I spent just long enough to get it to work with DCS and decided not to pursue it further. I am sure things have moved on since then but it has rather tainted my view on headsets that don't have a DP connection, which is probably an outdated view. I might try it again one day just to satisfy my curiosity and update my knowledge.

I have the original Reverb and we have a Quest2 for family stuff. I did try the Quest2 with the official link cable with DCS but found the image significantly inferior to the Reverb. This was some time ago so perhaps the video compression has improved?

I don't agree, you should see my Facebook feed! Social Media is full of people getting hot under the collar and offended over opinions. Of course that can happen here over debates on what ED should and shouldn't do but there is an awful lot of good technical advice and help to be found on these forums. This is a quite complex and factual subject. Being corrected by those with expert knowledge isn't critical although it can be a bit humbling (many of us have posted something we didn't get quite right, as I said it can be complex stuff). It is an important reference for advice, so it needs to be right. Don't let it damp your enthusiasm!

A couple of years in fact! However, DCS only added native support recently so we can use the SteamVR option using its OpenXR runtime.

When I had this happen I created a little batch file (.bat) to rename the folders and copied it into each config\input\[module name]\joystick folder and ran it from there. Something like this: rename "Arduino Micro {C7514800-588C-11ea-8001-444553540000}.diff.lua" "Arduino Micro {42D97A40-DDEC-11e9-8001-444553540000}.diff.lua" rename "Arduino Micro {B98437C0-1FF5-11ea-8001-444553540000}.diff.lua" "Arduino Micro {C152B650-32EE-11ea-8001-444553540000}.diff.lua"

Ok, just to be sure, you need to rename your existing files to the new names, e.g. X56 H.O.T.A.S. Throttle {B80694C0-3ED4-11eb-8007-444553540000}.diff.lua should be renamed to : Saitek Pro Flight X-56 Rhino Throttle {AB9C1880-B7B9-11ed-8002-444553540000}.diff.lua In the Viggen folder I can see entries for both I do find it strange the name of the device has changed as well as the id though? I guess that is due to new drivers with the motherboard swap?

Which module did you copy and paste the controller ids and is that in the Input zip you posted? Edit: Also are all functions of the stick mapped? - roll & pitch will probably work by default.

Thanks. I think it can make it difficult to use videos as stated proof of VR performance/smoothness which was the point I was trying to make in this case. Probably a bad choice of words on my part but I saw a lot of stutters that I wouldn't consider acceptable if that is what I saw in the headset.

No need for the aggression. The video I viewed you described as "smooth and nice" in the Youtube description. It isn't what I consider smooth, which maybe the recording or maybe our subjective definitions. I couldn't run with that and would need motion reprojection to remove the jerkiness but each to their own.

It is in UI Layer. If you set the Reset VR View to something other than Num 5 in the Keyboard category it will work, if you leave it blank it will always default to Num 5.

I know what constitutes acceptable smoothness seems subjective but in the nicest possible way your videos stutter like crazy, if that is a true recording of what you are seeing then I am not sure what you are showing.

Same here. Anything less than 90 feels like a stuttering mess without reprojection on.

Well explained and certainly describes my initial experience with purchasing DCS. Once I got the DCS bug I transitioned to standalone. It avoided adding a third party to the mix and any discrepancies with release dates or third party rules. I had no issue with purchasing in dollars. Plus I had read up about more money going to ED and had made the decision I wanted to support them for future development - as I considered them a key vendor for my hobby. I also dislike having loads of programs running as installers but found I had complete control over the DCS updater and when it ran and where it installed files. So was happy in this respect. I fully understand people using Steam - I am an IT guy so it should be simpler for me to work out. That said there are a bunch of aircraft systems I struggle to get my head around, DCS can be a pretty complex simulation to learn so for me at least setting it up and managing the installation seem the easy bit! However, getting people into DCS to catch the bug to find out all the stuff I did to move to standalone requires accessibility and IMHO Steam provides that. So I am surprised to see such big discrepancies with this module between the versions which haven't been forced upon the developers by Steam's own rules. I appreciate it is down to RB rather than ED but in my view seems an odd choice.

I don't and haven't had an issue.

Though not an ED provided solution isn't that what the Quaggles input command injector does? https://github.com/Quaggles/dcs-input-command-injector

Quite. We know how eagle eyed DCS fans are, if they spot something that shouldn't have been on the aircraft or some fuel tanks that aren't on it that should be there will be a zillion threads and social media posts that need managing! It is quite possible the delays are for the process of the pre release and unrelated to the work going to ready the product for release. The back end pre-order system could have a currency glitch which was expected to be updated in time for all we know. It is just speculation.

To use native DCS OpenXR you need to amend the shortcut. You can still use the opencomposite method of capturing OpenVR output ( I presume this worked previously with the Pimax) I understand ED plan to integrate OpenXR support within the UI, this is a first pass.

Fixed Foveated Rendering works with DCS using the OpenXR Toolkit Setting the render scale in Microsoft OpenXR Tool for Mixed Reality will make it the default, which can be overridden per game using the OpenXR Toolkit.

You can also do it in the Microsoft OpenXR Tools for Mixed Reality - just set a customised render scale.

I now use JoyPro to manage DCS controls, which saves its own profiles. I also have two installs of DCS (Openbeta and Stable) and have a batch file to copy controls from one to the other. So I think I am covered if something terrible happens to my controls in DCS!

I have never bothered with profiles. The input folders for all aircraft and devices can simply be copied. Saved Games\DCS (or DCS.Openbeta)\Config.Input Individual devices can be restored if needed by copying the relevant folder for that aircraft and device (e.g. Throttle - HOTAS Warthog...)