From docs/auto-group.md in the repository (generated, always the current text).
Auto Group puts the same function of every DCS aircraft and every other supported game into one relation. For example, "CMS forward" (dispense) of the F-16, the F/A-18, the A-10C, Falcon BMS, Star Citizen and War Thunder goes into one relation, so one button does it in every aircraft and game.
Games with a function catalog: DCS (all modules and input layers), Falcon BMS, IL-2 Great Battles, IL-2 Korea, Star Citizen
(ship controls), X4: Foundations, Elite Dangerous, MSFS 2020 and 2024, X-Plane 11 and 12, War Thunder, Arma 3, Arma Reforger and
WARDOGS. --planes also takes a game id (StarCitizen, X4, EliteDangerous, IL2Game, IL2Korea, FalconBMS, MSFS2020,
MSFS2024, XPlane11, XPlane12, WarThunder, Arma3, ArmaReforger, Wardogs).
- GUI: Relations → Auto-build relations from all my actions... → By function (Auto Group) (Preview first, then Apply).
- To group only some functions or aircraft, describe them in a sentence: Group by description.
- To build one relation step by step (one action, then what fits with one click), use the relation editor; its suggestions use the same catalog and your learned style.
- CLI:
engine relations auto-group [--preset all|wing|era|purist] [--no-substitutes] [--planes p1|p2] [--replace] [--dry-run] [--no-map]. - Head tracking: when the profile's head-tracking answer is yes (the Setup wizard's question, setup-wizard.md), no look-around relation (snap views, look axes) is made for the sims that support head tracking or VR; the recenter stays. The suggestions follow the same answer.
#Presets
| Preset | Relations |
|---|---|
all |
One relation per function for all aircraft (default). |
wing |
Split into fixed wing and helicopters. |
era |
Split by wing type and era (WW2, Korea, early/late Cold War, modern); spaceships form their own group. |
purist |
Only the basic flight controls are shared (axes, trigger, trim, gear, flaps, brakes, canopy, kneeboard). Every other function gets one relation per aircraft. |
#What it changes
- Existing relations of the same name (or the relation that stands for the function in your profile, whatever its name) keep their binds and only get the aircraft they are missing.
- Commands you already use in another relation stay there. They are listed under "Kept", so a bind is never moved behind your back.
- Your own relations (not tagged
AutoGroup) get only what is their function: an axis that only the function catalog reads as it, its title without any of the function's words (a gunner seat's "Gun Up/Down" for pitch), stays out and is listed under "Kept" (KeptOutOfOwnRelations). Star Citizen's catalog spellingmap___actionis the profile'smap|action, so an action already in the relation is never added twice. - New relations get the group
AutoGroupand a readable name ("Anti Skid Off", "AI menu down", not the catalog'sAntiSkidOff/ai_menu_down; a relation of the catalog's spelling from an earlier run keeps being used).--replaceremoves those first. Your own relations are never removed. - In the GUI the preview is a list (new and extended relations with their actions and aircraft, what was kept) and
Applyasks first with the counts. - Disabled entries: a command switched off for an aircraft in a relation stays off in that relation ("Kept
Disabled By You"), and so does a suggestion you dismissed there (
DismissedSuggestions). Since 2.6.0 that holds only for that relation: JoyPro itself switches an aircraft off in one relation when two relations carry the same command, so the aircraft may still be placed in the relation of its function. - Shared buttons (2.6.0): relations on the same device input with the same modifiers ("HOTAS slots") never end up
with the same aircraft on in two of them, or one press would run both (the check's "one input does two things"). The
relation the aircraft already has there stays; the new placement is left out and listed under "Kept"
(
KeptForButtonConflicts, "Left Out, Button Already Used For The Aircraft"). A conflict you kept with "keep both" is allowed. - Your action first (2.6.0): a DCS aircraft that already has an action on in one of your relations gets no second
one there (
KeptYourAction), also when the catalog calls your action something else (TDC depress on Radar Lock). - Unknown commands: commands or aircraft the local DCS database does not know yet are skipped. Refresh the DCS database to include them.
- Input layers: the catalog also covers the layers that are not aircraft:
Default, theNS430GPS, Combined Armsground_unitand the VoIP push-to-talk layers (VoiceChat,RadioVoIP). They are shared by all aircraft, so the wing and era presets never split them.
#Where the functions come from
DB/Functions holds the function catalog:
slots.json: the functions, their names and kinds.aircraft.json: wing type, era and variants.<Game>.tsv(DCS.tsv,StarCitizen.tsv,FalconBMS.tsv...): aircraft (or game), function, command, status, HOTAS position, frequency and control.- Rows and functions learned from a reworked profile come from
tools/relations/learn_catalog.py(relation exports before and after; every action switched on since becomes a row of its relation, a new relation a new function, statusnew). The 2026-11-04 rework added 151 functions (look and view buttons, autopilot modes, anti-ice, electrics, magnetos, G1000 keys ...) and rows for FSX, Prepar3D, IL-2 1946, Cliffs of Dover, Tiny Combat Arena, ACE COMBAT 7/8, Battlefield 2042/6, Project Wingman and the other games. Actions still to be tested in the game (MSFS 2024's G1000 keys in the NS430 relations, its TDC vertical and canopy) and Auto Group's ignored mods are left out. <Game>.rejected.tsv: old profile entries the manuals or game docs proved wrong. They are for guesses: a catalog substitute or a function map row on that list is not used. What you put into your own relations is your style and counts even when the list rejects it (2.6.0).
Every aircraft was checked against its own manual. The catalog is shipped with updates, so new aircraft arrive through the updater; no AI is involved at runtime.
What the catalog does not list yet (a new DCS module, a game without a <Game>.tsv such as IL-2 1946, Cliffs of Dover,
FSX / Prepar3D or Tiny Combat Arena, or an action a catalog aircraft lacks) comes from the
function map: an action whose title clearly names a function (full weight, the
function's own words) goes to the slot the catalog uses most for that function and direction, so it follows your style;
only where the aircraft has no catalog row for that slot, and one action per aircraft and slot. The preview lists
these under Function Map with the aircraft and games they brought in. --no-map groups from the catalog alone;
autoGroupIgnore in function-map.json names aircraft left to the catalog (A-4E-C, the Hercules mod).
#Free slots and your style
If an aircraft lacks a function, Auto Group can fill the slot with a substitute (on by default, off with
--no-substitutes). It picks the substitute in this order:
- Your habit. It looks at what you put on that function in other aircraft. It needs at least two separate
decisions; kneeboard placeholders do not count (your deliberate substitutes count even where
<Game>.rejected.tsvrejects the command for the function: since 2.6.0 the rejected lists only keep catalog guesses out). The preview lists these under "Learned From Your Profile". - The catalog's substitute. This is a function at the same physical position.
These rules always apply:
- Slew directions (TDC, cursor) never stand in for TMS, DMS or coolie slots. They go into "TDC Slew Up/Down/Left/Right".
- The press a slew needs goes into "TDC Depress / Designate".
- A substitute never repeats a command the aircraft already has in its own slot.
- MFD bezel buttons, keypad keys and aircraft-specific slots only take that aircraft's own commands.