southvast.blogg.se - Scopebox input sources

SCOPEBOX INPUT SOURCES CODE

pchActionSetName - The path to the action set.

This handle is used for all performance-sensitive calls.įor best performance, applications should call this function once per action set name and save the returned handle for later use. See action manifest file documentation for the format of these files.ĮVRInputError IVRInput::GetActionSetHandle( const char *pchActionSetName, VRActionSetHandle_t *pHandle )

pchActionManifestPath - Absolute path to the action manifest file to use for this application.

This call must be made before the first call to IVRInput::UpdateActionState or IVRSystem::PollNextEvent.

Setting and the path provided by this call are different, VRInputError_MismatchedActionManifest is returned. Was set on the Steam partner site, calls to this function are ignored. Sets the path to the action manifest JSON file that is used by this application.

Include your action manifest and all your default binding files in your app when it releases.ĮVRInputError IVRInput::SetActionManifestPath( const char *pchActionManifestPath ).

Repeat 8-10 for other controller types you want to provide default bindings for.

Edit the action manifest and add a default_bindings section that refers to your default binding file.

Usually putting the bindings next to the action manifest file is he best choice. The changes will be saved out to the folder where the action manifest JSON file was placed.

Make some bindings using the UI and then click "Replace Default Binding" at the bottom of the screen.

The system should list "No Bindings Found", but will allow you to create a new one for editing.

From the SteamVR menu, Select "Devices"->"Controller Input Binding" and select your application, which should be listed as the current one.

Make the results from those calls perform the action in the application.

Add calls to vr::VRInput()->Get*ActionData() for each action used by the application.

SCOPEBOX INPUT SOURCES CODE

Add a call to vr::VRInput()->UpdateActionState() at the top of the application's input processing code before reading any action state.actions/my_app) into handles that can be used at runtime. Add one or more calls to vr::VRInput()->GetActionSetHandle() to the application's initialization.actions/my_app/in/DoSomething) into handles that can be used at runtime. Add several calls to vr::VRInput()->GetActionHandle() to the application's initialization.This function takes an absolute path to the application's action manifest file. Add a call to vr::VRInput()->SetActionManifestPath() to the application's initialization.Create an action manifest file to allow SteamVR to know what actions exist in the application.This will enable some options that will be used in later steps. Check "Enable debugging options in the input binding user interface" under Developer settings in SteamVR.To use the IVRInput API in an application, a developer should take the following steps: Users can also select bindings that were shared by other users. Users are able to modify those bindings or create new bindings for new devices.

Application developers can provide default bindings for any controller types they like. SteamVR then binds those actions to actual inputs on a game/vr controller, or more specifically input components provided for the input devices that the user is using. To read controller input state in OpenVR, an application provides a list of the "actions" that represent the operations a user can perform in the application.