Suggested profile names:

Suggested profile names:

10. Camera Migration

Camera migration can mean several things:

• Moving ChasePlane profiles to another PC.
• Restoring profiles after Windows reinstall.
• Moving from MSFS 2020 to MSFS 2024.
• Recreating normal MSFS custom cameras inside ChasePlane.
• Importing shared ChasePlane views.

Do not assume a profile created for one simulator or aircraft version will align perfectly in another.

Aircraft models may have:

• Different cockpit origins.
• Different seat positions.
• Different cabin models.
• Different door locations.
• Different exterior dimensions.

Recommended migration process:

1. Back up the original profile.
2. Import or copy it into the intended ChasePlane version.
3. Load the correct aircraft.
4. Check every cockpit view.
5. Check every exterior view.
6. Confirm the camera is not inside the model.
7. Resave the profile for the new simulator.
8. Keep the original backup unchanged.

11. Community Folder Components

ChasePlane may install simulator-side components, but its main user views are not stored in the Community Folder.  

Students should still check for:

• Duplicate ChasePlane packages.
• Old beta packages.
• MSFS 2020 components placed in MSFS 2024.
• Manual copies left beside installer-managed files.
• Old camera tools using their own Community Folder modules.

Do not rename ChasePlane core folders unless instructed by Parallel 42.

12. First Installation Test

Load:

• A default aircraft.
• A default airport.
• Clear Skies.
• Daylight.
• No AI traffic.
• No GSX.
• No replay system.
• No head tracking.

Confirm:

• ChasePlane opens.
• The simulator is detected.
• The camera responds.
• A new view can be created.
• The view can be saved.
• A shortcut can recall it.
• Camera movement is smooth.
• No CTD occurs.

Do not begin creating twenty views until one view has been saved and recalled successfully.

STEP 2 – CAMERA CREATION, MOTION AND AIRCRAFT PROFILES

Estimated Time: 23–25 Minutes

13. Understanding Camera Modes

ChasePlane provides three broad camera modes:

• Internal.
• External.
• World.

The MSFS 2024 product describes these as the main camera categories used for cockpit, exterior and fixed-world views.  

Internal Cameras

Used for:

• Pilot position.
• Copilot position.
• Overhead panel.
• FMC or MCDU.
• Pedestal.
• Radios.
• Circuit breakers.
• Cabin views.
• Passenger windows.

External Cameras

Used for:

• Aircraft chase views.
• Wing views.
• Nose views.
• Tail views.
• Gear views.
• Engine views.
• Cargo-door views.
• Tracking shots.

World Cameras

Used for:

• Static airport views.
• Runway-side cameras.
• Terminal cameras.
• Tower views.
• Fly-by positions.
• Scenic landscape viewpoints.

Depth of field is currently limited to World views in both MSFS 2020 and MSFS 2024.  

14. Creating the Main Pilot View

The pilot view should be the most natural and useful camera in the profile.

Position it so the student can see:

• Primary flight instruments.
• Flight Mode Annunciator.
• Autopilot panel.
• Engine indications.
• Enough outside view for taxi and landing.

Avoid:

• Sitting too far back.
• Sitting too close to the windscreen.
• Excessive zoom.
• Cutting off important instruments.
• Placing the eye position unrealistically high.

Suggested workflow:

1. Load the aircraft at the gate.
2. Move to the normal pilot eye point.
3. Set the zoom or field of view.
4. Check the runway perspective.
5. Check instrument readability.
6. Save as Pilot – Main.
7. Assign the most accessible shortcut.

15. Cockpit Detail Cameras

Create practical working views.

Recommended:

• Overhead.
• Autopilot panel.
• Left FMC or MCDU.
• Right FMC or MCDU.
• Pedestal.
• Radios.
• Engine-start panel.
• Centre console.
• Side window.
• Circuit-breaker area where simulated.

Each view should have a purpose.

Avoid creating several almost identical views.

16. Overhead-Panel Camera

Position the view so:

