GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — InputSystem/Assets/Samples/CustomDeviceUsages at develop · Unity-Technologies/InputSystem

Expand file tree

/

CustomDeviceUsages

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
/

CustomDeviceUsages

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
.sample.json
.sample.json
 
 
CustomDeviceUsages.cs
CustomDeviceUsages.cs
 
 
CustomDeviceUsages.cs.meta
CustomDeviceUsages.cs.meta
 
 
README.md
README.md
 
 
README.md.meta
README.md.meta
 
 
TwoPlayerControls.inputactions
TwoPlayerControls.inputactions
 
 
TwoPlayerControls.inputactions.meta
TwoPlayerControls.inputactions.meta
 
 

README.md

This sample shows how to tag devices with custom "usages" and how to bind actions specifically to devices with only those usages.

This is useful if you have the same type of device that appears in multiple different roles that you want to distinguish when binding to the device. For example, when a device may appear in both the left and the right hand or may appear held in different orientations (say, horizontal vs vertical).

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.