Vampire: The Masquerade - Justice: Right thumbstick movement doesn't register, rendering resolution cannot be changed

[Neon-White]

Describe the bug

I am not even sure that this is a VDXR bug since I suspect it might be down to the way the game implements its OpenXR support, but here goes.

When forcing VTMJ to run in OpenXR mode (which can be done by adding the -hmd=openxr launch option and enforcing VDXR in the VD Streamer settings), two problems occur:

1. The right thumbstick movement does not register. Thumbstick clicks work. The left thumbstick works both in movement and in clicking. But very specifically, the right stick's movement does not (so practically, it's possible to crouch but not to turn)
2. The game seems to be stuck at 100% render resolution. There is an option to change the scale in the settings menu. The option works when the game is running through SteamVR, but not when running through VDXR. This happens also despite the fact I'm using the Godlike preset, which should use supersampling by default, if I understand correctly (as is also evident by line 15 of the logs attached below)

Please note that without passing the parameter, the game seems to insist on starting with SteamVR, even when the OpenXR Runtime is set to VDXR.

OpenXR.log

Environment

• Game and version: Vampire: The Masquerade - Justice, VtmJustice.exe file version is 4.27.2.0, product version is UE4 Partner Oculus 4.27-CL-0
• Version of Virtual Desktop: 1.30.1

To Reproduce

1. In VD Streamer, set OpenXR Runtime to VDXR
2. Create a shortcut to VtmJustice.exe (executable is present in the root of the game's installation directory)
3. Append the launch parameter -hmd=openxr under the shortcut's Target field
4. Try to turn by moving the right stick left/right

Expected behavior The character should turn left/right when the right stick is moved left/right

[mbucchia]

I'll see if I can somehow obtain the game, but I would not hold my breath.

If you must use the command line option to force OpenXR support, then it means the game is probably never tested in this configuration by the developer.

Can you try with SteamVR OpenXR (not OpenVR) and see if those issues occur? Aka, set runtime to SteamVR AND pass the command line argument? Or even Oculus Link with Oculus OpenXR

[Neon-White]

Thank you for taking the time to go through the issue :)

I tried SteamVR OpenXR (Quest 3, Streamer Runtime set to SteamVR, -hmd=openxr parameter passed) and both issues persist. In that case, if I understand correctly, that narrows it down to the game's OpenXR implementation, so I think we can close this issue.

Edit: The issue persists even when using Index with SteamVR OpenXR - definitely not a VD thing

[mbucchia]

That sounds about right, not much I could do :(