Microsoft Flight Simulator

Microsoft Flight Simulator is a notoriously demanding title, and the combination of the flagship Intel Core Ultra 9 290K Plus processor with the entry-level NVIDIA GeForce GTX 1650 creates a stark performance bottleneck. The measured data reveals a system where the CPU has immense headroom, but the GPU is consistently overwhelmed, resulting in a gameplay experience that is playable only at the lowest settings and resolutions. The benchmark results indicate a clear hierarchy of constraints, with the graphics card acting as the primary limiter across all tested configurations.

Settings Recommendations

The measured FPS data provides a clear directive for users of this specific hardware pairing. Across all four resolutions tested—3840x2160, 2560x1440, and 1920x1080—the "Low" preset consistently delivers the highest average frame rates, making it the only viable option for a responsive experience. At 1920x1080, the "Low" preset achieves an average of 48 FPS, which is the only configuration in the entire dataset that approaches the generally accepted threshold for smooth, playable performance. The jump from "Low" to "Medium" at this resolution results in a significant 11 FPS drop to 37 FPS, a trade-off that sacrifices substantial fluidity for a marginal visual improvement.

The "Medium" preset can be considered a secondary option for users who prioritize visual fidelity over frame rate stability, particularly at 1080p where the 37 FPS average is technically playable, though not ideal. However, the data shows that the "High" and "Ultra" presets are effectively non-viable. At 1920x1080, "High" produces only 28 FPS and "Ultra" drops to 27 FPS, both of which are below the threshold for comfortable gameplay. The situation worsens dramatically at higher resolutions, where the "High" preset at 2560x1440 yields 23 FPS and at 3840x2160 it plummets to 17 FPS, rendering the simulator a slideshow. The "Ultra" preset is the worst performer, with the lowest average FPS recorded at every resolution, including a 16 FPS average at 4K.

Therefore, the data strongly suggests that the "Low" preset is the only sensible choice for this combo, providing the best balance of frame rate and playability. Users should only consider "Medium" if they have a high tolerance for lower frame rates and are playing at 1080p, as the performance cost of higher settings is not justified by the measured outcomes. The "High" and "Ultra" presets are demonstrably outside the capability of this GPU, regardless of the resolution.

How This Combo Ranks

The performance data positions this combination in the lower echelon of tested systems. The combo rank for Microsoft Flight Simulator is 2885 out of 2996 tested combos, placing it in the bottom 3.7% of all configurations in the database. This low ranking is a direct consequence of the GTX 1650's limited capabilities, as the CPU is a top-tier component. The GPU's average benchmark score is 7472, and its percentile rank against all GPUs is 40, meaning it performs better than only 40% of the graphics cards in the database. This is a clear indication that the GPU is the limiting factor, dragging down the overall system performance.

The CPU, in contrast, is a powerhouse. The Intel Core Ultra 9 290K Plus has a percentile rank of 96 against all CPUs, indicating it is in the top 4% of processors. Its average benchmark score of 84003 is slightly higher than that of its closest rival, the Intel Core Ultra 9 285K, by a margin of 0.2%. This massive disparity in component capability—a top-tier CPU paired with an entry-level GPU—explains the combo's poor ranking in a game that is heavily GPU-bound. The data implies that the CPU is never the bottleneck in this scenario; it is the graphics card that prevents the system from achieving higher frame rates and a better overall rank. The results indicate that this pairing is severely unbalanced for this specific title, with the GPU's performance ceiling being the sole determinant of the final outcome.

GPU Role

The NVIDIA GeForce GTX 1650 is the decisive component in this configuration, and its specifications clearly explain the measured performance. The GPU is equipped with 4 GB of GDDR5 memory, a capacity that is a significant constraint for a modern, high-fidelity simulator like Microsoft Flight Simulator. The memory operates at an effective speed of 8 Gbps across a 128-bit bus, providing a memory bandwidth of 128.1 GB/s. This limited bandwidth and capacity are likely major contributors to the frame rate drops seen at higher resolutions and settings, as the GPU struggles to manage the large textures and geometry data required by the game.

The GPU's compute capabilities are also modest. It features 896 shading units, 56 texture mapping units, and 32 render output units, with a base clock of 1485 MHz and a boost clock of 1665 MHz. These specifications result in a pixel rate of 53.28 GPixel/s and a texture rate of 93.24 GTexel/s, figures that are insufficient for the demands of this simulator at high settings. The GPU's FP32 performance is 2.984 TFLOPS, which is a low figure for a desktop graphics card in this era. The data shows a clear correlation between the GPU's workload and its performance. For example, at 1920x1080, the average FPS drops from 48 on "Low" to 27 on "Ultra," a 21 FPS difference that highlights the GPU's inability to handle the increased shader and texture complexity. The measured results are consistent with a GPU that is operating at its absolute limit, even at the lowest settings.

Measured FPS Breakdown

The measured FPS data provides a detailed view of the system's performance across different resolutions and settings. At 1920x1080, the "Low" preset achieves an average of 48 FPS, which is the highest score recorded for this combo. The "Medium" preset yields an average of 37 FPS, with a minimum of 32 FPS and a maximum of 43 FPS. The "High" preset drops to 28 FPS, and the "Ultra" preset is only marginally better at 27 FPS. This shows a steep performance cliff when moving from "Low" to "Medium," while the difference between "High" and "Ultra" is negligible.

