Steamvr Please Sign in Again to Continue the Action
Overview
The VR ecosystem is growing every day and with Knuckles we're adding quite a fleck of potential to the space. SteamVR now needs to handle finger tracking and strength sensors. This requires we accept some other look at how we're treatment input now, and how we'll handle information technology in the time to come. Joe Ludwig posted most the new SteamVR Input Organisation a bit here. At present we're going to dive into how you every bit a Unity programmer can use this arrangement to stop worrying about each new input device and focus on creating your virtual reality. We'll commencement from the beginning with downloading the unity plugin, go through adding new actions, bounden them, using them in the editor and code, and finally creating a build.
We have not removed access to the former input functions, only both can't be used at the same fourth dimension. We strongly encourage you to move to the new input organization. All of the scenes, prefabs, the default camera rig, and the interaction system in the SteamVR Unity plugin now use this new system. Simply if you prefer, the old system is on the releases page of our github.
Video version
If you'd prefer a video version of this tutorial y'all can watch it on youtube hither: https://world wide web.youtube.com/watch?v=qo-9CmcKWlY
Downloading the Plugin
This is an significantly different iteration of the Unity plugin. We've fabricated a lot of changes to how input works and we want to make sure nosotros go on to become your feedback. We welcome you to post about issues on our github problems folio here. You tin download the SteamVR Unity Plugin from the Unity Asset Store here or on the releases page of the SteamVR Unity Plugin on github. If you'd similar to propose specific lawmaking changes please practice that with an Result or Pull Request on our github page.
To start off, go alee and download this bundle and excerpt it into a new Unity projection. We recognize that many of our developers are notwithstanding on older versions of Unity and we are committed to standing to support them. Currently the plugin will work every bit far dorsum as Unity version 5.4 and up to 2019.one.
SteamVR Interaction Arrangement
The SteamVR Interaction Organisation has been updated to support the new SteamVR Input System as well as the Knuckles EV2 and EV3. You can find the main scene in your project under Assets/SteamVR/InteractionSystem/Samples/Scenes/Interactions_Example.unity
In this scene you'll find a number of new things. Nosotros've extended throwing examples, added a platformer controller, an RC car, a simple push push button, grenades, and lots of paw samples.
In the throwing section there's now a bones instance of item interaction with velocity based motility similar to NewtonVR. This makes it so your items no longer pass through solid colliders unimpeded. Instead they slide more smoothly around obstructions. A more hearty velocity estimation algorithm has been added to non only boilerplate existing controller velocity merely to match throwing intent even if the bodily release bespeak was a bit too early on or late. And we've separated out the existing styles of interacting with items so you can appraise those equally well. All of these interactable bits are settings on the existing Throwable component.
The platformer and rc auto department has some fun samples for you lot to discover. They're relatively elementary controllers but show a more indirect form of interacting with your world. The controllers concord the actions and get queried with the hand that is holding them.
Knuckles brings finger tracking to SteamVR. This is accessed through the new SteamVR Skeletal Input organization. Duke estimate finger positions and so passes that data off to the driver which interprets that into 31 os transforms. This can be used to much more deeply engage the user with their reality. Just this isn't a feature exclusive to Knuckles. The plugin also includes finger estimations for Vive wands and Oculus Touch on, and we'll be working with Microsoft to add together support for Windows MR controllers as well. By default in the scene you lot'll now see hands likewise as controllers. You tin teleport over to the Skeleton section of the scene to Bear witness and Hide the controller models equally well equally switch between a hand animation gripping the current controller and a hand blitheness that opens and closes freely. To acquire more about the SteamVR Skeletal Input system, view this blog post.
The SteamVR Input window
If you select your Window menu you'll see a new item here called SteamVR Input. Click on that and you lot'll likely become a dialog explaining that you're missing an actions JSON and request if you'd like to use the default. Select Yes and it'll re-create the default deportment.json file, as well equally the related bindings files for a few popular controllers into the root of your project directory. This is where SteamVR volition read them from when you go into Play Mode and where it'll re-create them from when you make a build.
Once those are copied the window will populate a list of actions sets and deportment that are used in the Interaction Arrangement scene. We'll become into adding and modifying deportment later for now nosotros're going to skip down to the lesser of this window to Save and Generate. Clicking this push will offset a bunch of behind the scenes work to plumb your deportment into generated properties for you to directly to access them without magic strings.
When the progress bar completes information technology will accept created a folder in your project called SteamVR_Input with all those code files in it. This path tin be configured through the settings push button at the height of this window.
Testing
Alright, lets see these deportment in... action! Now that you've imported the plugin and generated your actions you should be able to just striking play to become in globe and bank check out the interaction system example scene.
Once you've looked around a piffling bit permit's have a look at the state of the deportment themselves. We have an easy ways to visualize the land of actions at runtime. In the window menu you'll encounter a new choice: SteamVR Input Live View. This is a live view of all your actions separated by action set and controller. Open up your scene view and your game view and so they're both viewable at the same time and make sure the "Maximize on Play" button is unchecked. This button provides significant in editor functioning increases but we desire to meet the rest of the editor right now.
When an activeness's value changes it will highlight dark-green and then fade away to requite you a strong visual indication of state change. A yellow groundwork for an action ways it hasn't been accessed past your code yet. Nosotros only start updating actions once you access them somehow. If y'all're not seeing any changes when y'all press buttons make sure that your controllers are being recognized by SteamVR and that you don't have whatsoever errors in the console.
Calculation an action
SteamVR Input abstracts away the device specific parts of your code then you lot tin focus on the intent of the user - their actions. Instead of writing the code to recognize "pulling the trigger button downwardly 75% of the manner to grab the block" yous can now just focus on the final chip of that, "grab the block". You all the same configure the default for what "grab" means but the user can rebind it to their preference in a standard interface. And when a new input device comes out your users tin publish bindings to share for that device with no code changes on your finish.
Dorsum in the SteamVR Input window you'll find your listing of actions. Selecting an action volition populate its details and permit them to be modified. Boolean, vector1, vector2, and vector3 types should exist pretty straight forward. The skeleton type controls the manus os position/rotations. Pose is the position/location of the controller itself. At the bottom you lot'll come across the localized string for an action, this is what users will see in the binding UI, then effort and give your actions short but descriptive names.
Nosotros've included a sample script and model for a planting example, so lets go ahead and implement an activity for that. In the default action set at the lesser of the In actions hit the plus icon to create a new action. Become over to name and name this activity "Plant". Nosotros want to keep it boolean since the idea is nosotros're either planting or not, and nosotros don't desire to crave this action to be bound since it's not critical to our application so leave information technology every bit suggested. Nether localization lets duplicate the name for English language, just put in "Plant" there as well.
At present lets save and generate. This will salve out a new deportment.json file (which you're welcome to look at, it's just text) then generate a scriptable object and property for our new activeness.
Binding deportment
Once we've created our new action we now need to bind it to a button for testing. So after it'south done generating click the "Open up Binding UI" push. This will open your default browser to the SteamVR binding UI with the selected application being Unity.
If you're presented with a list of games instead of a list of bindings yous may have renamed your Unity executable and yous'll need to become into play manner and click the open binding UI button over again to get Unity to annals correctly.
Select the electric current binding by clicking the Edit button adjacent to information technology. You lot should now see a list of buttons for your currently tracked controllers and actions that are bound to them. Near the tiptop your default action set should exist highlighted red, if you lot mouse over that it will let y'all know that your suggested action "Plant" has not yet been bound.
I'm going to gyre down to my A push since it doesn't have any bindings withal and hit the plus icon next to that. That volition give me a list of options on what sort of way I want to bind for this activeness. I want something elementary and then I'thousand going to select Button. Adjacent to the text "Click" under Push you'll run into a box that says None, click on that and it will prompt you to bind the button click to an activity. Select Plant.
Nosotros want the same response on both controllers and so under the A push on the other hand repeat the same steps.
Now you lot can go to the lesser of the window and click the Supercede Default Binding button. This volition automatically replace the associated binding file in the root binder of your projection with these new changes.
To solidify this change striking the back push button on the binding UI to go to your bindings for Unity. Now you should have an existing "Current Binding" just now also one nether "Official Bindings" that you lot just created. Select View here and and then "Select this Binding" at the lesser left to attach this binding file that you've exported as your electric current binding. If it prompts you about your local changes you can freely discard them since nosotros explicitly exported those changes.
Assigning actions in the editor
We've created, generated, and bound an activeness now let'due south assign it to do something. In the project y'all'll detect a script at Assets/SteamVR/InteractionSystem/Samples/Scripts called Planting. Drag this component onto your hands in the bureaucracy at Player/SteamVRObjects/Hand1 and Role player/SteamVRObjects/Hand2. In the inspector for these two components you'll see a dropdown for the "Institute Action" click on the dropdown and select \actions\default\in\Plant. It'due south that easy to utilise actions in the editor.
Become into play mode and hitting the A button (or whatsoever you bound) and check out your fancy planted flower!
Working with actions in the code
Double click on the Planting script to open up information technology in your IDE and let's accept a wait at how our script interacts with this action.
At the pinnacle you'll see an OnEnable method that has a reference to our action in it. It's calling the AddOnChangeListener method and passing in a method we want called when the action changes. We're also passing in the type of hand that the script is currently on and so nosotros but get change events when the action has changed for that hand.
In OnPlantActionChange we've gotten a notification that the action'southward state has changed but that could be to truthful or to false. We only care about when the button has been pressed down and then nosotros call GetStateDown and again pass in the manus type that we're working with. If the button was pressed down then nosotros execute our planting coroutine. Yous're non restricted to calling GetStateDown from inside an event, y'all can call it from anywhere, within Update, coroutines, etc.
If yous'd adopt, you can reference deportment explicitly in code by named property in the SteamVR_Actions class:
Working with actions in the Editor
Nosotros've also got some helper components if you're more comfortable with the editor than lawmaking. Let's go back to Hand1 and Hand2 and add SteamVR_Input_Boolean components to them. Select our plant activity on that component. Here you'll meet a lot of unity events for different push state changes.
Planting one flower at a time is okay, but I want more, like a lot more. Let's striking the add together button in the OnPress section of the SteamVR_Input_Boolean component. And then drag our planting component into the object section. Nether function select the Plant method.
Now when you go into Play mode you'll plant a flower on press downwards but likewise whenever the button is pressed at all. By default this volition execute in one case per frame. Lots of flowers!
Troubleshooting actions
If you're having trouble with your actions and want a different interface for viewing u.s. at runtime check out the Input Debugger. In the binding UI select your game, select your electric current binding so in the lower right hand corner click the Input Debugger push.
On the left you lot'll see a list of actions and their current states. For a given action the first circle is if the action is active, the middle is if it's currently truthful, and the concluding is when that action has changed.
On the right you'll run across the currently tracked controllers and the states of their individual buttons.
Creating a build
When you go to create a build null has changed every bit far as your workflow goes but 1 new thing will happen. Your action and bindings files will be copied to the build directory aslope your executable. By default they will overwrite what's there to ensure y'all take the most up to date bindings for your build. If you don't want this to happen there's an pick to disable that in the SteamVR Input window.
Source: https://valvesoftware.github.io/steamvr_unity_plugin/tutorials/SteamVR-Input.html
0 Response to "Steamvr Please Sign in Again to Continue the Action"
Post a Comment