@Steve Tack Thanks for the link and info! @PsyDev Getting last used controller: http://guavaman.com/projects/rewired/docs/HowTos.html#last-used-controller There's also a new way to get the current contributing sources for an Action: http://guavaman.com/projects/rewired/docs/HowTos.html#get-contributing-input-sources You can combine that technique with the controller type check to get all kinds of info about what the user is doing. There's also a way to track back to find the generalized elements on the Dual Analog Gamepad template that are being activated, though this technique is a bit hacky and will probably be changed at some point. (LMK if you want to know about this.) If you build a lookup table of common controller glyphs, I recommend you use the Element Identifier Id to match instead of the string name. Also, for associating your glyph set to a particular joystick, use controller.hardwareTypeGuid to determine the controller being used. The Guid shows up on the settings page of each HardwareJoystickMap. A Guid of all 0's (Guid.Empty) is an Unknown Controller.