• The complete overhead is visible.
• Labels remain readable.
• The camera does not clip into the seat or roof.
• Mouse interaction remains comfortable.
• Head movement is limited enough for accurate switch operation.

For large aircraft, consider creating:

• Overhead upper.
• Overhead centre.
• Overhead lower.

This is often easier than using one highly zoomed-out overhead view.

17. Taxi Cameras

Taxi cameras are particularly useful in wide-body aircraft.

Possible views:

• Captain side window.
• Nose-wheel reference.
• Left wingtip.
• Right wingtip.
• Overhead exterior view.
• Main-gear reference.

Use these to:

• Judge stand clearance.
• Monitor tight turns.
• Avoid clipping scenery.
• Position the aircraft during pushback.
• Check wing clearance.

Do not use an unrealistic top-down view as the only taxi reference. It should support, not replace, correct ground handling.

18. Exterior Cameras

Exterior views should highlight the aircraft without making it difficult to control.

Recommended views:

• Rear-quarter chase.
• Front-quarter.
• Tail view.
• Wing view.
• Engine view.
• Landing-gear view.
• Belly view.
• Nose tracking view.

For each exterior view, check:

• Camera distance.
• Zoom.
• Aircraft-centering.
• Horizon alignment.
• Camera clipping.
• Behaviour during turns.
• Behaviour at high speed.

19. Passenger and Wing Views

Passenger views are excellent for immersion and content creation.

Create views for:

• Left wing.
• Right wing.
• Forward cabin.
• Rear cabin.
• Engine and wing.
• Flap observation.
• Landing-gear observation.

For realistic passenger views:

• Keep the camera inside the cabin.
• Avoid clipping through windows.
• Use mild motion effects.
• Avoid extreme wide-angle zoom.
• Position the camera at a believable seated eye height.

20. Static World Cameras

World cameras remain fixed in the environment rather than attached to the aircraft.

Use them for:

• Runway departures.
• Landing shots.
• Taxi shots.
• Terminal-side recording.
• Mountain approaches.
• Low passes.
• Airport traffic observation.

Create a static camera by:

1. Placing the camera near the intended location.
2. Pointing it toward the aircraft path.
3. Setting zoom.
4. Saving it in the World group.
5. Assigning a shortcut.
6. Testing it with the aircraft moving.

Never place a static camera where nearby scenery blocks the shot.

21. Tower Camera

ChasePlane includes a Tower Cam function capable of moving the camera to nearby tower locations. Parallel 42 states that the product includes more than 3,500 tower positions.  

Tower views are useful for:

• Watching approaches.
• Monitoring taxi.
• Capturing take-offs.
• Replays.
• Observing AI or online traffic.

Test the selected tower position because:

• Some towers may be blocked by scenery.
• Third-party airports may relocate tower structures.
• The nearest tower is not always the best camera angle.

22. Fly-By Cameras

The FlyBy function places the camera at a fixed location so the aircraft passes it.

It is useful for:

• Low passes.
• Take-offs.
• Approaches.
• Formation flying.
• High-speed aircraft.
• Cinematic recordings.

Parallel 42 describes FlyBy as a restored fixed-position camera experience similar to older flight simulators.  

Test:

• Camera distance.
• Aircraft speed.
• Zoom.
• Tracking behaviour.
• Audio.
• Frame pacing as the aircraft passes.

23. Cinematics Mode

Cinematics mode automatically presents changing camera angles.

Use it during:

• Cruise.
• Ground servicing.
• Boarding.
• Long-haul flights.
• Livestream breaks.
• Promotional videos.

The MSFS 2024 product includes automatic cinematic behaviour and GSX-aware ground sequences.  

Students should still monitor the aircraft.

Cinematics must not distract from:

• ATC instructions.
• Descent planning.
• Fuel monitoring.
• Weather changes.
• Approach preparation.

Do not rely on cinematic mode during critical flight phases.

24. Camera Transitions

Camera transition settings determine how ChasePlane moves between views.

Possible transition styles include:

