Use GoFlight panels with MSFS 2020: choose a compatible bridge, install drivers, map modules, and fix missing inputs, displays and LEDs.
Yes, many GoFlight panels can be used with Microsoft Flight Simulator 2020 on PC, but they normally need a Windows driver and an MSFS-compatible interface utility; plugging them in is rarely enough. Install one integration layer, map each module, then save aircraft-specific profiles for displays and complex controls.
This is a PC solution. GoFlight modules are not supported as general-purpose panels on the Xbox version because the console cannot run the required Windows helper software.
What software do GoFlight panels need for MSFS 2020?
A GoFlight panel needs software that can read the hardware and exchange events and data with MSFS 2020 through SimConnect or a companion module. The right choice depends on the exact GoFlight model and whether you need only switches or also displays, annunciators and rotary encoders.
| Connection method | Choose it when | Main limitation |
|---|---|---|
| Direct MSFS binding | The panel appears as a normal controller and exposes usable buttons or axes | Uncommon for specialist GoFlight modules; displays and LEDs will not be driven |
| Legacy GF Config software | A supported bridge requires its GoFlight driver components, or you are checking older hardware | Legacy GF Config alone is not a dependable MSFS 2020 integration layer |
| MSFS-compatible panel bridge | You need complete input and output control | The utility must explicitly support both MSFS 2020 and your exact module |
A dedicated GoFlight Interface Tool build for MSFS 2020 or a broader panel manager such as SPAD.neXt can provide the bridge. Do not assume that every release supports every panel: check the utility's module list for identifiers such as GF-MCP, GF-166, GF-46, GF-T8 or GF-RP48 before installing it.
Many GF Config packages in circulation were written for earlier simulators. Our archived explanation of how GF Config supported older Flight Simulator generations shows why a package labelled for “Microsoft Flight Simulator” is not automatically compatible with MSFS 2020.
GoFlight and Logitech/Saitek panels use different drivers and plug-ins. If the hardware carries Logitech or Saitek branding, use our MSFS 2020 Logitech/Saitek panel installation procedure instead.
How to set up GoFlight panels in MSFS 2020
- Identify the exact module. Read the model number from the unit rather than relying on its appearance. Compatibility is module-specific, especially for MCP, radio and display panels.
- Install the required GoFlight driver. Use the driver package required by your chosen interface utility and follow its instruction about when to connect the panel. Restart Windows if requested. Do not select an FSX installation folder or copy legacy GoFlight DLL files into the MSFS
Communityfolder. - Check Windows recognition. Connect one module directly to the PC first and confirm that it appears in Device Manager without a warning symbol. For several modules, use a good powered USB hub rather than an unpowered splitter.
- Close competing panel software. Run only one programme that controls the GoFlight hardware unless its documentation specifically requires another component. Two utilities reading the same panel can produce duplicate button presses, frozen displays or failed connections.
- Start MSFS 2020 and load an aircraft. Then open the panel utility and select its MSFS 2020 or SimConnect mode. SimConnect support is part of MSFS; do not install random legacy FSX runtimes unless the utility explicitly requires one.
- Map inputs and outputs separately. Assign buttons and switches to simulator events, rotary encoders to increase/decrease events, and LEDs or displays to the corresponding simulator variables. Some utilities require an additional WASM package for custom aircraft controls; install it only when that utility's instructions call for it.
- Create an aircraft profile. Begin with a default aircraft using standard simulator events, verify every control, and then duplicate the profile for other aircraft. Save or export a backup after the panel works.
Why doesn't my GoFlight panel appear in MSFS Controls Options?
Most GoFlight panels do not present themselves as ordinary game controllers, so their absence from MSFS Controls Options is usually expected. The GoFlight driver and interface utility communicate with the hardware outside the simulator's normal keyboard, joystick and yoke binding screen.
Use two checks to locate the fault. If Windows does not recognise the module, investigate the driver, cable, port and USB power. If Windows sees it but the interface utility does not, confirm exact-model support, close GF Config and other panel managers, and reconnect the module with only the chosen bridge running.
Do not bind the same physical control in MSFS and in the bridge. A duplicate assignment commonly makes a rotary jump by two steps or causes a switch command to fire twice.
Will GoFlight panels work with every aircraft?
Basic controls usually work across aircraft when they use standard simulator events, but advanced add-on aircraft often need their own profile. Airliners may implement autopilot, electrical and radio systems through custom L: variables, H: events or other aircraft-specific data rather than the standard MSFS commands.
This distinction is most obvious with an MCP. A heading knob can successfully send the standard heading-increase event while its display remains blank because reading and displaying the selected heading is a separate output assignment. An add-on aircraft may also ignore that standard event entirely.
Maintained switches require care as well. A generic toggle command can leave the physical switch opposite to the cockpit state after loading a flight. Use explicit ON and OFF events where the aircraft exposes them, or enable the bridge's switch-synchronisation feature if it has one.
What fixes the common GoFlight panel problems?
- No power or Windows detection: try one panel directly on another USB port, reinstall the required driver and inspect Device Manager. Add a powered hub only after the single-panel test succeeds.
- Random disconnections: suspect USB power before remapping everything. Test a powered hub and, if necessary, disable USB power-saving only for the affected hub or device.
- Inputs work but displays stay blank: configure the output variables as well as the input events. Confirm that the selected aircraft exposes the data expected by the profile.
- Rotaries skip or move twice: remove duplicate MSFS assignments, close other bridge software and reduce encoder acceleration or repeat settings.
- Default aircraft works but an add-on does not: create a separate profile using that aircraft's custom events and variables. A standard Cessna profile is not proof that an airliner MCP will use the same commands.
- The bridge will not connect: load fully into a flight, select the utility's MSFS 2020 mode and reconnect. Legacy FSX or Prepar3D modes cannot be redirected by choosing the MSFS executable manually.
Once both Windows and the interface utility recognise the module, remaining faults are normally profile or aircraft-integration problems rather than failed GoFlight hardware.