Fix Logitech/Saitek Multi and Radio Panels not detected in FSX by checking USB power, panel software, SimConnect, trust prompts and aircraft power.
FSX does not detect Logitech/Saitek Multi and Radio Panels as ordinary game controllers. They require the correct Flight Panels software and its FSX plug-in, a working USB connection, and SimConnect. If Windows sees them but FSX does not, repair the plug-in; if Windows cannot see them, fix USB power or the driver first.
Should the panels appear in FSX's controller list?
No. The Multi Panel and Radio Panel usually do not appear as assignable joysticks under FSX's control settings. They are driven by external panel software through SimConnect and the panel output system, so their absence from the controller list is normally expected.
Installing only the yoke driver is not enough. The panels need their own software package and FSX support component; our complete FSX panel installation sequence covers the initial setup and connection order.
How can I tell which part is failing?
The point at which detection stops identifies the likely fault.
| Symptom | Likely cause | What to check |
|---|---|---|
| No change in Device Manager when connected | USB port, power, cable or device driver | Test a direct motherboard port, another computer and a powered hub |
| Windows detects both panels, but FSX does nothing | FSX plug-in, startup entry or SimConnect | Repair the panel software and check that its FSX component starts |
| Buttons work, but the displays remain blank | Aircraft electrical power or the output component | Test a powered default aircraft, then repair the panel output software |
| Panels disconnect when both are attached | Insufficient USB power or power management | Use a powered hub and disable power saving on the relevant USB hubs |
| Panels work with default aircraft only | Add-on aircraft uses custom systems | Use aircraft-specific integration or compatible panel middleware |
How do I fix Multi and Radio Panel detection in FSX?
- Confirm Windows detection. Close FSX, open Device Manager and connect one panel at a time. A new USB or human-interface device should appear. A dark panel display is not proof of failure because the display may remain off until the FSX plug-in and aircraft are running.
- Rule out USB power problems. Connect each panel directly to a rear motherboard port before testing hubs, front-panel sockets or the USB ports built into a yoke. If they work separately but fail together, use a separately powered USB hub. In Device Manager, also disable “Allow the computer to turn off this device to save power” for the affected USB hub where that option is available.
- Install the panel package, not just the controller driver. Remove obsolete or duplicate Saitek and Logitech panel packages, restart Windows, then install the package intended for Flight Panels and FSX. Select the installer matching the architecture of Windows; do not choose a 32-bit Windows package merely because FSX itself is 32-bit. Leave FSX closed during installation and connect the hardware when the installer requests it.
- Approve the FSX security prompt. Start FSX after installation and allow the panel support component to run. If it was previously rejected, back up
FSX.cfgand remove only the trust entry belonging to the panel software, or reinstall the FSX plug-in so the prompt is presented again. Do not erase the entire trusted-software section. - Check that the panel application starts with FSX. Panel packages normally register a startup entry in
exe.xml, and some versions may also usedll.xml. These files are held in the FSX profile under%APPDATA%\Microsoft\FSX; Steam Edition may instead use anFSX-SEprofile when boxed FSX is also installed. A disabled entry, obsolete installation path or malformed XML file can stop the plug-in. Back up the XML files, then repair or reinstall the panel package rather than pasting an unverified entry from another computer. - Repair SimConnect. If Windows recognises the panels but the software cannot communicate with FSX, repair the legacy SimConnect runtime required by the panel package. FSX: Steam Edition can keep several SimConnect runtimes side by side, so do not copy random DLL files into the simulator folder. Our explanation of FSX and Steam Edition SimConnect runtimes shows how to identify and repair this layer safely.
- Remove software conflicts. Run FSX and the panel application at the same Windows privilege level, and close other utilities that may be trying to control the same hardware. Two panel applications cannot reliably own the Radio or Multi Panel simultaneously.
- Test with a default powered aircraft. Load the default Baron 58, switch on the battery, alternators and avionics, then change a radio frequency and an autopilot selection in the virtual cockpit. This separates basic hardware detection from add-on-aircraft compatibility.
What changes with FSX: Steam Edition?
The hardware works with both boxed FSX and FSX: Steam Edition, but older installers may register their plug-in against the wrong simulator. Run Steam Edition once to create its profile, close it, and then repair or reinstall the panel software.
If boxed and Steam editions coexist, check which profile and simulator path the installer selected. Steam Edition's profile name can vary depending on whether boxed FSX was already present. The same path and registry differences also affect other legacy software, as explained in our FSX: Steam Edition compatibility checks.
Why are the panel displays dark even though Windows detects them?
A dark display often means that the FSX connection or aircraft electrical system is off, not that the panel is undetected. The Radio Panel normally needs an active plug-in plus aircraft battery and avionics power; the Multi Panel also needs the panel service to be communicating with FSX.
If the controls operate the virtual cockpit but no digits appear, reconnect the panel, repair the panel output component and close competing hardware utilities. For faults isolated to that unit, follow our Radio Panel display and driver diagnosis.
When both panels work with a default aircraft but not a complex add-on, the installation is functioning. That aircraft probably uses custom variables for its radios or autopilot, which the standard Logitech/Saitek plug-in cannot interpret without aircraft-specific integration.
What if only one panel is detected?
If one panel works, SimConnect and the main FSX plug-in are probably running, so concentrate on the failing panel's USB connection, power and individual driver. Move only the failing unit between ports: if the fault follows the port, suspect power or the port; if it follows the panel on every computer, suspect its driver or hardware.
There is rarely any reason to reinstall FSX for a single missing panel. Reinstall the affected panel software first, preserving the simulator and its add-ons.