Questions
Map every button at once
A new preset used to start empty, one blank row at a time. In InputConfig 1.5 an empty input device offers Automatically insert available inputs and says what it found, for example "InputConfig has detected an Access Controller, which has stick, 10 buttons." One press lays out a row for every control, under a heading per part of the controller, each waiting for you to choose its output.
What gets laid out
Only what the device reports to its driver, not what its name suggests. A DualSense gets both sticks, triggers, D-pad, every named button, the touchpad, and motion. A DualSense Edge adds its paddles and FN buttons under Paddles and extras. An Xbox pad gets no motion because it has none. The PlayStation Access Controller gets its real shape: one stick, eight sockets, PS and Options. A generic HID pad gets exactly the axes and buttons its layout decodes; the Steam Controller gets its stick and two trackpads; a mouse slot gets buttons, movement, and scroll.
Sections
The rows arrive under headings: Left stick, Right stick, Triggers, D-pad, Buttons, Menu buttons, Paddles and extras, Touchpad, Motion. Click a heading to rename it, its plus adds a row to it, its x lifts the heading off. New section makes one of your own, Sort rows into sections tidies a preset built by hand, and a row dragged into a section joins it. The built-in presets ship this way too.
Then bind
Each new row shows Choose an output where the output goes. Pick a type and the normal controls appear. Nothing is guessed on the output side, so a laid-out preset does nothing until you decide what each control should do, and the Notes line on every row names the control while you work.
Questions
Can I add just one part?
Yes. The input device's ⋯ menu has Insert one part with a submenu per section.
What if the controller is not connected yet?
The layout is a standard gamepad and says so. Connect the controller and use the ⋯ menu to insert the parts it adds.