Microsoft Flight Simulator

Microsoft Flight Simulator running on the Intel Core Ultra 9 275HX and NVIDIA GeForce RTX 5050 Mobile is a GPU-limited pairing in a game famous for punishing hardware, and the measured data reflects exactly that. At 1080p Low the combo reaches 88 FPS, yet at 4K Ultra it falls to 29 FPS — a collapse that points squarely at the graphics side rather than the CPU, which sits in the 94th percentile of all tested processors. The pairing ranks 2976 out of 3714 tested combinations in this title, which tells you up front that this is a workable but far from leading configuration for one of the most demanding flight simulators ever released.

Resolution Scaling

The scaling story across resolutions is consistent across every preset, and that consistency is the diagnostic key. Take the Low preset: 88 FPS at 1920x1080, 71 FPS at 2560x1440, and 52 FPS at 3840x2160. That is a drop of roughly 19% from 1080p to 1440p and roughly 27% further from 1440p to 4K — meaning the frame rate at 4K Low is about 59% of what it is at 1080p Low. Now compare the High preset: 51 FPS at 1080p, 41 FPS at 1440p, 31 FPS at 4K. The proportional losses are almost identical to Low. Ultra behaves the same way, sliding from 49 FPS at 1080p to 39 at 1440p and 29 at 4K.

What this tells you is that the performance envelope is governed almost entirely by pixel throughput. When a CPU is the bottleneck, raising the resolution barely dents frame rates; here, every resolution step costs the same relative chunk of performance regardless of how light or heavy the settings preset is. The RTX 5050 Mobile, with its 128-bit memory bus, 8 GB of GDDR7, and 384.0 GB/s of bandwidth, simply runs out of shading and fill capacity as the pixel count quadruples from 1080p to 4K. The pixel rate of 48.00 GPixel/s and texture rate of 120.0 GTexel/s define a hard ceiling, and Microsoft Flight Simulator's heavy scenery streaming and draw-distance workload pushes straight into it.

The steepness matters too. The 1080p-to-4K fall at Medium goes from 68 FPS to 41 FPS — losing 27 FPS, roughly 40% of the total. A well-balanced mobile pairing would retain more. The data indicates the 275HX has headroom to spare; the GPU does not.

How This Combo Ranks

Out of 3714 tested hardware combinations in Microsoft Flight Simulator, the Core Ultra 9 275HX plus RTX 5050 Mobile sits at rank 2976. That places it in the bottom fifth of the chart for this specific title — a striking result given how strong each component is in isolation.

The CPU half of the pairing is not the problem. The Core Ultra 9 275HX sits in the 94th percentile versus all CPUs, with an average benchmark score of 67469. Its nearest rivals at the aggregate level include the Intel Xeon w5-3525 (average score 67673, just 0.3% ahead), the AMD EPYC 4484PX (67822, 0.5% ahead), the AMD Ryzen Threadripper PRO 5955WX (67868, 0.6% ahead), and the Intel Xeon 6515P (67006, 0.7% behind). In other words, this mobile chip trades blows with workstation-class silicon. Its Cinebench R23 multi-core score of 35589 and single-core score of 2204, plus a Geekbench single-core result of 2458, confirm a processor with genuinely strong per-core output — which matters in a simulator that leans on single-threaded performance for flight dynamics and scenery logic.

The GPU half drags the combo down. The RTX 5050 Mobile sits in the 83rd percentile versus all GPUs with an average score of 43268, statistically tied with the NVIDIA Quadro M6000 24 GB (43262, 0% delta), the Quadro M6000 (43301, 0.1% ahead), and the NVIDIA GeForce RTX 4070 SUPER (43223, 0.1% behind), while the GeForce RTX 4090 Mobile is only 0.9% ahead at 43667. Those aggregate scores reflect general compute and synthetics — a 3DMark Steel Nomad DX12 score of 2365 and a Geekbench OpenCL result of 84171 — but Microsoft Flight Simulator is not a general workload. It is one of the most VRAM- and bandwidth-hungry titles in the database, and a rank of 2976 out of 3714 is the direct consequence: a 94th-percentile CPU chained to a GPU whose strengths do not align with this game's demands.

