How do I set ChasePlane physics and turbulence in MSFS?

Configure ChasePlane camera physics only after its views and bindings work, then tune acceleration, rotation and turbulence separately in small steps. Microsoft Flight Simulator’s turbulence setting changes the aircraft’s atmospheric response; ChasePlane changes how the camera reacts. Avoid running strong native camera shake and another motion add-on at the same time.

This procedure applies to ChasePlane running alongside Microsoft Flight Simulator 2020 or 2024 on PC. ChasePlane is an external PC application and cannot be installed on Xbox or PlayStation consoles.

What do ChasePlane physics and MSFS turbulence control?

Microsoft Flight Simulator and ChasePlane act at different layers, so their turbulence controls are not interchangeable.

• MSFS turbulence changes how atmospheric conditions disturb the aircraft. It can affect attitude, altitude, control inputs and autopilot workload.
• ChasePlane physics controls camera displacement, lag and vibration as the aeroplane accelerates or rotates. It does not change the weather or flight model.
• Other camera effects, including MSFS camera shake and head-motion add-ons, can stack with ChasePlane and make the result look unnaturally violent.

MSFS 2020 offers Low, Medium and Realistic turbulence assistance choices. Our explanation of the MSFS 2020 turbulence levels and their menu location covers that simulator-side control. Menu organisation may differ in MSFS 2024, but the principle remains the same: decide how strongly the aircraft should encounter turbulence before tuning camera movement.

How do I configure ChasePlane physics step by step?

The reliable method is to isolate each type of movement and change one control at a time.

1. Confirm the basic setup. Make sure ChasePlane detects the running simulator, changes views correctly and has no binding conflicts. If it does not, complete the ChasePlane installation, connection and view-binding process before touching physics.
2. Choose one aircraft and cockpit view. Physics that suits a light single will usually feel excessive in an airliner. Start with the normal pilot view rather than an instrument close-up or external camera.
3. Create a repeatable baseline. Use preset weather with little wind and no gusts instead of Live Weather. Keep the aircraft, loading, field of view and test flight unchanged while adjusting the profile.
4. Remove competing movement. Disable or minimise camera shake, head movement and turbulence effects from other add-ons. Leave only the simulator’s physical aircraft response and ChasePlane’s camera physics active.
5. Open the view’s physics controls. Enter ChasePlane’s view editor and open the section labelled Physics or Motion in your build. Control names and grouping can change between ChasePlane releases, so identify them by function rather than relying on one exact panel layout.
6. Tune linear acceleration first. Test braking, take-off acceleration and a coordinated turn. Increase translation or acceleration response until movement becomes noticeable, then reduce it slightly. The viewpoint should suggest weight without sliding through the seat or panel.
7. Add rotational response. Adjust pitch, roll and yaw movement separately where those controls are exposed. Excessive rotational lag makes the horizon slosh after control inputs and can make an otherwise stable aeroplane appear unstable.
8. Add camera turbulence last. Keep the MSFS turbulence level fixed and raise only ChasePlane’s turbulence response in small increments. Test again in repeatable wind or gust conditions; do not tune it during unpredictable Live Weather.
9. Save and verify the profile. Reload the view or restart the test session to confirm the settings were stored in the intended aircraft profile. Check instrument close-ups and external views separately rather than assuming one strength suits every camera.

Which turbulence settings should I use?

Choose the simulator setting for flight-model behaviour and ChasePlane settings for visual movement and comfort.

There is no useful universal percentage. Aircraft size, camera field of view and viewing distance all alter the apparent strength. A zoomed instrument view often needs almost no physics even when the main pilot view uses noticeable movement.

Why does ChasePlane shake too much?

Excessive ChasePlane shaking usually comes from stacked effects or from tuning against changing weather.

• Constant shaking in calm air: another head-motion or camera-shake layer is probably active, or ChasePlane’s procedural turbulence is set too high.
• Violent movement only in rough weather: the aircraft is already moving under MSFS turbulence and ChasePlane is adding too much relative camera motion. Reduce ChasePlane first if you want to preserve realistic flight-model forces.
• The camera continues moving after a turn: lower acceleration or rotational inertia, or increase damping if that control is available.
• The viewpoint passes through the seat or panel: reduce translational displacement and check the view’s starting position and field of view.
• The instruments show real altitude or pitch oscillation: this is not merely camera physics. Check trim, duplicate control bindings and autopilot behaviour using our guide to diagnosing autopilot altitude oscillation.

Should ChasePlane and another motion add-on run together?

Use one add-on as the primary source of cockpit movement and disable overlapping effects in the other.

ChasePlane is the better fit when view creation, transitions and view-specific camera behaviour are the priority. A dedicated effects package may focus more heavily on cockpit vibration, turbulence cues and sounds. Our comparison of MSFS camera and motion add-ons explains those roles. If two products remain active, assign turbulence and head movement to only one of them.