Persistent "-othervr" Argument in EXE

When I try to run Aerofly FS4 from the "Games" tab in Virtual Desktop, I get a warning that the "-othervr" argument is specified and it asks me to continue or cancel the request. When I continue, the Meta Link void shows up for a fraction of a second but is then replaced by the SteamVR void and the program runs fine. It also seems to run fine if I just start it from the Steam window rather than the VD "Games" tab. I used to have a shortcut with the "-othervr" argument when I was trying to force it to run OpenXR, but have since deleted it, so I'm not sure where VD thinks the argument is. I don't have any arguments specified in the Steam app properties for Aerofly. Ihave tried reinstalling Aerofly to see if the argument disappears in VD, but it persists.

I know it's no big deal, and doesn't affect the performance of the app, but it's annoying that I can't figure out where VD is getting the argument. If anyone has any ideas, I'd appreciate it.

Zitat von TomC RLG

That command is only used to startup SteamVR in Oculus mode (oculus runtime) if, like FS2/4 it supports Oculus mode. It can only be used when using Link or Air Link. Virtual Desktop doesn't actually use the official oculus sdk's, just their hacked version of it so the command doesn't do anything. VD mainly uses SteamVR as it's openxr runtime, and sometimes VDXR if the app supports it (like msfs2020).

I'm not sure why after deleting this from both your shortcut and Steam app properties launch code it still shows up. Maybe just go to your SteamVR settings and make sure you've selected SteamVR as your openxr runtime. Plus, go to your VD streamer app and select SteamVR instead of VDXR. Also, make sure you haven't done a silly regedit mod previously.

Thanks for the reminder about silly RegEdit mods. I should write these various hacks down when I try them. Will look in the registry…