No Explicit Support for HP Reverb G2 + New SteamVR Update = No Hands

[Jackalgirl]

Describe the bug?

With the latest update of SteamVR (on 5 July 2023), Steam will pass the Oculus controller to a VR game if the game does not explicitly support the user's controller. For users of NeosVR with HP Reverb G2 VR sets, this results in users' controllers being entirely disabled. The issue can be temporarily fixed by selecting "Disable Steam Input" in the "Controllers" section of game settings (WMR for SteamVR, SteamVR, NeosVR), but this solution appears only work for one play session after making these changes; upon subsequent game loads, SteamVR overrides these settings.

Prior to the SteamVR update, the Neos log would state:

loaded VR device: HP Reverb Virtual Reality Headset G20

After the SteamVR update, the Neos log would state:

loaded VR device: Oculus Quest2

The current solution is to revert/downgrade SteamVR to the previous version (instructions for how to do this are available in the tutorials channel on the Discord).

Relevant issues

No

To Reproduce

Using an HP Reverb G2 set on a Windows machine with the current July 5, 2023 version of SteamVR, log into NeosVR. The dashboard menu will display the Oculus controller guide, and you will have no hands (and subsequently no way to interact with the game other than by looking around).

Expected behavior

When possible, patch NeosVR so that it will respond to SteamVR with positive support for the HP Reverb G2 so that SteamVR will not "help" the user by defaulting to/overriding user's wishes and falsly indicating that the user has an Oculus.

Here is a controller guide for the HP Reverb G2, if you'd like to add a guide to the dashboard as well:

Log Files

No response

Screenshots

No response

How often does it happen?

Always

Does the bug persist after restarting Neos?

Yes

Neos Version Number

2021.11.10.1253

What Platforms does this occur on?

Windows

Link to Reproduction Item/World

No response

Did this work before?

Yes

If it worked before, on which build?

2021.11.10.1253

Additional context

It's not the version of Neos that is the issue per se, it's that the newest version of SteamVR does stuff that didn't impact Neos before, but does now.

Reporters

Solution (downgrade/reversion) provided by:

• Madameblu Users affected:
• Jackalgirl7
• Mr. Claw#6931

[shiftyscales]

Thanks @Jackalgirl. I looked into this the other day, and determined a potential cause of the problem. It appears that there are binding files defined, but the bindings seem to have some properties misconfigured.

As a temporary solution, you can fix this on your end by creating custom bindings. If you edit the default bindings, go into the 'options' there should be an option to disable SteamVR's new emulation mode. If you disable emulation, the controllers will function as normal again.

[Jackalgirl]

Hell Shifty, and thank you! If you're talking about the options within Steam, which you can set for controllers for SteamVR or for the games (Neos and/or Windows Mixed Reality), I actually did that. I disabled Steam input, but it only worked once per game/experience. When I exited the game and reentered it, it overrode my choice, and I was once again without hands and looking at an Oculus controller map on my Neos dashboard. I think there was one of the three I did not try, so I can't for certain state whether that one would have "stuck".

Now, if there are other settings that I can change (that is, if I can create custom bindings somewhere else, such as within Neos or in configuration files), I would love to give that a try. Could you point me in the right direction?

[shiftyscales]

SteamVR Settings > Controllers > Neos VR > Custom > Edit This Binding > Options (top right corner) > Compatibility Mode > None > Save Personal Binding.

It's not related to Steam Input, I am referring to the SteamVR bindings which can be found through the SteamVR settings, @Jackalgirl.

[Jackalgirl]

Hi there, and thank you for pointing me in the right direction! I will update SteamVR and make those changes, and report back here. : )

[Jackalgirl]

Okay, update: it worked! Mostly. I'd been trying to change the settings from within the Steam Client, and did not realize I had to be inside SteamVR to make these changes. I did as you suggested and it worked, and also persisted across both multiple exits/reentries as well as from launching NeosVR in SteamVR mode directly from the Steam client.

However, with this new update, my controllers now vibrate whenever I press a button/pull the trigger, etc. This is super annoying, and reverting back to the previous version had fixed this. Nothing that I set seems to be making a difference at present, but I will see if I can find a solution that doesn't involve reverting.

Thank you, Shifty!

[shiftyscales]

@Jackalgirl - SteamVR custom bindings also allow you to control the haptic intensity as well. Hopefully you can find them alright.