• Immediate cut.
• Smooth slide.
• Fast movement.
• Slow cinematic movement.
• Delayed easing.

Use different transition speeds for different purposes.

Operational Views

Use short transitions for:

• FMC.
• Overhead.
• Radios.
• Autopilot panel.

The student must be able to access controls quickly.

Cinematic Views

Use slower transitions for:

• Wing views.
• Exterior shots.
• Passenger views.
• Ground-service sequences.

Avoid long transitions while manually flying.

25. Testing Camera Transition Quality

A good transition should:

• Move smoothly.
• Avoid passing through cockpit geometry.
• Avoid sudden zoom changes.
• Arrive accurately at the saved point.
• Maintain stable frame pacing.
• Not cause motion sickness.

If the camera moves through a seat, wall or instrument panel:

1. Shorten the transition.
2. Move the start or destination point.
3. Use an instant cut.
4. Create an intermediate view.
5. Reduce movement distance.

26. Motion Effects

ChasePlane can add camera movement responding to:

• Turbulence.
• Acceleration.
• Braking.
• Touchdown.
• Engine vibration.
• Taxi surface.
• Aircraft manoeuvres.

Motion effects should be subtle.

Too much movement can:

• Make instruments difficult to read.
• Cause motion sickness.
• Make video footage look artificial.
• Conflict with aircraft or simulator camera effects.
• Fight with FSRealistic or head tracking.

Begin with low values and increase gradually.

27. Turbulence Effects

A realistic turbulence profile should:

• Move the camera slightly.
• Respond to aircraft motion.
• Avoid constant shaking.
• Scale with turbulence severity.
• Remain controllable during approach.

Test in:

• Clear air.
• Light turbulence.
• Strong turbulence.
• Cloud layers.
• Approach.
• Taxi.

Do not judge turbulence effects while parked in calm weather.

28. Landing and Taxi Effects

Taxi effects can simulate:

• Pavement vibration.
• Runway joints.
• Braking.
• Nose-wheel movement.

Landing effects can simulate:

• Touchdown.
• Main-gear impact.
• Nose-wheel contact.
• Reverse-thrust vibration.

Keep them restrained.

A normal landing should not make the camera behave like a crash.

29. Profiles by Aircraft

Each aircraft should have its own ChasePlane profile.

Do not use one generic airliner profile for everything.

Aircraft differ in:

• Cockpit geometry.
• Seat position.
• Window shape.
• Cabin model.
• Wing location.
• Engine location.
• Aircraft length.
• Door positions.

Recommended organisation:

30. PMDG 737 Profile

Recommended PMDG views:

• Captain main.
• First Officer.
• MCP.
• Left CDU.
• Right CDU.
• Overhead.
• Pedestal.
• Engine-start panel.
• Captain side window.
• Wing view.
• Tail view.
• Gear view.

Pay attention to:

• MCP readability.
• CDU mouse access.
• Side-window taxi references.
• Shorter aircraft dimensions compared with wide-bodies.
• Different views for passenger and cargo variants where needed.

31. Fenix A319 and A320 Profiles

Recommended views:

• Captain main.
• FMA-focused main.
• FCU.
• Left MCDU.
• Right MCDU.
• Overhead.
• Pedestal.
• ECAM controls.
• Captain side window.
• Left and right wing.
• Passenger-window views.

Do not assume the A319 and A320 cabin and wing views align perfectly.

Create or adjust separate profiles.

32. iniBuilds A350 Profile

Recommended views:

• Captain main.
• Large-display overview.
• Autopilot panel.
• Left and right MFD controls.
• OIS.
• Overhead upper.
• Overhead lower.
• Pedestal.
• Side-window taxi camera.
• Wingtip clearance cameras.
• Engine view.
• Passenger view.

The A350’s size makes wingtip and taxi cameras particularly valuable.

33. iniBuilds A300 Profile

Recommended views:

• Captain main.
• Autopilot panel.
• Left and right FMS.
• Upper overhead.
• Lower overhead.
• Engineer or system panels where modelled.
• Pedestal.
• Cargo-door view.
• Main-deck freight view where available.
• Side-window taxi reference.
• Engine and wing views.