Moving to 2560x1440, the performance degrades further. The "Low" preset averages 39 FPS, which is a 9 FPS drop from the same settings at 1080p. The "Medium" preset averages 30 FPS, with a minimum of 26 FPS and a maximum of 35 FPS. The "High" preset falls to 23 FPS, and the "Ultra" preset averages 22 FPS. The pattern is consistent: each increase in resolution or settings results in a significant loss of frame rate, with the "Low" preset remaining the only option above 30 FPS.

At 3840x2160, the system's limitations are stark. The "Low" preset is the only setting that manages to stay above 20 FPS, with an average of 29 FPS. The "Medium" preset averages 22 FPS, with a minimum of 19 FPS and a maximum of 26 FPS. The "High" preset drops to 17 FPS, and the "Ultra" preset bottoms out at 16 FPS. These figures are all well below the playable threshold, making 4K gaming an impossible task for this GPU. The data reveals that the GTX 1650 can only deliver a smooth experience at 1080p with the "Low" preset, and even that is borderline.

FAQ

Q: What is the best settings preset for this CPU and GPU combo?

A: The "Low" preset is the only viable option for a smooth experience. At 1920x1080, it achieves an average of 48 FPS, which is the highest score recorded. The "Medium" preset at 1080p can be considered with an average of 37 FPS, but all other presets and resolutions result in average frame rates below 30 FPS.

Q: How does this system perform at 4K resolution?

A: The performance at 3840x2160 is very poor. The "Low" preset averages 29 FPS, "Medium" averages 22 FPS, "High" averages 17 FPS, and "Ultra" averages 16 FPS. None of these scores are suitable for a playable experience.

Q: Is the CPU or the GPU the main bottleneck in this system?

A: The data indicates the GPU is the primary bottleneck. The Intel Core Ultra 9 290K Plus is a top-tier processor with a 96th percentile rank, while the GTX 1650 has a 40th percentile rank. The CPU's high benchmark scores and the GPU's low performance in the game's FPS tests confirm that the graphics card is limiting the frame rate.

Q: Is the GTX 1650's 4 GB of VRAM sufficient for this game?

A: The 4 GB of GDDR5 memory is a significant constraint. The measured FPS drops heavily when moving from "Low" to "Medium" settings, which suggests the GPU is running out of memory and bandwidth to handle the increased texture data, especially at higher resolutions.

Q: How does the CPU compare to its nearest rival?

A: The Intel Core Ultra 9 290K Plus has an average benchmark score of 84003, which is 0.2% higher than the Intel Core Ultra 9 285K's score of 83807. It also outperforms the AMD EPYC 4584PX by 1.1% and the AMD EPYC 9135 by 1.2%. This shows the CPU is performing at the top of its class.

Q: What is the frame rate difference between 1080p and 4K on the "Low" preset?

A: The average frame rate drops from 48 FPS at 1920x1080 to 29 FPS at 3840x2160, a decrease of 19 FPS. This significant drop highlights how the GPU's workload scales with resolution, further confirming it as the limiting component.

CPU Role

The Intel Core Ultra 9 290K Plus is a high-end processor that is vastly overqualified for the task of pairing with a GTX 1650 in this game. Its specifications are formidable: it features 24 cores and 24 threads, with a base clock of 3.70 GHz and a boost clock of 5.80 GHz. The CPU also has a large 36 MB of shared L3 cache and supports DDR5 memory with a bandwidth of 115.2 GB/s. These characteristics make it one of the most powerful processors available, and its benchmark scores reflect this. It achieves a Cinebench R23 multi-core score of 51731 and a single-core score of 7303, placing it in the 96th percentile of all CPUs.

In the context of Microsoft Flight Simulator, the CPU's role is to handle the complex flight model, physics, and AI traffic calculations. The data suggests that the CPU is more than capable of performing these tasks without becoming a bottleneck. The measured FPS is consistently low across all settings, and the performance drops are directly correlated with increases in GPU load (higher resolution and settings). If the CPU were the limiting factor, we would expect to see a smaller performance difference between the "Low" and "Ultra" presets, as the CPU load would remain relatively constant. Instead, the data shows a massive performance drop, indicating that the CPU is waiting on the GPU to render frames. The CPU's high PassMark multi-thread score of 60860 and single-thread score of 4823 further confirm its strength, leaving no doubt that the processor is not the cause of the low frame rates.

Resolution Scaling

The resolution scaling data offers a clear picture of the system's bottleneck. From 1920x1080 to 2560x1440 on the "Low" preset, the average FPS drops from 48 to 39, a 9 FPS decrease. Scaling further to 3840x2160, the FPS drops to 29, another 10 FPS decrease. This pattern holds across all settings. For example, on "Medium," the FPS goes from 37 at 1080p to 30 at 1440p to 22 at 4K. This consistent and significant FPS drop with each resolution increase is the classic signature of a GPU-bound system. As the resolution increases, the number of pixels the GPU must render grows exponentially, and the GTX 1650 simply does not have the processing power to keep up.

If the system were CPU-bound, the resolution scaling would be much flatter. The CPU's workload is largely independent of resolution, so we would expect similar frame rates at 1080p and 4K if the CPU were the limiting factor. The data shows the opposite, with a 19 FPS difference between 1080p and 4K on the "Low" preset. This steep decline confirms that the GPU is the sole performance limiter. The CPU is capable of feeding the GPU with data much faster than the GTX 1650 can process it, meaning that the frame rate is entirely dictated by the GPU's rendering capabilities. The data implies that even a significant reduction in resolution does not fully alleviate the GPU's struggle, as it still cannot achieve a consistent 60 FPS even at 1080p on the "Low" preset.