Device Management
Once your plugins have run, every physical and virtual device they found is listed in Customise. This is where you name devices, pick templates, hide the ones you don't care about, and decide how they merge with each other.
The Customise Area
Customise is split into four sub-pages in 2.2:
Master list of every device. Rename, assign a template, hide, or alias it to another device.
Per-profile overrides. Rename or hide a specific aircraft/profile without touching its source.
Replace game action names with your own text. "Weapon Fire Primary Mode Toggle" → "Guns".
Cascade bindings from one profile into another. Covered on the Merging Bindings page.
Renaming a Device
Device names come from the operating system and aren't always friendly. You can rename them to simplfy.
- Go to Customise → Devices.
- Select the device in the list on the left.
- Edit the Display Name field. The new name is used on every diagram going forward.
Display names are a label only; they don't change how the plugin matches devices. The underlying GUID is preserved.
Assigning a Template
Each device needs a template before you can export. The template is the SVG layout (button positions, labels, axes) for that specific piece of hardware.
- Select the device in Customise → Devices.
- Pick a template from the dropdown. Templates that match the device name are suggested first.
- If your hardware isn't listed, see Custom Templates.
The template assignment is also visible on the Export tab so you know what each device is about to render.
Hiding Devices
Joystick Diagrams will find every device referenced in your config files, including virtual devices, disconnected hardware, and test rigs you've long forgotten about. Toggle Hidden on any device to stop it appearing on diagrams globally.
Device Aliases
Two plugins can report the same physical hardware under different GUIDs. Some games/tools don't even use GUIDs in these scenarios a placeholder identifier might be used. This feature lets you tell Joystick Diagrams to treat them as the same device, leading to merge of all binds.
Setting up aliases and choosing how conflicting bindings merge is covered on the Merging Bindings page.