I use a regular laptop with a Ryzen 7 processor, 16GB of RAM, and integrated Radeon graphics. It isn’t a dedicated gaming laptop, but I have been able to run X-Plane 11 and enjoy regular flights when performance remains within a reasonable range.
If you’re getting started with flight simulation on similar hardware, you can also read my Beginner Guide to Flight Simulation on a Low-End or Mid-Range PC.
For me, there is a difference between a flight simulator being playable and feeling comfortable. Around the low 20s, I can still fly and control the aircraft, although the experience isn’t as smooth. Once the frame rate reaches the upper 20s and into the 30s, flying generally feels smoother and more comfortable to me.
To see how this changes during an actual flight, I flew a Boeing 737-800 from Toronto Pearson (CYYZ) to Ottawa (CYOW). The flight took place during the evening, and I arrived in Ottawa around sunset. Instead of changing settings throughout the flight, I watched how the FPS changed during different stages of the route.
Phase One: Gate & Taxi
Toronto Pearson was the starting point for my flight to Ottawa. While sitting at the gate and taxiing in the Boeing 737-800, my frame rate was around 17–21 FPS.
At this stage, the frame rate was lower than what I experienced later in the flight. When it stayed around 20 FPS or slightly above, I still found the simulator playable, although it wasn’t as smooth as the higher frame rates I experienced during other parts of the flight.
For this test, I wasn’t trying to adjust individual graphics settings to increase the frame rate. Instead, I wanted to observe how performance changed naturally during a normal flight from Toronto to Ottawa. This gave me a starting point that I could compare with takeoff, the flight toward Ottawa, and the approach and landing.
If you’re looking for ways to improve performance instead, I tested several settings tweaks to boost flight simulator performance on budget hardware in a separate article.
Phase Two: Takeoff & Departure
During takeoff from Toronto Pearson, my frame rate was generally in the 20s, although it briefly dropped lower at times. Despite these short drops, I was able to complete the takeoff normally and continue the flight toward Ottawa.
As I climbed away from Toronto, the performance gradually improved. This was one of the interesting things I noticed during the flight because the frame rate I experienced around Pearson didn’t represent the performance I would get throughout the entire trip.
I kept the same setup during the flight rather than changing graphics settings to improve performance. My goal was to observe how the frame rate changed naturally from takeoff through the rest of the flight.
Once I was farther into the flight, the frame rate eventually reached the late 20s and early 30s, which felt smoother and more comfortable to me than the lower frame rates I experienced around Toronto.
Phase Three: Cruising Through the Skies
Once I was in flight toward Ottawa, the frame rate improved compared with what I experienced around Toronto Pearson. During this part of the flight, I was generally getting FPS in the late 20s to early 30s.
For me, this was the most comfortable part of the flight. The simulator felt smoother than it did when the frame rate was around the low 20s, and I was able to enjoy the flight without focusing as much on the FPS counter.
What I found interesting was how much the frame rate changed during the same flight. I didn’t change my graphics settings between the different phases. Instead, I kept flying normally and observed how the performance changed as I travelled from Toronto toward Ottawa.
This helped demonstrate the difference between what I consider playable and comfortable performance. I could still fly at the lower frame rates I experienced earlier, but the late 20s and early 30s provided a noticeably smoother experience.
Concluding Phases: Approach, Landing, and Taxing at Ottawa
As I approached Ottawa around sunset, the frame rate dropped from the higher levels I experienced earlier in the flight. During the approach and touchdown, I was getting around 20–23 FPS.
Even though the frame rate was lower than during the main part of the flight, I was still able to complete the approach and landing. For me, this was within the playable range, although it wasn’t as smooth as the late 20s and early 30s I experienced earlier.
After landing, I noticed another change in performance. While taxiing and parking at Ottawa, my frame rate increased to around 27–28 FPS. This felt smoother and was back within what I would consider a comfortable range.
The Toronto-to-Ottawa flight showed me that FPS can change considerably during different stages of the same flight. I experienced around 17–21 FPS at Toronto Pearson, generally in the 20s during takeoff, late 20s to early 30s while in flight, 20–23 FPS during the Ottawa approach and touchdown, and 27–28 FPS while taxiing and parking in Ottawa.
Rather than expecting one FPS number throughout an entire flight, I found it more useful to consider how the simulator actually felt at each stage. Lower frame rates were still playable for me at times, while the upper 20s and low 30s provided a more comfortable experience.
Frequently Asked Questions
What FPS do I consider playable in X-Plane 11?
For me, FPS around the low 20s can still be playable. The experience may not feel as smooth as it does at higher frame rates, but I can still control the aircraft and continue the flight. This is based on my own experience and shouldn’t be treated as a requirement for everyone.
What FPS feels comfortable to me in a flight simulator?
I generally find the upper 20s and low 30s more comfortable. During my Toronto-to-Ottawa flight, the late 20s and early 30s I experienced while in flight felt noticeably smoother than the lower frame rates around the airports.
Does FPS stay the same throughout an entire flight?
Not in my experience. During this flight, my FPS changed several times between Toronto Pearson and Ottawa. This is why I don’t judge the performance of a flight simulator from only one FPS reading.
Is 20 FPS enough for flight simulation?
For me, around 20 FPS or slightly above can still be playable, although I prefer higher frame rates for a smoother experience. What feels acceptable can also vary from one person to another.
Do I need 30 FPS all the time to enjoy X-Plane 11?
I don’t need to maintain 30 FPS throughout an entire flight. During this test, there were several stages where my frame rate was below 30 FPS and I was still able to fly normally. However, when the FPS reached the upper 20s and low 30s, the experience felt more comfortable to me.
Why did I use a complete flight instead of testing one location?
I wanted to see how performance changed during an actual flight rather than judging my laptop from one location. Flying from Toronto to Ottawa allowed me to observe FPS at the gate, during taxi and takeoff, while in flight, and again during approach, landing and taxiing.
What This Flight Taught Me About FPS
My Toronto-to-Ottawa flight gave me a better understanding of the difference between playable performance and comfortable flying. I didn’t need the frame rate to stay in the 30s throughout the entire trip to complete and enjoy the flight.
What mattered more to me was how the simulator actually felt. The lower frame rates weren’t always as smooth, while the upper 20s and low 30s provided a noticeably more comfortable experience.
It also showed me why looking at a single FPS number doesn’t tell the whole story. Performance changed throughout the flight even though I wasn’t changing my graphics settings between each phase.
For anyone using a regular laptop or budget PC for flight simulation, I think it’s worth experiencing an actual flight before deciding whether the performance is good enough. Playable and comfortable can mean different things, and ultimately the right balance depends on what feels acceptable to you while flying.