ArmA 3 Hooking but immediately closing.

[Dai-San]

Hi,

I have an issue with getting ArmA 3 to run with Vorpx.

I have a fresh install of ArmA3 which works perfectly well on my monitor.

The issue is when I try to run using Vorpx the ArmA 3 launcher opens fine, I start the game which shows the normal ArmA 3 loading screen, the Vorpx ‘Hooking .exe’ as it should, the Oculus view switches from the normal menu screen to the ArmA 3 loading window but then the game closes and I’m back to Desktop (on my monitor) and Menu screen in Oculus.

There are no errors popping up, I have checked the ArmA logs (no errors).

I have Runtime Switcher set to opencomposite but have also tried it set to SteamVR (same result).

In Configure Vorpx I have tried resetting the ArmA III profile back to default (even though I didn’t edit it) and also tried restoring the game setting but the list is empty.

Any ideas?

Any help would be most appreciated.

Cheers

Bryan

[Ralf]

Please make sure that BattleEye is disabled in the ArmA III launcher. BattleEye blocks vorpX, so it has to be disabled.

If that is not your issue, please first and foremost don’t use that runtime switcher tool. I have no idea what exactly that does, but the name alone sounds like asking for trouble.

If you use a SteamVR headset (or a Quest together with Virtual Desktop), set vorpX to SteamVR in the config app. If you use an Oculus headset, set vorpX to Oculus.

[Dai-San]

Hi Ralf,

Thanks for the quick reply.

I run a Rift-S and the runtime switcher is used because SteamVR causes some games (IL-2 BOS etc) to run badly, stutter etc so is switches it over to using opencomposite instead of SteamVR.

This is not a process running in the background and should not effect Vorpx as other steam games I run in Vorpx work fine.

I have checked in the Vorpx settings and Oculus is selected as the device in General Settings.

BattleEye is disabled in the ArmA III launcher and I even uninstalled it to try that, no joy.

Any other ideas would be welcomed.

Bryan

[Ralf]

Please do not use vorpX wth anything else than the actual, current headset runtimes. No OpenComposite, no “runtime switcher” please. If you change/mess up the headset runtimes with a tool, it doesn’t have to be running while vorpX is active to cause problems.

Your Rift-S should work perfectly fine with vorpX set to ‘Oculus’ in the config app, there is no need to use SteamVR with a Rift-S for ArmA III, let alone any SteamVR wrapper/emulation layer.

[Ralf]

One more thing: there seems to be a new issue related to the Steam overlay. In fullscreen mode the game crashes for me when the Steam overlay hooks the graphics pipeline. Never happened before, but now happens even with older vorpX versions, so probably an ArmA III or Steam change triggering this issue.

Disabling the Steam overlay doesn’t help, it hooks anyway, running the game windowed however does.

[Dai-San]

Windowed was the thing, changed nothing else except forced window mode in launcher parameters and works fine.

Well I say works fine, now just gotta set it up but at least it starts up.

Thanks for the help bud.

[Ralf]

I uploaded a new vorpX version that should work fullscreen again. Might be better for using custom resolutions higher than your monitor res. I didn’t bump up the version number, so no auto-update, but you can get it with a manual reinstall.

[Author]

Posts