
18 | A Detailed Look at the Unity Integration | Unity
interface guidelines and requirements, please review Interface Guidelines and Universal
Menu in the Mobile SDK documentation.
Control Layout: Mobile
Note: This section describes control layout for the Mobile Unity Integration only.
We recommend that you start by familiarizing yourself with Unity’s input system, documented here: http://
docs.unity3d.com/ScriptReference/Input.html
There are several ways to handle controller input in Unity for a VR app, ranging from using the
InputManager.asset file shipped with the SDK, which pre-populates all of the controller mappings, to completely
writing your own script that refers to the specific hardware keys. Beginning developers may find it easiest to set
up their own InputManager settings and then write their own controller code.
The mappings below are used by the Samsung El-GP20 gamepad and most other third-party Bluetooth
controllers. The actual mapping between a controller and Unity’s input system is up to the controller vendor and
the OS, but it is generally consistent with this schema.
Table 3: Samsung EI-GP20 Gamepad Controller Mappings
Button / Axis Name Input Manager Mapping / Axis
Value
Sensitivity
Button A / 1 joystick button 0 1000
Button B / 2 joystick button 1 1000
Button X / 3 joystick button 2 1000
Button Y / 4 joystick button 3 1000
Left Shoulder Button joystick button 4 1000
Right Shoulder Button joystick button 5 1000
Left Trigger Button n/a 1000
Right Trigger Button n/a 1000
Left Analog X Axis X axis 1
Left Analog Y Axis Y axis 1
Right Analog X Axis 3rd axis (Joysticks and Scroll
wheel)
1
Right Analog Y Axis 4th axis (Joysticks) 1
Dpad X Axis 5th axis (Joysticks) 1000
Dpad Y Axis 6th axis (Joysticks) 1000
Play Button n/a 1000
Select Button joystick button 11 1000
Start Button joystick button 10 1000
Comentarios a estos manuales