One of the main issues with comparing all the user feedback in terms of performance issues and regressions is the flight conditions used. Depending on whether you’re flying low over photogrammetric cities, dense forests or 2k up in the air over plains will easily make 10…15 FPS difference. Different airplanes and weather conditions as well as lighting conditions (time of day, season) add to that. That’s why I’m doing my performance analysis using the Flight Recorder addon with a pre-recorded flight using the same aircraft, same year, same date, same time of the day, same weather.
I suggest that to be able to really compare performance between different hardware systems and settings, we should use a standardized bench flight. This way, all the small but significant variations caused by manual steering including altitude, heading, speed etc. will be avoided too. The procedure described below should not take you more than 5min to set up plus the time for the bench flight.
I’ve included a link to a test flight below. If you haven’t been using Flight Recorder yet, it’s as simple as:
- load the app
- load the bench flight
- embark on a normal flight anywhere on the planet with the conditions given below
- ALT-TAB to Flight Recorder and press Replay Flight
- ALT-TAB back to MSFS
- make sure MSFS has set the correct time of day
- start benching
Please bear in mind that if you haven’t been flying in the area, you’ll likely experience somewhat lower performance on the first flight(s) due to new scenery loading.
Here are the settings / conditions I suggest using as a standard:
- Aircraft: DA40NG
- Flight date: May 1st, 2021, 12:00 AM, the region is Central Europe.
- Flight conditions: Weather = clear sky, AI traffic = off, photogrammetry = on.
- Benching duration: 6min (can be set in CapFrameX), the recorded flight itself is longer. ! After launching the recorded flight, allow 25s before starting frame capturing to avoid initial stutters !
- Benching conditions: Cockpit view. Headset placed on table untouched, view centered. No user interaction with PC during capturing - have a coffee or beer.
I suggest capturing frames using CapFrameX. Install, launch, and after launching MSFS select “Flight Simulator” as input/source. Specify capturing duration (360s = 6min) and ALT-TAB back to MSFS. Frame capturing can then be started without switching windows using CapFrameX’s hotkey, which should be F11 by default. I suggest using Average / 1% / Min FPS for reporting.
I hope this idea will work out and I’m looking forward to your numbers .
Here’s the link, please see if it works for you: