Microsoft Flight Simulator

The pairing of the Intel Core Ultra 5 125H with the NVIDIA GeForce RTX 5090 in Microsoft Flight Simulator presents a particularly lopsided configuration, one where a mobile processor designed for efficiency is tasked with feeding one of the most powerful graphics cards ever produced. The measured frame rates across resolutions and settings reveal a system that is almost always constrained by the CPU, with the GPU’s immense capabilities frequently left waiting for more data. This analysis breaks down those measurements, explaining the role each component plays and what the numbers mean for the overall experience.

CPU Role — cores, clocks, and how they relate to this game's results

The Intel Core Ultra 5 125H is a 14-core, 18-thread mobile processor based on the Meteor Lake architecture, built on Intel's 7 nm process. Its base clock is 3.60 GHz, with a boost clock of 4.50 GHz, and it carries 18 MB of shared L3 cache. While the processor’s synthetic benchmark scores are respectable — a Cinebench R23 multi-core score of 12804.5 and a single-core score of 1647.5 — its position in the broader market is more telling. The CPU’s percentileVsAllCpus is 79, meaning it outperforms 79% of all processors in the database, yet its avgBenchmarkScore of 27507 places it in close competition with desktop parts like the AMD Ryzen 7 5800 (avgScore 27535, deltaPct -0.1) and the Intel Core i5-12600K (avgScore 27578, deltaPct -0.3). This indicates that while the 125H is a capable chip, it is not in the top tier of processing power, especially when compared to the desktop-grade silicon that might typically accompany an RTX 5090.

In Microsoft Flight Simulator, the CPU’s role is paramount. The simulation engine must constantly calculate flight physics, weather, and the positions of countless objects in the world. The data strongly suggests that this workload is what limits the system. At 1080p Low settings, the average frame rate is 173 FPS. When the resolution is increased to 4K Low, the frame rate drops to 103 FPS. A pure GPU bottleneck would typically show a much steeper drop at higher resolutions, but here the drop is roughly 40%, suggesting that even at Low settings, the CPU is working hard to feed frames. The processor’s single-thread performance, as evidenced by a PassMark single-thread score of 3399, is a critical factor. Flight simulators often have a primary simulation thread that cannot be fully parallelized, so this single-core capability directly influences the ceiling for frame rates. The dual-threaded nature of the 125H, with its 18 threads, helps with secondary tasks like rendering draw calls, but the core simulation loop appears to be the bottleneck. The benchmark results imply that the CPU is consistently the limiting factor, as the GPU rarely seems to be waiting for more work. The 125H’s 28 W TDP classifies it as a power-efficient mobile part, but that efficiency comes at the cost of raw sustained performance, which is a critical trade-off for a game as demanding as this one.

GPU Role — VRAM, clocks, and how they relate to this game's results

The NVIDIA GeForce RTX 5090 is a flagship desktop GPU based on the Blackwell 2.0 architecture, built on a 5 nm process at TSMC. It is a behemoth with 32 GB of GDDR7 memory on a 512-bit bus, providing a staggering 1.79 TB/s of memory bandwidth. Its boost clock is 2407 MHz, and it houses 21760 shading units. The GPU’s synthetic benchmark scores are equally dominant, with a PassMark G3D score of 39650 and a Geekbench Vulkan score of 376728. Its percentileVsAllGpus is 92, and its avgBenchmarkScore of 79842 puts it in the same league as data-center accelerators like the NVIDIA Tesla P100 PCIe 16 GB (avgScore 79605, deltaPct 0.3). This is a GPU with an enormous amount of raw compute and memory resources, far beyond what is needed for typical gaming at any resolution.

In the context of Microsoft Flight Simulator, the RTX 5090’s role is to render the incredibly detailed world. The 32 GB of VRAM is more than sufficient for even the highest resolution textures and draw distances the game can throw at it, and the 1.79 TB/s bandwidth ensures that texture streaming is never a bottleneck. However, the measured frame rates suggest that the GPU is often underutilized. For instance, at 1080p Ultra, the average FPS is 96. At 4K Ultra, it drops to 57 FPS. This is a relatively modest decrease for a 4x increase in pixel count, which is a classic sign of a CPU bottleneck. If the GPU were the limiting factor, the 4K Ultra frame rate would be far lower, likely in the 20s or 30s, given the massive increase in rendering load. Instead, the data shows that the GPU has enough headroom to handle the extra pixels without collapsing performance, because the CPU is unable to feed it frames any faster. The GPU’s raw power is being held back. The passmark_directx_12 score of 185 and passmark_directx_11 score of 341 are interesting but don’t directly translate to this game’s performance. The RTX 5090 is clearly capable of far higher frame rates in this title than it is achieving, which points the finger squarely at the processor as the performance ceiling. The GPU is waiting, not working.

