Use FlightControlReplay with MSFS 2024: connect FCR, record and save a flight, replay it, change cameras, and fix connection or desync problems.
To use FlightControlReplay with Microsoft Flight Simulator 2024, install a release that explicitly supports MSFS 2024, load a flight, start FCR on the same Windows PC, confirm its SimConnect connection, then press Record. Stop and save the session; load or select it in FCR and press Play to replay it.
FlightControlReplay is an external Windows replay utility, not the simulator’s Developer Mode Replay tool, so Developer Mode is not required. Button names and positions vary between FCR releases, but the basic sequence remains Record, Stop, Save and Play.
How to record and replay a flight with FCR
The most reliable workflow is to connect after MSFS 2024 has loaded the aircraft, record from a stable state and replay without live control inputs.
- Install a compatible FCR release. Use the supplied installer and update any installation that predates explicit MSFS 2024 support. Do not treat the main Windows programme like an aircraft mod and simply drop it into the Community folder; let the installer place any companion components it requires.
- Load your flight in MSFS 2024. Wait until the aircraft, scenery and avionics have finished initialising. For a landing replay, begin recording a few minutes before the approach rather than recording an entire long-haul flight unnecessarily.
- Start FlightControlReplay. Select MSFS 2024 if your release presents a simulator choice, then check that FCR reports a connection. It communicates with the simulator through SimConnect.
- Begin from a clean state. Avoid starting while the aircraft is spawning, in slew mode or entering or leaving Active Pause. Press Record and allow a few seconds of stable data before moving.
- Fly normally. Leave FCR running while you fly. Ignore advanced ghost, AI and video-rendering options until a basic recording plays correctly.
- Stop and save the recording. Give the file a useful name containing the aircraft, airport and manoeuvre. The basic FCR recording contains replay data rather than a conventional screen video.
- Prepare for playback. Replaying during the same simulator session gives the best result. For a recording opened later, load the same aircraft variant and preferably the same livery before selecting the saved session in FCR.
- Press Play and leave the controls alone. Use FCR’s timeline and transport controls to pause, scrub or change playback speed. Avoid moving hardware axes, using slew or changing the simulator rate while FCR is controlling the aircraft.
Our broader explanation of how replay recordings are saved, played back and kept in sync covers the file-management and camera habits that apply across replay tools.
Once playback is stable, change to an external, drone or fixed camera. FCR controls the recorded aircraft path; the simulator’s camera system controls the view. For a runway-side shot, use our method for positioning a tower-style replay camera.
What does FlightControlReplay record?
FCR primarily records aircraft movement and compatible simulator variables, not a complete rewindable copy of every cockpit system.
| Element | What to expect |
|---|---|
| Position and attitude | Normally reconstructed throughout playback, including the aircraft’s latitude, longitude, altitude, pitch, bank and heading. |
| Aircraft configuration | Standard gear, flap, light and control-surface states usually replay, provided the aircraft exposes them through supported simulator variables. |
| Custom avionics | FMS pages, custom local variables, tablet settings and some add-on animations may not return to their original state. |
| Weather and traffic | These may continue as live simulator conditions rather than matching the moment of recording exactly. |
| Video and sound | The flight-data recording is not itself a video. Video rendering or capture is a separate feature whose availability and audio behaviour depend on the FCR release. |
Why will FlightControlReplay not connect to MSFS 2024?
A failed connection usually means the FCR build, launch state or Windows permissions do not match the simulator session.
- Check compatibility first. The installed FCR release must explicitly support MSFS 2024, not merely MSFS 2020. A simulator update can also require an FCR update.
- Load into an aircraft before reconnecting. Close FCR, let the flight finish loading, then reopen it and check the connection status.
- Match privilege levels. Run both applications normally. If one has been forced to run as administrator, use the same privilege level for the other or remove the unnecessary elevation.
- Repair the supplied installation. Security software can quarantine a companion component, while manually copied files can leave an incomplete installation. Repair or reinstall from the original package rather than mixing files from an older FCR release.
- Restart both programmes. A stale SimConnect session often clears only after MSFS 2024 and FCR have both been closed.
Why does an FCR replay jump or desynchronise?
Replay jumps occur when live aircraft logic, controller inputs or environmental conditions fight the recorded data.
- Aircraft state was not settled: Record only after the aircraft has fully loaded and is stationary or established in flight.
- Hardware is still sending inputs: Centre the controls and avoid touching them. Disconnect a noisy axis or use a neutral controller profile if throttle or control surfaces keep twitching.
- The autopilot or AI assistance is fighting playback: Disable AI piloting and other control assistance. If the live autopilot keeps correcting the aircraft during replay, disconnect it before trying again.
- The aircraft uses custom systems: Complex add-ons can store important states outside the standard variables FCR records. Replay in the same session and treat the result as a visual replay rather than an exact reconstruction of every switch and display.
- Weather or traffic has changed: Live turbulence, ground collisions and moving traffic can alter playback. Use consistent weather and reduce traffic if the replay repeatedly strikes another object.
- The recording interval is unsuitable: If your FCR release exposes a recording interval or sampling control, a shorter interval produces smoother motion but adds processing load. A longer interval reduces load but can make turns appear stepped.
For an exact record of an avionics procedure or cockpit failure, capture video during the original flight. Position replay is better suited to reviewing landings and producing new exterior camera angles.
Can FlightControlReplay run on Xbox or PlayStation?
The standard FlightControlReplay workflow is PC-only because FCR runs as an external Windows application and connects through SimConnect. Its Windows executable cannot be installed on Xbox Series X|S, PlayStation 5 or PS5 Pro.
Should I use FCR or MSFS 2024 Developer Mode Replay?
Choose FCR for regular saved replays and its broader playback, camera, ghost-aircraft and rendering tools; choose Developer Mode Replay for occasional basic PC replay without running a separate replay application.
| Option | Best suited to | Main limitation |
|---|---|---|
| FlightControlReplay | Saved sessions, repeated landing review, flexible playback and video-oriented work | Requires a compatible external Windows application and can still miss custom aircraft states |
| Developer Mode Replay | Basic replay using tools supplied with the PC simulator | Less convenient for routine use and requires the Developer Mode workflow |
Our comparison of replay tools for MSFS 2020 and 2024 explains where FCR fits alongside the alternatives. If you prefer the native option, follow the separate steps for enabling MSFS 2024 Developer Mode and opening its tools.