GPU Role

The RTX 5050 Mobile is a Blackwell 2.0 part built on TSMC's 5 nm process, packing 16,900 million transistors into a 149 mm² die at a density of 113.4M transistors per mm². Its specifications read like an efficient entry-tier design: 2560 shading units, 80 TMUs, 32 ROPs, 20 RT cores, and 80 tensor cores, with FP32 throughput of 7.680 TFLOPS and a boost clock of 1500 MHz from a 1020 MHz base. Its 8 GB of GDDR7 runs at 1500 MHz (24 Gbps effective) over a 128-bit bus, yielding 384.0 GB/s of bandwidth.

Against Microsoft Flight Simulator, three of those numbers dominate the interpretation. First, the 8 GB VRAM capacity. This simulator streams enormous amounts of photogrammetry and terrain data, and 8 GB is the practical floor for high-detail textures at higher resolutions — the sharp drop from 52 FPS at 4K Low to 29 FPS at 4K Ultra is consistent with both the fill-rate cost of higher presets and memory pressure at 3840x2160. Second, the 128-bit bus and 384.0 GB/s bandwidth. That is a narrow pipe by the standards of this game's appetite, and it helps explain why frame rates scale down so steeply with resolution rather than plateauing. Third, the 50 W TDP. This is a power-constrained mobile design, and sustained scenery-heavy flight segments will keep it pinned at its limits, which is exactly the regime where measured averages settle where they do — in the 29-to-52 FPS band at 4K depending on preset.

The CPU side, by contrast, barely breaks a sweat in the data. The 275HX is an Arrow Lake-HX design on TSMC's 3 nm node, with 24 cores and 24 threads, a 2.70 GHz base and 5.40 GHz boost, 36 MB of shared L3 cache, and 102.4 GB/s of dual-channel DDR5 bandwidth. Its 55 W TDP and PCIe Gen 5 connectivity with 20 CPU lanes mean it can feed the GPU without compromise. Nothing in the resolution-scaling pattern suggests CPU saturation; if it were the limiter, the 4K rows would sit much closer to the 1080p rows. They do not.

Settings Recommendations

The measured rows make the recommendations straightforward.

For 1080p play, Low is the frame-rate play at 88 FPS, but Medium is the sweet spot: 68 FPS average with a measured floor of 58 FPS and ceiling of 78 FPS. That minimum figure matters enormously in a flight simulator, where stuttering during landing approaches or dense-city flyovers is more disruptive than in almost any other genre. A 58 FPS floor keeps the experience smooth even in worst-case measured moments. High (51 FPS) and Ultra (49 FPS) at 1080p are playable but leave little margin — High buys only visual polish over Medium while surrendering 17 FPS of average.

At 1440p, Medium remains the best compromise at 55 FPS average, 47 minimum, 63 maximum. The 47 FPS floor is still comfortable for a simulator, where 30-to-60 FPS is broadly considered fluid thanks to the slower pace of cockpit views. High at 41 FPS and Ultra at 39 FPS are borderline; they hover at the edge of smoothness and will dip below it in heavy scenes.

At 4K, the honest recommendation is Low. Medium averages 41 FPS with a 35-to-47 measured range, and a 35 FPS floor is where perceptible judder begins in panning cockpit shots. Low's 52 FPS average at 4K delivers the most stable 4K experience this pairing can offer. Ultra at 4K — 29 FPS — should be treated as a showcase setting only, not a play setting.

One more observation: the gap between High and Ultra is small everywhere — 2 FPS at 1080p, 2 FPS at 1440p, 2 FPS at 4K. Given how little performance separates them, there is essentially no scenario where Ultra is preferable to High on this hardware; the data shows Ultra costs frame rate for negligible practical difference in the measured aggregate.

