Supmua

According to my personal testings, clicking Apply changes to the global or DCS profile via NVI is all that is needed to get optimized stereoscope and clarity. I don’t know for sure if this also applies to other people’s PC.

No idea for the quick fix on other issues, seems like it is going to need a firmware update for this. I already emailed Dragon about it. You might have to use the older firmware for now. Didn't realize they already annouced the Haptics, lol. Yep that's to one to get. Haptics feedback, how cool is that.

I don't think changing stereo profile to on, or any additional parameters, did anything, it is just so that I can click Apply Changes afterward and cause it to save over the default profile. Sometimes unless you make a change clicking save will not save.

Ok found the CM2 and just tested it. Note that I'm using experimental firmware which is a little further ahead than the single HID device firmware but mostly similar. So, basically there are switches that are continuously on or depressed with that grip (#31, 35, 39-46, 48-60). But all the buttons on the grip works normally (those excess buttons in ON state are not attached to any button the CM2 grip). And interestingly, if you press the paddle button 3 is activated but all those ON switches become deactivated. Since all the buttons on the grip works for me it should work fine in DCS, but you'll have to do manual bindings (select the button number directly) in DCS instead of pressing a button to assign--as numerous buttons are already ON by default and will be registered instead. Also make sure that those ON switches are not already assigned to any function in DCS, so a clean binding is recommended. This is likely fixable via firmware, but check with Realsim tech support for this. I'll also let Dragon know about this issue.

Do not buy any RS grip yet *hint*. I still haven't found the CM2 (hidden somewhere in my basement), only found my VKB stuff.

New GeForce driver is out. I urge people to update then try DCS right away without making any change to the current profile and then compared the visuals after you make the change with NVI. Let’s see what happens. I’m not going to dial in any parameters with NVI, just going to hit apply changes on the second run. EDIT: Got slight increase in 3D effect and clarity again after NVI apply changes (This time I made no parameter changes other than stereo profile on, but I don't think any input besides Apply Changes has any meaningful effect). So I'm mostly convinced that every new update did something bad to the default profile (at least my profile) causing reduced clarity and less 3D stereoscopic effect and this got corrected after running NVI.

The CM2 base is also my go to for center mounted setup. It is very hard for me to use other joystick grips after owning the Realsim ones.

I’ll check with my CM2 grip later today, if I can find it (haven’t touched it in the past few years).

The only supported non-Realsimulator grips, I believe, are the Thrustmaster ones. Virpil grips DX buttons are assigned differently and will likely need special firmware for compatibility, which is not likely to happen. There’s also some new features related to the upcoming hardware that will set it further apart from conventional joysticks

I managed to reproduce this screen…by running SteamVR without Varjo Base app first. So, first run Varjo Base...then optionally SteamVR either by manual start or via Steam compatible apps.

And if you like post processing utility, Reshade 5 is highly recommended. Back when I was still using the Index, Reshade made me feel like getting a new headset with just sharpening filter. There is a Reshade guide in the Varjo general guide thread which is applicable to any SteamVR headsets, the suggested numbers won’t be the same due to different screen types and resolutions.

With the latest SteamVR beta, I don’t see significant performance difference between OpenVR vs OpenXR mode on my Aero headset so I’m actually using Steam’s OpenVR mostly these days. I think Steam’s OpenVR mode is just fine for SteamVR headsets such as Index.

This thread is about Varjo Aero general setup, not sure the content here is applicable to the Rift S.

Not sure it’s possible with DCS at present. The OpenXR mod works by translating Steam’s OpenVR into OpenXR, but it also bypasses the SteamVR hence the supported headset has to have direct access to OpenXR. I think the Valve Index can only use OpenXR via Steam so it won’t work with DCS. For the very few games out there that use native OpenXR API (MSFS, Hubrix demo), the toolkit should work. The devs can probably make it run via Steam’s OpenXR, but the very purpose of this mod is to reduce Steam overhead by bypassing SteamVR so even if it works you won’t see any performance increase.

https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners

That must've been the case with the newer OpenXR mod then, the old version used to identify the Aero as the Reverb G2.

Interesting, I don't have the VarjoAero.lua one. Is the content inside like this? EYE_LEFT = { L_OUT =1.395020, L_IN =0.701069, L_TOP =0.759638, L_BTM =1.010263, } EYE_RGHT = { R_OUT =1.357678, R_IN =0.703286, R_TOP =0.755739, R_BTM =1.011197, }

Without force_steam_VR, DCS will automatically use Varjo’s OpenVR mode which doesn’t need cross eye adjustment (but as I said, not recommended as it has performance and GUI issue at present). This would’ve been an ideal mode to run DCS if Varjo and ED can work it out, since it doesn’t need Steam GUI and/or OpenXR translation layers. The cross eye tool window at present will keep popping up unless you have already created the corresponding headset.lua file after pressing SAVE, which only comes up after a parameter change is made (by mouse clicking) in Varjo’s OpenVR mode—but this mode doesn’t need it as it already has cross eye adjustment done automatically.

The Oculus lua file is generated by cross eye tool if you use OpenComposite OpenXR mode (it incorrectly ID the Aero as Oculus CV1), the hedy.lua file indicates the Aero for OpenVR mode (I have no idea why they don’t use Aero.lua or something more intuitive—sometimes the way some programmers think is a bit eccentric I guess). So only one is used depending on which API you choose to run DCS with.

Setting your own default center view (NUM5) might help. I always do this since I like to be a bit further way from the HUD. Procedure: 1. NUM5 to activate default center view. 2. Adjust as desired (hold down RSHFT+RCRTL then press NUM2/4/6/8 for down/left/right/up, also / or * for zoom in or out). 3. RALT+NUM0 to save the new center view. 4. Press VR recenter keybind to recenter.

Those numbers are for Steam's OpenVR with the default distortion profile only, if you use OpenXR then it likely won't be the same. I was getting a bit nauseous using those numbers also but for the sake of science, lol...and better 3D effect. Anyway, stick with what is working for you which seems to be OpenXR in this case.

Are you using the latest Varjo Base software 3.5.1.7? Also try SteamVR beta, I'm using version 1.22.10 right now. You don't need OpenXR to run DCS, although it's also an option. I left mine on because I use it for MSFS.

It seems there's a problem with SteamVR and DCS with your setup. Can you run other SteamVR games from Steam Store at all? or this issue is specific to DCS?

K, I need some of you guys (with functioning Aero of course) to help me test something if you don't mind. My theory is that increasing eye separation will increase 3D depth perception, so doing that with Cross eye tool should have similar effect. What to do: 1. Delete hedy.lua in \Saved Games\DCS.openbeta\ folder 2. Run DCS with Cross eye tool and dial in the numbers that I circled in the pic. Note that the top numbers are for OpenVR with default distortion profile only, if you use the new experimental distortion profile use around 1.480 for both L_OUT and R_OUT. 3. Fly around and see if you have improved 3D effect or perception.

Do me a favor, try clicking on OpenVR switch in Varjo Base once (I know it’s probably off but click on it again just once). Then Reset Varjo via Base Then try to run DCS via SteamVR again.