Tried changing SteamVR to beta to compare only to notice that it's the very same version with the same issues, 2.14.3.
@kisak-valve can you get someone assigned for this?
@Patola - Is this still happening for you with 2.16.4?
@Patola - Is this still happening for you with 2.16.4?
No, it's not happening; tested with the two games mentioned (AMID EVIL VR and Into The Darkness) and I've been doing tests with other UE4 games in the last months, none of them have this issue anymore.
It's also possible that at the time, when looking for a pattern, I misinterpreted what was happening in #666 which is solved for me now with STEAM_COMPAT_MOUNTS
Then I'll close this out, but ping me it if the problem reoccurs.
STEAM_COMPAT_MOUNTSx1 2026-05
Describe the bug
After SteamVR updated to stable 2.14.3, when starting some games -- apparently UE4 VR games --, the oculus touch controllers are no longer recognized. In vrserver.txt, we have messages like these (game: Into the Darkness VR):
Another affected game is AMID EVIL VR (also UE4 VR game) with the bindings json very similar to Into the Darkness VR.
There are suspicious lines before the bindings errors:
vrserver.txtis attachedIn-game, this equals to you not seeing your hands, or not seeing them moving, and also being unable to interact with anything. If you go to the input bindings for the game in SteamVR, you see a "default" binding but it seems empty and there are no community bindings.
To Reproduce
Steps to reproduce the behavior:
Just play the game via SteamVR
Expected behavior
The game should start and correctly recognize the controllers and in most cases show your hands
System Information (please complete the following information):
I'm using SteamVR stable 2.14.3
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]Additional context
Need to test other game to see if it's an UE4 issue indeed
steam-logs.tar.gz
steam-minidumps.tar.gz