Why ChasePlane fully replaces the default cameras

• The simulator does not hand its camera commands to add-ons. MSFS 2024 has a camera API and MSFS 2020 has none, but neither lets ChasePlane act on the default camera keys — so it brings its own.
• ChasePlane also has to block the simulator’s own camera movement. Otherwise both systems would drive the camera at once.
• ChasePlane reads your controllers itself, through its own Bridge, rather than relying on the simulator to pass input along.
• Most ChasePlane actions have no counterpart in the simulator — Cinematics, Binoculars, Tower view, and many more — and add-ons cannot add entries to its Control Settings.
• Several default camera behaviours are bugged. Starting clean does more than building on them would.

The installer offers to remove your simulator camera assignments, apart from Drone mode, so the two systems cannot fight. Accepting is optional but recommended.

Removed assignments are backed up here:

%LOCALAPPDATA%\Programs\Parallel 42\ChasePlane\V2\MSFS2024\Backup

%LOCALAPPDATA%\Programs\Parallel 42\ChasePlane\V2\Backup

Uninstalling ChasePlane from the same Manager puts them back. To be asked again after declining, uninstall and reinstall — your views, groups, and settings are untouched.

Find the Manager in the Windows Start menu, in the p42-util-chaseplane folder inside Community, or on your Downloads page.

For a mod that needs the default camera — a walkaround or pop-out manager — disable ChasePlane any of these ways:

• Click and hold the ChasePlane logo at the top of the window.
• Preferences → General Functionality → Enable/Disable ChasePlane.
• Assign a key to Enable/Disable ChasePlane in Control Assignments.

If you let the installer remove your simulator camera assignments, nothing controls the camera while ChasePlane is off. Restoring them so you can use both camera systems at once is not recommended.