Passenger and freighter variants may require separate camera positions.

34. Controls and Shortcuts

Assign shortcuts for views used repeatedly.

Recommended priority:

1. Main cockpit.
2. Overhead.
3. FMC or MCDU.
4. Pedestal.
5. Side window.
6. Exterior chase.
7. Wing view.
8. Static or tower view.
9. Cinematics toggle.
10. Binocular or zoom function.

ChasePlane supports custom keyboard, button and joystick assignments through its own control system.  

Avoid assigning one button to:

• A ChasePlane function.
• An MSFS camera function.
• An aircraft function.

35. Controller Profiles

Create a dedicated controller profile for ChasePlane.

If an Xbox controller is used as the primary flight-control device, ChasePlane currently cannot automatically switch the same controller between aircraft control and camera control. Parallel 42 recommends using another device for camera bindings in that situation.  

36. Head Tracking and Eye Tracking

When using:

• TrackIR.
• Tobii.
• VR head movement.
• Other head-tracking tools.

test them separately before combining them with camera-motion effects.

Potential conflicts include:

• Double movement.
• Camera drift.
• Failed recentering.
• Motion effects fighting head movement.
• Incorrect view position after switching cameras.

Support differs between simulator versions and release branches, so students should review current Parallel 42 guidance before setup.  

37. Content-Creation Camera Setup

For TikTok, YouTube and livestream content, build a dedicated group.

Recommended content views:

• Cockpit wide.
• Pilot hands and controls.
• Engine-start exterior.
• Pushback rear-quarter.
• Wing during take-off.
• Gear-retraction view.
• Scenic cruise wing view.
• Approach runway-side camera.
• Touchdown side view.
• Reverse-thrust view.
• Taxi-to-gate view.
• GSX boarding view.

Label them in sequence:

38. Livestream Camera Setup

For live content, prioritise reliability.

Use:

• Fewer views.
• Fast transitions.
• Easy shortcuts.
• One cockpit recovery button.
• One exterior chase view.
• One passenger or wing view.
• One ground-service view.

Always create an emergency shortcut that instantly returns to the main cockpit view.

Do not search through camera menus while flying an approach.

STEP 3 – PERFORMANCE, STABILITY AND CONFLICT TESTING

Estimated Time: 10–12 Minutes

39. Establish a Camera Baseline

Use your permanent benchmark scenario.

Record with ChasePlane disabled:

• Startup time.
• Flight loading time.
• Average FPS.
• 1% lows.
• Frame times.
• MainThread status.
• CPU usage.
• RAM usage.
• VRAM usage.

Then repeat with ChasePlane active.

Keep constant:

• Aircraft.
• Airport.
• Weather.
• Camera position.
• Graphics settings.
• Traffic.

40. CPU Usage

ChasePlane may use CPU resources for:

• Camera calculations.
• Controller-input processing.
• Transition calculations.
• Motion effects.
• Cinematic behaviour.
• Aircraft tracking.
• World cameras.

Monitor:

• Total CPU usage.
• MainThread status.
• ChasePlane process usage.
• Bridge-process usage where visible.
• 1% lows.

A small background workload may be normal.

Investigate:

• Persistent high CPU use while stationary.
• CPU use increasing over time.
• Camera process freezing.
• Significant MainThread degradation with all motion disabled.

41. RAM Usage

Record:

• MSFS RAM.
• ChasePlane application RAM.
• Total system RAM.
• RAM after multiple aircraft-profile changes.
• RAM after a long flight.

Test:

1. ChasePlane closed.
2. ChasePlane open.
3. One aircraft profile loaded.
4. Many views loaded.
5. Cinematics active.
6. Long flight completed.

Look for unusual continuous growth rather than one small increase.

42. Frame Pacing During Transitions

Average FPS may remain unchanged while transitions create visible frame-time spikes.

Test transitions between:

