This article covers the following platforms
MSFS 2024
MSFS 2020
ATS
FSX
Prepar3D
ChasePlane assignments and Microsoft Flight Simulator control bindings are separate. A button can be assigned correctly in ChasePlane and still do something unexpected if the simulator binds the same input to a camera command.
What is happening?
ChasePlane cannot capture or run an assignment from a device it has not detected.
- Load a flight and open ChasePlane from the simulator toolbar.
- Open Preferences → Control Assignments.
- Look under Connected Devices for the controller you intend to use.
- If it is missing, close the simulator, connect the controller, and start the same simulator again.
- Recheck Connected Devices.
ChasePlane detects controllers when it starts and watches for device changes while it runs.
- In Preferences → Control Assignments, select the ChasePlane action you want to configure.
- In Assign Control, find Listening to and make sure your controller is selected.
- Press the key or button, or move the axis, that you want ChasePlane to capture.
- For an axis, complete each direction shown and select Confirm. For a key or button, select Save Assignment.
- Confirm the input appears under Saved Assignments before closing the editor.
The editor does not listen to the mouse by default. To capture a mouse button, select Mouse under Listening to.
A yellow marker beside an input means the shortcut is already used elsewhere in ChasePlane. Select it to open Already Assigned, which finds duplicates across Control Assignments, individual view shortcuts, View Name Shortcuts, and camera-group shortcuts.
Remove the unintended assignment from the location shown, then test again. Adding a duplicate does not remove the earlier mapping.
If ChasePlane reports no duplicate, the simulator is competing for the input:
- Open Preferences → Control Assignments → Cheat Sheet to see every ChasePlane assignment for the current aircraft.
- Compare the input with Controls Options in Microsoft Flight Simulator.
- Remove the matching simulator camera binding, so ChasePlane is the only camera system responding.
- Leave unrelated aircraft and flight-control bindings alone.
Use the ChasePlane Manager for MSFS 2024. On first installation it asks whether to remove simulator camera assignments from default, current, and future custom control profiles. If you accepted, it backs up the affected profile data and restores it when ChasePlane is uninstalled.
Use the ChasePlane Manager for MSFS 2020. Its first-install prompt offers the same automatic cleanup and restores the backed-up simulator bindings when ChasePlane is uninstalled.
A shortcut assigned in a view’s editor applies only to that view, in that aircraft.
If the shortcut works after changing aircraft but not with the original one, inspect that aircraft’s view shortcut rather than resetting all controls. Preferences → Control Assignments → Cheat Sheet lists the current aircraft’s view shortcuts alongside your global assignments.
Open the affected action in Control Assignments and use its trash button to remove one saved assignment before capturing it again. That is the narrowest reset and preserves the rest of your setup.
If many standard assignments are missing or incorrect, Reset Default restores the default Control Assignments. Clear All removes them instead of restoring defaults. ChasePlane warns first because neither can be undone.
Still not responding?
Restart the simulator, reproduce the problem once, then contact Parallel 42 Support with:
- the simulator version and Microsoft Store or Steam edition;
- the controller’s exact name as shown by Windows;
- a screenshot of Connected Devices;
- a screenshot of the saved assignment and any Already Assigned result;
- whether the input appears in the Cheat Sheet; and
- the ChasePlane logs from that fresh attempt.