Measured FPS Breakdown

All figures below are measured averages for Microsoft Flight Simulator on this exact pairing; where captured, minimum and maximum frame rates are included.

3840x2160 (4K):

• Ultra: 29 FPS average
• High: 31 FPS average
• Medium: 41 FPS average (35 min / 47 max)
• Low: 52 FPS average

2560x1440:

• Ultra: 39 FPS average
• High: 41 FPS average
• Medium: 55 FPS average (47 min / 63 max)
• Low: 71 FPS average

1920x1080:

• Ultra: 49 FPS average
• High: 51 FPS average
• Medium: 68 FPS average (58 min / 78 max)
• Low: 88 FPS average

Reading across the rows: Low loses 36 FPS going from 1080p to 4K, Medium loses 27, High loses 20, and Ultra loses 20. The lower the preset, the more absolute performance resolution costs — which is another signature of a GPU-limited system, since lighter settings expose more of the pixel-pipeline cost of the resolution itself. Within any given resolution, the preset ladder is tight: at 1080p, the entire span from Ultra to Low is 39 FPS; at 4K it is 23 FPS. The simulator's settings overhead is real but modest compared to its resolution overhead on this GPU.

The Medium rows are the only ones with min/max capture, and they are instructive: the 1080p Medium range of 58-to-78 sits entirely above the 4K High average of 31, and the 1440p Medium floor of 47 nearly matches the 1440p High average of 41. If consistent frame pacing is the goal, Medium at a lower resolution beats High at a higher one every time in this dataset.

FAQ

Q: Is this pairing good for Microsoft Flight Simulator?

A: It is adequate but bottom-tier for this specific title. The combo ranks 2976 out of 3714 tested configurations. The CPU is excellent — 94th percentile versus all CPUs — but the RTX 5050 Mobile's 8 GB of GDDR7 on a 128-bit bus limits this game specifically, producing 29-to-52 FPS at 4K and 49-to-88 FPS at 1080p depending on preset.

Q: Which component is the bottleneck?

A: The GPU. Frame rates drop proportionally with resolution at every preset — 88 FPS at 1080p Low becomes 52 FPS at 4K Low, a loss of about 40% — which is the classic signature of a graphics-side limit. A CPU-limited system would show much flatter scaling. The 275HX's strong single-core results (Geekbench single-core 2458, Cinebench R23 single-core 2204) indicate ample processor headroom.

Q: Can it run the game at 4K?

A: Yes, but only comfortably at Low, which averages 52 FPS. Medium at 4K averages 41 FPS with a measured minimum of 35 FPS, and High and Ultra average 31 and 29 FPS respectively — playable for slow sightseeing, marginal for anything requiring smooth panning.

Q: What settings give the smoothest experience?

A: Medium at 1920x1080 is the standout: 68 FPS average with a 58 FPS minimum and 78 FPS maximum. That floor of 58 FPS makes it the most consistent measured configuration in the dataset. Medium at 1440p (55 FPS average, 47 minimum) is the best option for higher-resolution displays.

Q: Is the Core Ultra 9 275HX a strong CPU overall?

A: Yes. It averages 67469 across benchmark suites, placing it in the 94th percentile of all CPUs and within a fraction of a percent of workstation parts like the Intel Xeon w5-3525 (67673 average, 0.3% delta) and AMD EPYC 4484PX (67822, 0.5% delta). It posts 35589 in Cinebench R23 multi-core and 19899 in Cinebench R20 multi-core.

Q: Is there any reason to use the Ultra preset?

A: No, per the measured data. Ultra trails High by only 2 FPS at every resolution — 49 vs 51 at 1080p, 39 vs 41 at 1440p, 29 vs 31 at 4K — while sitting 19-to-20 FPS below Medium at each step. Ultra costs performance without a meaningful measured advantage over High on this hardware, and High itself is already outclassed by Medium in frame rate.