• Cockpit and overhead.
• Cockpit and exterior.
• Exterior and static camera.
• World and cockpit.
• Passenger and cockpit.
• Cinematic sequences.

Record:

• Average FPS.
• 1% lows.
• Frame-time graph.
• MainThread.
• GPU utilisation.

If spikes occur only during large exterior transitions, the simulator may be loading new scenery, geometry or textures as the camera position changes.

43. Camera-Stutter Testing

Camera stutter may appear as:

• Uneven panning.
• Small jumps.
• Delayed input.
• Stuttering transitions.
• Irregular zoom.
• Camera snapping.

Possible causes include:

• Controller polling conflicts.
• Duplicate camera bindings.
• MainThread pressure.
• Premium airport scenery.
• VRAM saturation.
• Head-tracking conflict.
• Excessive motion effects.
• Replay-tool conflict.
• Low wireless-controller stability.

Test first at a default airport with a default aircraft.

44. Cockpit Panning Test

At the gate:

1. Face forward.
2. Pan slowly left.
3. Pan slowly right.
4. Look up at the overhead.
5. Look down at the pedestal.
6. Repeat with motion effects off.
7. Repeat with head tracking off.
8. Record frame times.

If panning stutters without ChasePlane, the cause is unlikely to be ChasePlane alone.

45. Exterior Rotation Test

Rotate around the aircraft slowly.

Monitor:

• Texture loading.
• VRAM.
• GPU utilisation.
• Frame pacing.
• Airport-object loading.
• Livery performance.

If stutters occur when a detailed terminal enters view, scenery or VRAM may be the main cause.

46. Conflict With Default Camera Controls

Because ChasePlane overrides the default camera system, duplicate controls are one of the most common causes of bad behaviour.  

Symptoms include:

• View moving twice.
• Camera drifting.
• Shortcut opening the wrong view.
• Zoom jumping.
• Controls not responding.
• Camera snapping back.

Diagnostic process:

1. Create a clean MSFS control profile.
2. Remove normal camera bindings.
3. Keep only required Drone controls.
4. Configure controls inside ChasePlane.
5. Retest.
6. Reintroduce special bindings individually.

47. Conflict With Other Camera Tools

Do not initially combine ChasePlane with:

• Another camera manager.
• Head tracking.
• Replay-camera systems.
• FSRealistic camera motion.
• Aircraft camera shake.
• Controller camera software.

Test ChasePlane alone first.

ChasePlane cannot move cameras while the default MSFS replay system or an add-on relying on that system has camera variables locked. Parallel 42 recommends using replay alternatives that do not impose the same limitation when ChasePlane camera movement is required.  

48. FSRealistic Conflict Test

Both ChasePlane and FSRealistic may add:

• Taxi vibration.
• Turbulence.
• Braking effects.
• Touchdown movement.
• Engine vibration.

Running strong effects in both can create:

• Excessive shaking.
• Irregular camera motion.
• Motion sickness.
• Unstable content footage.

Test:

1. ChasePlane motion only.
2. FSRealistic motion only.
3. Both at low intensity.
4. Compare frame pacing and visual quality.

Choose one application as the main camera-motion provider.

49. Controller Conflict Testing

If a camera moves by itself:

1. Disconnect unused controllers.
2. Check for stick drift.
3. Remove duplicate axes.
4. Check Xbox controller mappings.
5. Check Steam Input.
6. Check joystick software.
7. Increase dead zone slightly where needed.
8. Reconnect devices individually.

Do not immediately reinstall ChasePlane when the real cause may be controller drift.

50. Loading-Time Impact

Measure:

ChasePlane Disabled

• Simulator launch to main menu.
• Main menu to cockpit-ready.

ChasePlane Enabled

• Simulator launch to main menu.
• Main menu to cockpit-ready.
• Time for ChasePlane connection.
• Time for aircraft profile to load.

Compare

A small delay may be reasonable.

A major delay may indicate:

• Corrupted profile.
• Old installation files.
• Cloud synchronisation issue.
• Security-software interference.
• Incorrect simulator version.
• Conflict with another utility.

51. Aircraft Profile Stability

Test each major profile.

For each aircraft:

1. Load the profile.
2. Recall every cockpit view.
3. Recall every exterior view.
4. Test transitions.
5. Test motion effects.
6. Change livery.
7. Reload the flight.
8. Restart MSFS.
9. Confirm the profile remains linked.
10. Confirm camera positions have not shifted.

Aircraft updates can sometimes alter model geometry or viewpoint references.

After an aircraft update, recheck:

• Seat position.
• Wing views.
• Engine views.
• Cabin views.
• Door views.
• Static views.

52. Long-Flight Stability

During a longer flight, test:

• View switching.
• Cinematics.
• Motion effects.
• CPU usage.
• RAM usage.
• Controller input.
• Profile saving.
• Return to cockpit.

Record any problems at:

• Departure.
• Climb.
• Cruise.
• Descent.
• Arrival.
• Landing.

Cinematic mode should not prevent a quick return to the cockpit.

53. Cloud Backup and Restore Test

Where cloud backups are enabled:

1. Create a test view.
2. Save it.
3. Confirm synchronisation.
4. Export or back up the profile manually.
5. Delete or duplicate the test view.
6. Restore the backup.
7. Confirm the original view returns.

Never test restore procedures for the first time after losing an entire profile library.

54. Clean Troubleshooting Profile

If ChasePlane becomes unstable:

1. Back up current data.
2. Create a new blank aircraft profile.
3. Disable motion effects.
4. Disable Cinematics.
5. Disable head tracking.
6. Use one keyboard shortcut.
7. Test at a default airport.
8. Add functions gradually.

If the blank profile works, the original profile may be damaged or overly complex.

55. Common Problems

ChasePlane Does Not Detect MSFS

Check:

• Correct ChasePlane edition.
• Simulator fully loaded.
• ChasePlane updated.
• Firewall permission.
• Bridge application running.
• Correct simulator version selected.
• Experimental MSFS 2024 limitations.

Default Camera Controls No Longer Work

This is expected while ChasePlane is active because it overrides the simulator camera system. Configure camera controls inside ChasePlane.  

Camera Moves Twice

Check for:

• MSFS camera bindings.
• ChasePlane bindings.
• Head tracking.
• Another camera tool.
• Controller software.

Camera Drifts

Check:

• Controller stick drift.
• Axis dead zone.
• Head tracking.
• Xbox controller mapping.
• Wireless-controller connection.

Profile Loads in the Wrong Position

Check:

• Correct aircraft variant.
• Aircraft update.
• Different simulator edition.
• Different cockpit model.
• Imported community profile.
• Camera migration.

Camera Clips Through the Cockpit

Shorten transitions or reposition the view.

MSFS 2024 can also show copilot-model clipping when the camera moves too close to the copilot avatar, which Parallel 42 currently lists as a simulator-side limitation.  

ChasePlane Does Not Work During Replay

The default replay system locks camera variables, preventing ChasePlane from moving the camera during playback.  

Frame Pacing Is Poor

Test:

• Motion effects off.
• Cinematics off.
• Default airport.
• Default livery.
• Head tracking off.
• Other camera tools disabled.
• Lower scenery load.
• VRAM usage.

Profile Disappears After Reinstall

Check the separate ChasePlane user-data and cloud-backup locations. User views are not normally stored in the Community Folder.  

Student Practical Assignment

Build and Test a ChasePlane Aircraft Profile

Choose one aircraft:

• PMDG 737.
• Fenix A319 or A320.
• iniBuilds A300.
• iniBuilds A350.
• FlyByWire A380X.

Part 1 – Installation

Simulator: MSFS 2020 / MSFS 2024

ChasePlane edition:

Version:

Account linked: Yes / No

Cloud backup enabled: Yes / No

Control-assignment backup created: Yes / No

Part 2 – Aircraft Profile

Create:

☐ Main pilot view.