Resolution Scaling — how FPS drops from 1080p to 4K and what it says about the limiting component

The resolution scaling of the measured FPS data is the clearest indicator of where the bottleneck lies. Let’s look at the High settings preset across the three resolutions. At 1920x1080, the average FPS is 101. At 2560x1440, it drops to 82 FPS, a decrease of about 19%. At 3840x2160, it falls to 60 FPS, a further drop of about 27% from 1440p. For a GPU-bound scenario, we would expect a much more dramatic decline. Going from 1080p to 1440p increases pixel count by 78%, and from 1440p to 4K, by another 125%. The fact that the FPS drops are far smaller than the pixel count increases indicates that the GPU is not the primary constraint. If it were, the frame rate would scale almost inversely with the pixel count.

Consider the Low settings preset. At 1080p Low, the average is 173 FPS. At 1440p Low, it’s 139 FPS, and at 4K Low, it’s 103 FPS. The drop from 1080p to 4K is about 40%. This is a significant reduction, but still less than the 4x increase in resolution. This suggests that even at Low settings, where the GPU load is minimal, the CPU is still the limiting factor. The CPU has to compute the game world and issue draw calls, and that work doesn’t change with resolution. The GPU, on the other hand, has less work to do at Low settings, but it still can’t push past the CPU’s frame generation limit. The same pattern holds for Medium and Ultra settings, though the absolute frame rates are lower. This consistent behavior across all presets is the definitive proof: the Intel Core Ultra 5 125H is the bottleneck in this system. The RTX 5090 is capable of much higher performance, but it is being starved of data by the CPU. The frame rate scaling is a function of the CPU’s speed, not the GPU’s rendering capability.

Measured FPS Breakdown — resolution by resolution, settings by settings, exact numbers

The measured FPS data provides a complete picture of this system’s performance in Microsoft Flight Simulator. Here is the exact breakdown.

At 3840x2160 (4K):

• Low: average FPS of 103.
• Medium: average FPS of 80, with a minimum of 68 and a maximum of 92.
• High: average FPS of 60.
• Ultra: average FPS of 57.

At 2560x1440 (1440p):

• Low: average FPS of 139.
• Medium: average FPS of 109, with a minimum of 92 and a maximum of 125.
• High: average FPS of 82.
• Ultra: average FPS of 78.

At 1920x1080 (1080p):

• Low: average FPS of 173.
• Medium: average FPS of 135, with a minimum of 114 and a maximum of 155.
• High: average FPS of 101.
• Ultra: average FPS of 96.

These numbers reveal a few key trends. First, the difference between High and Ultra settings is remarkably small at every resolution. At 4K, High averages 60 FPS while Ultra averages 57 FPS, a difference of only 3 FPS. At 1440p, the gap is 4 FPS (82 vs 78), and at 1080p, it’s 5 FPS (101 vs 96). This suggests that the Ultra preset adds significant graphical effects that are not heavily taxing the GPU, or that the CPU bottleneck is so severe that the extra load on the GPU is hidden. The Medium preset provides a substantial step up from Low, but the jump from Medium to High is more pronounced than from High to Ultra. For instance, at 1080p, Low is 173 FPS, Medium is 135 FPS, High is 101 FPS, and Ultra is 96 FPS. The frame rate drops are consistent, but the High-to-Ultra delta is the smallest, implying diminishing returns from the most demanding settings. The minimum and maximum FPS data for Medium settings show a variance of about 24 FPS at 1080p (114 min, 155 max), 33 FPS at 1440p (92 min, 125 max), and 24 FPS at 4K (68 min, 92 max). This indicates that frame pacing is relatively stable, but the overall numbers are capped by the CPU.

FAQ

Q: Why is the frame rate so similar between High and Ultra settings?

A: The data shows a difference of only 3-5 FPS between High and Ultra across all resolutions. This indicates that the system is not GPU-limited at these settings; the CPU is the primary constraint. The extra graphical load from Ultra settings doesn’t translate to a significant FPS drop because the CPU cannot generate frames quickly enough to expose the GPU’s limitations.

Q: Is this system good for playing Microsoft Flight Simulator at 4K?

