steamvr_unity_plugin
steamvr_unity_plugin copied to clipboard
ValveSoftware
SteamVR uses legacy bindings on first startup of game and not the bindings that shipped with the game.
This only happens when the game is installed trough steam. Running in the editor and from the local build is fine. For most users of our game a simple restart fixes the issue and game recognizes the proper bindings and works. However for some this does not work. What can I do to fix this ? I'm using the SteamVR Unity Plugin 2.6.1(skd 1.13.10)
This could be a issue with the app key in the binding files. You can try removing the app_key line from the actions.json and bindings json files and see if that fixes the issue. The next version of the plugin will fix this.
The version that should fix this is out now: https://github.com/ValveSoftware/steamvr_unity_plugin/releases/tag/2.7.1
I upgraded to the 2.7.1 release and the issue still persists. In the steam vr settings I have set the app key to steam.app.[ourAppId]. We tried a fresh install by deleting all game files and steam user settings. Installing the game results in the legacy bindings being used. Running the game a second time results in the correct default bindings (the ones we created and ship with the game) being loaded. I also tested by deleting the app key line from the generated json files, the result was the same.
We also have this issue. Through viveport though not steam store.
Yes, we are also having the problem in vieveort and any other platform that relies on SteamVR. If a fix is not comming a temp workaround would be nice.
Does deleting the app key line from the JSON not fix the issue?
No it does not.
Can you send me a simple project that reproduces the issue? Or link me to one?