wrycu

To add on to this, I also had the "move really far forward" thing come about when my VR and TrackIR recenter buttons were the same thing and TrackIR was running at the same time (even though it obviously wasn't in use).

Thanks for the help - I FINALLY got it working. I'm not sure why, but I needed to do the OpenXR step in order to use --force_steam_VR and have OpenVR off in Varjo Base. I now have a stable framerate and a single cursor! I briefly tried the eye settings you asked for (now that I have a functioning Aero) and it made it my head hurt - I had to revert it.

It just occurred to me that I skipped this step in the guide: > How to: Varjo's OpenXR Mode since I'm using SteamVR. Was I supposed to complete it in order for OpenVR to be off and OpenXR to be on?

The same problem happens with other games, but only while OpenVR is disabled. With OpenVR enabled, SteamVR launches and works properly. no SteamVR complaints: SteamVR errors:

Toggled OpenVR ON and restarted the headset/system (via the "Support" tab) and ran DCS with --force_steam_VR, which opened with a single cursor (!) and was super laggy. Toggled OpenVR OFF and restarted the headset (still with --force_steam_VR) and I get the same connection warning and DCS launches in flat screen mode only.

First of all, thanks for the help! I ran a cleanup/repair and re-opened DCS (with the binary directly - not using the config tool). It opened in VR with the split cursor issue. I then re-opened it with --force_steam_VR and it launched flat screen and gave this issue in SteamVR: Which is the same problem @moggel was having (it only pops up when using --force_steam_VR)

I use a DCS config manager to swap between VR/non-VR (can't get DCS to launch in VR without it) and haven't found a way to pass command-line args to DCS to fix the cursor being split issue. Any suggestions?

The modding/scripting functionality that these relatively simple changes would make is huge, not to mention the beginning of a relationship where ED listens to the community and builds out APIs we've actively requested. This has my full-fledged support.

Allowing the community to expand base game functionality is part of what makes a product great. Please implement this, even if you plan on having similar functionality natively.