Before you start
- Use Windows 10 (version 1903 or later) or Windows 11.
- Connect and switch on your joystick, throttle, pedals or other HOTAS parts before opening the profiler. If they normally need the maker's software or drivers, install those the usual way; the profiler doesn't install drivers.
- Close calibration tools or other programs that take exclusive control of the device if the profiler can't see it. You don't need Fate of the Galaxy installed.
- Download the profiler from the HOTAS Project page and check that its SHA-256 matches. Run it as a normal user; it never needs administrator rights.
Choose your devices
The first screen, Plug in your HOTAS, lists the controllers it finds, each with its number of axes, buttons and hats. The list updates by itself when you plug something in. Everything is ticked to start; untick anything you'd rather not share. Keyboards and mice are never listed.
One HOTAS can appear as several devices (stick, throttle, pedals). Tick the parts you want to include, then press Next.
Quick share
On the next screen choose Quick share (the default, about ten seconds). It uses what Windows already knows about your devices, so there is nothing to press. You go straight to the review screen.
If a device shows no controls, try Help label the controls to check that it responds, or save the file with the warning attached.
Help label the controls
Optional, and a big help if you can spare a few minutes. Choose Help label the controls.
- The screen says Activate any control. Move one axis, press one button or push one hat at a time. Rest everything else.
- When a clear input is detected, the tool pauses and tells you what moved. Pick the best name (for example Pitch, Roll, Twist / rudder, Throttle, Trigger, Thumb hat), choose Other… to type your own, or I don't know.
- For a hat, push it in every direction before choosing its name so every direction is recorded. For an axis, move it through its full range.
- Skip this one leaves a control unlabelled. Undo last reverses your last answer. Controls you've already labelled are ignored afterwards, so you can keep going without worrying.
- Press Finish whenever you like. A partial profile is still useful; you don't need to reach 100%.
Tips: move one control at a time; don't touch the stick and throttle together; if the tool says More than one input changed, let go of everything and try again. Please don't type personal information into a name.
Switches that send several buttons for one position, and rotary selectors, can be confusing. If you're not sure, choose I don't know rather than guessing.
Review and submit
- Check the summary. Use Preview exactly what will be shared to read the complete profile.
- Tick the required consent box. Nothing is uploaded until you press Submit profile.
- Optionally tick the beta box (see below).
- Press Submit profile. You get a contribution ID. Keep it if you might want a removal later.
- If the upload fails, press Retry or Save file instead. Your result is kept.
If online sharing is not switched on in your build, only Save file instead is available.
Physical HOTAS testing beta
- Optional. Tick I'd like to apply for the physical HOTAS testing beta on the review screen and enter an email address.
- The email is only used to contact you about testing, is stored separately from your hardware profile, and is never published. Applying doesn't guarantee an invitation, and there are no promised builds or dates.
- To withdraw, email dev@manictrashpanda.dev with your contribution ID.
Saved files
When you submit, a copy of exactly what was sent is saved in Documents\Flight Control HOTAS Profiler\. Save file instead lets you choose a location. Files are named hotas-hardware-profile-v1-<id>.json, never contain your email, and can be opened in any text editor. Please don't edit them.
Troubleshooting
| Problem | What to try |
|---|---|
| HOTAS not listed | Connect it before launching; check Windows' "Set up USB game controllers"; install the maker's driver if it needs one; press Scan again. |
| Only the throttle appears | Some kits show each part as a separate device. Connect and tick the missing stick or pedals. |
| False axis movement | Release all controls, wait a moment, then move one at a time. Check for drift. |
| A toggle stays pressed | It may be a latching switch, not a momentary button. Label it as a toggle, or choose I don't know. |
| Hat not detected | Some devices expose the hat as buttons instead. It may show up as separate buttons. |
| Buttons overlap | Mode switches can reuse the same buttons. Say I don't know instead of guessing. |
| "We couldn't listen to your controllers" | Another program may be using them. Close calibration or vendor tools and try again, or share the quick profile. |
| Upload failed | Check your connection and retry, or save the file so nothing is lost. |
| Windows warning | The tool is new and unsigned. Only run it if the SHA-256 matches the one on the HOTAS Project page. |
| It captured fine but the game doesn't use my HOTAS | Expected. The profiler only collects information. Current Flight Control supports XInput gamepads. |
Privacy and limits
Sharing is opt-in at the moment you press Submit. No gameplay, account or nickname is needed. The profile contains no email, serial numbers or machine identifiers. See the full privacy notice.
A virtual testing setup can reproduce standard joystick inputs but not your device's exact identity, firmware or special features, so real-hardware testing would still be needed later. This is an experimental project with no promises.