How do I set up ChasePlane camera views in MSFS 2024?

To set up ChasePlane camera views in Microsoft Flight Simulator 2024, install and open ChasePlane on the PC, load a flight, let it recognise the aircraft, create and position a viewpoint, save it to that aircraft’s preset, then bind unique keys or controller buttons to recall the view.

ChasePlane is a Windows desktop utility, so this setup applies to the PC edition of MSFS 2024. It cannot be installed as an external app on Xbox Series X|S or PlayStation 5. Our summary of ChasePlane’s viewpoints and filming features explains what the wider camera toolset provides.

How do I create and save a ChasePlane view?

The reliable method is to establish the simulator connection first, create a neutral pilot view, and only then add specialist cameras and shortcuts.

1. Install the MSFS 2024 integration: Close the simulator and run the installer or update tool supplied with your ChasePlane licence. Select Microsoft Flight Simulator 2024 if separate simulator targets are offered, and let the installer place any required companion components automatically. Do not reuse files from an older FSX, Prepar3D or MSFS 2020 installation.
2. Run both programs at the same privilege level: Standard Windows privileges are preferable. Running ChasePlane as administrator while MSFS is running normally, or the reverse, can prevent communication between them.
3. Load an aircraft completely: Open ChasePlane and start an actual flight in MSFS 2024. The simulator’s main menu does not provide the loaded-aircraft identity ChasePlane needs for selecting the correct preset.
4. Create a baseline pilot viewpoint: Enter the cockpit, create a new viewpoint in the detected aircraft’s preset and give it a functional name such as Pilot eye. This becomes a recovery position if an experimental camera ends up outside the cockpit.
5. Position the camera: Use ChasePlane’s translation controls to move left, right, up, down, forwards or backwards, then adjust pitch, yaw and roll. Set zoom or field of view last; using an extreme wide angle to compensate for poor positioning distorts the panel and can expose gaps in the cockpit model.
6. Save the viewpoint: Commit it to the named aircraft preset and confirm that it appears in the preset list. ChasePlane builds may save some changes automatically, but the view should remain listed after switching to another camera and back.
7. Assign a recall control: Bind a unique keyboard combination, joystick button or controller button to the view. Avoid keys already assigned to MSFS Cockpit Quickviews, Freelook or Reset Cockpit View. Check the active control profile for every connected device, because a gamepad can hold a conflicting camera command even when the keyboard profile is clear.
8. Test persistence: Recall another view, return to the new one and then reload the flight. If it does not return correctly, verify the selected aircraft preset before creating the view again.

Which ChasePlane views and modes should I use?

Use saved viewpoints for repeatable cockpit and exterior positions, and reserve the dynamic modes for observation, screenshots or video capture.

A useful first preset contains the normal pilot position, a closer instrument scan, overhead and pedestal views, left and right exterior views, and one rear external angle. Keep the names descriptive rather than building a long list of entries called View 1, View 2 and so on.

The MSFS Drone or Showcase camera remains a separate system. Use our guide to controlling the native MSFS drone camera when you need unrestricted movement around scenery rather than an aircraft-based ChasePlane view.

Why is ChasePlane not connecting or retaining my views?

Connection failures usually come from a missing MSFS 2024 component, mismatched Windows privileges, Safe Mode or competing camera bindings.

• No simulator or aircraft detected: Finish loading into a flight, confirm that the MSFS 2024 integration was installed, and keep ChasePlane and MSFS at the same privilege level. MSFS Safe Mode disables third-party packages, so ChasePlane’s in-sim component may not load there.
• The camera moves and immediately snaps back: ChasePlane and the native camera system are probably responding to the same input. Remove only the duplicate Freelook, Quickview or reset command from the active MSFS device profile.
• Mouse movement does nothing: First click back into the simulator and verify that mouse-look has not been unbound or captured by another window. Our cockpit mouse-pan troubleshooting steps cover the native focus and binding faults that can also interfere with ChasePlane.
• A preset appears to be missing: Check which aircraft profile ChasePlane selected. Different variants of the same aircraft can report separate identities, so the view may be stored under another variant rather than deleted.
• A saved camera has shifted: An aircraft update may have changed the cockpit geometry or reference position. Edit and resave the affected viewpoint instead of compensating with excessive zoom.
• Nothing connects after an update: Remove or disable duplicate, outdated ChasePlane components and rerun its installer. Keeping two generations of the connector active can be as disruptive as having none.

Can ChasePlane and native MSFS views work together?

ChasePlane and native MSFS custom views can coexist, but they should not share the same movement or recall bindings.

Use ChasePlane when you want aircraft-specific preset management, exterior viewpoints, Smart Views, Cinematics Mode or FlyBy Mode. If you only need several fixed cockpit positions without running a companion app, the built-in MSFS custom-view workflow is simpler.

We recommend retaining one native pilot view as a fallback and assigning ChasePlane commands to a separate group of keys or buttons. That gives you a dependable way back to the seat if ChasePlane is closed, disconnected or using the wrong aircraft preset.