A: The benchmark results show that at 4K Ultra, the average FPS is 57, and at 4K High, it’s 60 FPS. This is playable, but it falls short of the 60 FPS target in the most demanding preset. The GPU is capable of more, but the CPU bottleneck prevents higher frame rates.

Q: What is the best resolution to play at with this combo?

A: At 1440p High, the system averages 82 FPS, which offers a smooth experience. At 1080p High, it’s 101 FPS. The data suggests that 1440p provides a good balance, as the frame rate is still high, and the resolution offers better visual clarity than 1080p without the steep FPS penalty seen at 4K.

Q: How does the CPU compare to its nearest rivals in synthetic benchmarks?

A: The Intel Core Ultra 5 125H has an average benchmark score of 27507. This is essentially identical to the AMD Ryzen 7 5800 (deltaPct -0.1) and the Intel Core i5-12600K (deltaPct -0.3), while being 0.5% ahead of the AMD Ryzen 3 PRO 5355G. This places it in a mid-range performance tier, not a top-tier one.

Q: Does the GPU’s 32 GB of VRAM matter for this game?

A: The RTX 5090 has 32 GB of GDDR7 memory, which is more than enough for Microsoft Flight Simulator’s highest texture settings. The data shows that the GPU is not the limiting factor in any of the measured configurations, so VRAM capacity is not a performance issue here.

Q: What is the limiting factor for this system in this game?

A: The data clearly points to the CPU. The frame rate scaling from 1080p to 4K is much smaller than the increase in pixel count, and the FPS differences between High and Ultra are minimal. This indicates that the Intel Core Ultra 5 125H is unable to feed frames to the RTX 5090 fast enough, making it the performance bottleneck.

Settings Recommendations

Based on the measured FPS data, the optimal settings for this system depend on the user’s priority for resolution versus frame rate. For a smooth and visually rich experience at 2560x1440, the High preset is the best choice, averaging 82 FPS. This provides a significant visual upgrade over Medium (109 FPS) while still maintaining a frame rate well above 60. The gap to Ultra (78 FPS) is only 4 FPS, but High is the safer pick for consistent performance. If the user prefers maximum visual fidelity, Ultra at 1440p is still playable at 78 FPS, but the frame rate is closer to the 60 FPS threshold. At 1920x1080, the High preset offers an excellent experience with an average of 101 FPS, which is smooth and responsive. The Medium preset at 135 FPS would be for those with high-refresh-rate monitors, but the visual quality difference is substantial. Ultra at 1080p (96 FPS) is also viable, but the 5 FPS gain over High is not worth the potential for more demanding scenes to cause dips. For 3840x2160, the choice is more constrained. The High preset averages 60 FPS, which is right at the target for many displays. Ultra averages 57 FPS, which is slightly below the 60 FPS line. Therefore, High is the recommended setting for 4K, as it provides the best balance of visual quality and performance, ensuring a stable 60 FPS in most situations. The Medium preset at 4K (80 FPS) is an option for those who want higher headroom, but the visual downgrade from High is noticeable. In summary, the data suggests that High settings are the sweet spot for this CPU-GPU combination, offering the best compromise between image quality and frame rate across all resolutions. The system’s CPU bottleneck means that pushing to Ultra yields negligible returns, so High is the most efficient choice.

How This Combo Ranks

The combination of the Intel Core Ultra 5 125H and the NVIDIA GeForce RTX 5090 is ranked 586th out of 2996 tested combinations in Microsoft Flight Simulator, placing it in the top 20% of all systems in the database. This rank reflects the measured performance, which is heavily influenced by the CPU bottleneck. The ranking reflects the GPU’s raw power, as the RTX 5090 can still achieve playable frame rates at 4K despite being held back by the processor. However, the rank also shows that many other combinations, likely those with more powerful desktop CPUs, achieve much higher frame rates. The data implies that this pairing is inefficient. The GPU is capable of far more, but the CPU cannot deliver. The rank of 586 suggests that while this system is above average, it does not fully utilize the potential of its components. A system with a more powerful CPU would likely rank significantly higher, as the RTX 5090 would be able to stretch its legs. The results indicate that the mobile 125H is a significant limiting factor, and the system’s overall performance in this game is capped by its processor. The high rank is a direct result of the RTX 5090’s immense capabilities, but the low CPU performance prevents it from being a top-tier contender. This pairing is a study in imbalance, where the GPU’s power is largely unrealized due to the CPU’s constraints.