SteamFrame/OpenVR-AdvancedSettings-frame
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add media key bindings, update docs

Browse Source 
All bindings are disabled by default. This is to prevent confusing
behaviour from users who do not know about the new bindings. Forcing
users to manually set up their bindings will also enable them to play
around with the SteamVR bindings interface, which allows for much more
versatile binding options that our current offerings.

All actions are curently in main action set. If the selection of
bindings was greatly expanded it could be beneficial to encapsulate the
options more. The current code is more intended as a proof of concept
until our full binding needs have been uncovered.

The processInputBindings function should probably also be split into
several functions of related bindings, as the amount of bindings grows.
This commit is contained in:
Vasily
2019-01-21 21:19:28 +01:00
parent 3a62ec89be
commit 667711246e
7 changed files with 117 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Readme.md
+11 -6
View File
@@ -83,20 +83,25 @@ To upgrade an existing installation first stop SteamVR and delete the old applic
<a name="bindings"></a>
## Bindings
Advanced Settings supports the OpenVR IVRInput API. In order to make the bindings interface visible, run the `bindingsinterface.bat` file from the install directory. When SteamVR starts, click the menu -> Settings -> Controller Binding.
Advanced Settings supports the OpenVR IVRInput API. In order to make the bindings interface visible, run the `bindingsinterface.bat` file from the install directory. After you're done configuring your bindings, close SteamVR and start it up again. You are now using your new bindings.
If you just run the application normally it will not show up in the bindings interface, this is an OpenVR bug.
Alternatively, you can change the `matzman666.AdvancedSettings.vrappconfig` in `C:\Program Files (x86)\Steam\config\vrappconfig` to have a `last_launch_time` close to the current date (in [Unix time](https://en.wikipedia.org/wiki/Unix_time)). If in doubt, try using the value from [this](https://time.is/Unix_time_now) site. Running the application normally will now make it show up in the bindings interface.
After you're done configuring your bindings, close SteamVR and start it up again. You are now using your new bindings.
The above two solutions are workarounds to a bug in the OpenVR API.
After doing one of the above workarounds, when SteamVR starts click the menu -> Settings -> Controller Binding.
By default no buttons are bound.
The following actions exist:
The following actions currently exist:
| Action | Type | Explanation |
| ------------- | ------------- | ------------ |
| PlayNextSong | Binary/Button | The same as using the media keys. Plays the next song. |
| TODO | TODO | TODO |
| NextSong | Binary/Button | The same as using the media keys. Tells a media player to play the next song.|
| PreviousSong | Binary/Button | The same as using the media keys. Tells a media player to play the previous song. |
| pausePlaySong | Binary/Button | The same as using the media keys. Tells the media player to press play/pause. |
| stopSong | Binary/Button | The same as using the media keys. Tells the media player to stop playback. |
<a name="command_line_arguments"></a>
## Command Line Arguments