☐ Overhead view.

☐ FMC or MCDU view.

☐ Pedestal view.

☐ Side-window taxi view.

☐ Exterior chase view.

☐ Wing view.

☐ Engine or gear view.

☐ Passenger view.

☐ Static runway camera.

☐ Tower or fly-by view.

Part 3 – Motion and Controls

Record:

Motion effects enabled: Yes / No

Turbulence intensity:

Taxi intensity:

Landing intensity:

Main-view shortcut:

Overhead shortcut:

Exterior shortcut:

Cinematics shortcut:

Controller used:

Part 4 – Content-Creation Group

Create at least five views:

1. Cockpit introduction.
2. Pushback.
3. Engine start.
4. Take-off.
5. Landing.

Confirm every view can be recalled without opening the main application window.

Part 5 – Performance Test

Part 6 – Conflict Test

Confirm:

☐ Default camera bindings reviewed.

☐ Duplicate controls removed.

☐ Head tracking tested separately.

☐ FSRealistic motion tested separately.

☐ Replay limitations understood.

☐ Controller drift ruled out.

☐ Profile backup restored successfully.

Student Checklist

Correct simulator edition selected.

Parallel 42 account configured.

ChasePlane installed and activated.

Current update installed.

Default control assignments backed up.

ChasePlane camera bindings created.

Community Folder checked for duplicates.

Profile data backed up.

Main cockpit view created.

Cockpit detail views created.

Exterior views created.

Passenger views created.

Static view created.

Tower or fly-by camera tested.

Cinematics tested.

Transitions configured.

Motion effects adjusted.

Aircraft-specific profile created.

Content-creation group created.

PMDG, Fenix or iniBuilds profile tested.

CPU and RAM recorded.

Frame pacing measured.

Camera stutters investigated.

Controller conflicts checked.

Loading-time impact measured.

Profile stability confirmed after restart.

Lesson Summary

You have now installed, configured, tested and backed up ChasePlane for Microsoft Flight Simulator 2020 or Microsoft Flight Simulator 2024.

Remember:

• Use the correct ChasePlane edition for your simulator.
• The current MSFS 2024 edition is labelled Experimental, so check the latest limitations before use.  
• ChasePlane completely overrides the default camera system while active.
• Camera controls should be assigned inside ChasePlane.
• Duplicate MSFS and ChasePlane camera bindings can create conflicts.
• Views and settings are stored separately from the Community Folder.
• Back up profiles before aircraft updates, simulator changes or reinstallations.
• Create separate profiles for each aircraft and variant.
• Use operationally quick transitions inside the cockpit.
• Use slower transitions for cinematic exterior footage.
• Keep turbulence and landing motion subtle.
• Avoid stacking strong motion effects from ChasePlane and FSRealistic.
• Test camera performance at a default airport before blaming ChasePlane.
• Frame pacing is more important than average FPS during camera transitions.
• Always keep a shortcut that instantly returns to the main pilot view.
• Verify profile stability after restarting the simulator.

Knowledge Check

1. What is ChasePlane designed to replace?
2. Why may default MSFS camera controls stop working?
3. Which camera assignments should generally be removed from MSFS?
4. Why should Drone controls sometimes remain available?
5. Where are ChasePlane views stored relative to the Community Folder?
6. Why should profiles be backed up separately?
7. What is the difference between Internal, External and World cameras?
8. Why are taxi-reference views useful for wide-body aircraft?
9. What is Tower Cam used for?
10. What is a FlyBy camera?
11. Why should operational cockpit transitions be short?
12. Why should motion effects remain subtle?
13. Why should each aircraft have a separate profile?
14. What views would be useful for a PMDG 737 profile?
15. What additional views benefit an iniBuilds A350?
16. Why can an Xbox controller cause assignment problems?
17. What causes the camera to move twice?
18. Why may ChasePlane not move the camera during default replays?
19. How should FSRealistic and ChasePlane motion effects be compared?
20. What evidence confirms that a ChasePlane profile is stable and ready for regular use?