Microsoft Flight Simulator

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

The AMD Ryzen 5 7500X3D brings a 6-core, 12-thread configuration built on the Zen 4 (Raphael) architecture, fabricated on TSMC's 5 nm process. The base clock sits at 4.00 GHz with a boost clock of 4.50 GHz, and the chip carries 96 MB of shared L3 cache — a substantial pool that flight simulators often exploit for streaming terrain and aircraft geometry. The CPU's 65 W TDP suggests efficiency is a design priority, though the measured frame rates in Microsoft Flight Simulator indicate that raw computational muscle is not the limiting factor here.

Benchmark data places this processor in the 89th percentile among all CPUs, with an average benchmark score of 44,573. That score is within 0.2% of the Intel Core Ultra X9 388H (44,466), 0.5% of the Intel Core i9-13950HX (44,342), and 0.6% of the AMD Ryzen AI Max 385 (44,309). It trails the Intel Core i5-14600 (44,889) by 0.7%. These deltas are tiny — sub-1% across the board — meaning the 7500X3D is firmly in a performance tier where CPU headroom should not bottleneck a mid-range GPU in most titles.

Yet the measured FPS in Flight Simulator tells a different story. At 1080p Low, the combo achieves 48 FPS average. Drop to 4K Ultra, and the average falls to 16 FPS. The game is notoriously simulation-heavy, taxing single-thread performance for flight physics and AI, but the CPU's single-thread Passmark score of 3,494 and multithread score of 25,047 suggest it can handle complex calculations. The question becomes whether the GPU or the CPU dictates these numbers.

The data hints at a CPU that is not the primary constraint. At 1080p Low, where GPU load is minimal, the 7500X3D still only manages 48 FPS — not a stellar figure, but respectable for a simulator that models weather, aerodynamics, and global scenery simultaneously. The L3 cache size is notable: 96 MB shared across six cores is generous, and for a game that streams large texture and mesh datasets, this cache likely helps maintain consistent frame pacing. However, the lack of an unlocked multiplier means overclocking is off the table, so the boost clock of 4.50 GHz is the ceiling.

What the data does not show is CPU utilization per core, but the benchmark scores imply the processor is capable. The nearest rival comparisons show the 7500X3D trading blows with high-end laptop and desktop chips, all within a 1% band. For Flight Simulator, the CPU role appears to be providing adequate single-thread responsiveness and cache bandwidth — but the FPS collapse at higher resolutions and settings points squarely at the GPU as the bottleneck.

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

The NVIDIA GeForce GTX 1650 is a Turing-architecture card on the 12 nm process, featuring 4 GB of GDDR5 memory on a 128-bit bus with 128.1 GB/s bandwidth. Its base clock is 1485 MHz, boosting to 1665 MHz, and it delivers 2.984 TFLOPS of FP32 performance. The 4 GB VRAM is the most glaring limitation for a game like Microsoft Flight Simulator, which loads high-resolution textures for terrain, aircraft, and airports.

The GPU sits in the 40th percentile among all GPUs, with an average benchmark score of 7,472. Its nearest rivals are telling: the AMD Radeon HD 8850M (7,447, 0.3% slower), Intel UHD Graphics 750 (7,441, 0.4% slower), AMD Radeon R7 350 (7,425, 0.6% slower), and Intel Arc A310 (7,550, 1% faster). This is entry-level territory. The GTX 1650 is essentially competing with integrated graphics and low-end discrete parts from years past.

The measured FPS confirms the GPU's struggle. At 1080p Low, the combo hits 48 FPS — the only playable result in the entire dataset. Move to 1080p Medium, and the average drops to 37 FPS with a minimum of 32 FPS. At 1080p High, 28 FPS; at 1080p Ultra, 27 FPS. The delta between Low and Ultra at 1080p is just 21 FPS, suggesting the GPU is already saturated even at the lowest settings.

The 4 GB VRAM is likely a hard ceiling. Flight Simulator's high-resolution texture packs can exceed 4 GB at higher settings, forcing the GPU to swap data to system memory, which causes stutter and severe FPS drops. The measured minimum FPS at 1080p Medium is 32 FPS, while the maximum is 43 FPS — a 11 FPS spread that hints at memory pressure. At 1440p and 4K, the situation worsens dramatically, as the pixel count and texture demands outstrip the 128-bit memory bus and 128.1 GB/s bandwidth.

The GTX 1650's 75 W TDP and lack of power connectors make it a low-power card, but that efficiency does not translate to gaming headroom. With 896 shading units, 56 TMUs, and 32 ROPs, the card is architecturally modest. The pixel rate of 53.28 GPixel/s and texture rate of 93.24 GTexel/s are figures that can handle 1080p at low-to-medium settings in lighter titles, but Flight Simulator's rendering of vast landscapes and complex lighting pushes the GPU to its limits.

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

The measured FPS data reveals a steep resolution penalty. At 1080p Low, the average is 48 FPS. At 1440p Low, it drops to 39 FPS — a 18.8% decrease. At 4K Low, the average falls to 29 FPS, which is 39.6% below the 1080p figure. This scaling pattern is characteristic of a GPU-bound scenario: as resolution increases, the pixel fill rate and memory bandwidth demands grow, and the GTX 1650 cannot keep pace.

For Medium settings, the progression is 37 FPS at 1080p, 30 FPS at 1440p, and 22 FPS at 4K. The drop from 1080p to 4K is 40.5%, consistent with the Low preset's scaling. High settings show 28 FPS at 1080p, 23 FPS at 1440p, and 17 FPS at 4K — a 39.3% reduction from 1080p to 4K. Ultra settings are the worst: 27 FPS at 1080p, 22 FPS at 1440p, and 16 FPS at 4K, a 40.7% drop.

The consistency of these percentage drops — all hovering around 40% — is a strong indicator that the GPU is the limiting component across all settings. If the CPU were the bottleneck, the FPS would remain relatively flat as resolution increases, because the CPU workload (physics, AI, game logic) does not scale with pixel count. Here, every resolution step costs roughly 15-20% performance, which is textbook GPU-bound behavior.

However, the absolute FPS numbers are low even at 1080p Low. A CPU-bound scenario would typically show higher FPS at low settings and resolution, but 48 FPS is modest. This suggests that while the GPU is the primary constraint, the game's engine is also demanding on the CPU side — or that the GTX 1650's 4 GB VRAM is causing additional overhead even at 1080p Low due to texture streaming.

The 4K Ultra result of 16 FPS is essentially unplayable, and even 4K Low at 29 FPS is a slideshow. The data implies that this combo is only viable at 1080p with Low or possibly Medium settings, and any attempt to scale resolution will be met with severe performance degradation. The GPU's 128.1 GB/s bandwidth is a fundamental limit — 4K requires roughly four times the pixel data of 1080p, and the memory subsystem simply cannot feed the rendering pipeline fast enough.

# How This Combo Ranks — use comboRankInGame vs other tested combos

The combination of the AMD Ryzen 5 7500X3D and NVIDIA GeForce GTX 1650 ranks 2,885 out of 2,996 tested combos in Microsoft Flight Simulator. That places it in the bottom 3.7% of all configurations — a stark illustration of how a strong CPU is wasted when paired with a weak GPU in this particular title.

The rank is driven almost entirely by the GPU. The CPU's 89th percentile standing among all processors is irrelevant when the GPU sits in the 40th percentile. Flight Simulator is a game that scales heavily with GPU capability, especially at higher resolutions and settings. The GTX 1650's 4 GB VRAM and 2.984 TFLOPS of compute are simply inadequate for the game's rendering demands.

To contextualize the rank: if the combo were paired with a GPU in the 80th percentile, the rank would likely improve dramatically, as the CPU's benchmark scores show it can compete with high-end mobile and desktop chips. But the data measures the combo as tested, and the result is a bottom-tier ranking.

The nearest rival GPUs to the GTX 1650 — the Intel UHD Graphics 750 and AMD Radeon R7 350 — are not gaming cards by modern standards. The fact that the GTX 1650 is only 0.4% faster than Intel's integrated graphics in average benchmark score underscores how far behind the curve this GPU is. For Flight Simulator, which is one of the most demanding titles on the market, this combo's rank of 2,885 is unsurprising.

The takeaway from the ranking is that the CPU is not the differentiator here. The 7500X3D has the compute headroom to drive higher frame rates, but the GTX 1650 cannot deliver them. Any upgrade path would focus on the GPU first; the CPU is already in a strong position relative to its peers.

# Settings Recommendations — which preset gives the best experience per the measured rows

Given the measured FPS data, the only viable preset for a playable experience is 1080p Low, which averages 48 FPS. This is the only configuration in the entire dataset that approaches smooth gameplay. The 1080p Medium preset averages 37 FPS with a minimum of 32 FPS — borderline playable but with noticeable dips during complex scenes or when flying over dense urban areas.

For users who prioritize visual fidelity over frame rate, 1080p High at 28 FPS average is technically possible, but the sub-30 FPS average will feel stuttery. The Ultra preset at 1080p yields 27 FPS, which is barely different from High — a sign that the GPU is already maxed out and the extra settings are not the bottleneck.

At 1440p, no preset delivers playable performance. Low averages 39 FPS, but the minimum is not recorded, and 39 FPS is still below the 60 FPS target most simmers prefer. Medium at 1440p averages 30 FPS with a minimum of 26 FPS — playable for casual flying but not for serious simulation. High and Ultra at 1440p are 23 FPS and 22 FPS, respectively, which are too low for comfortable use.

At 4K, all presets are effectively unplayable. Low averages 29 FPS, Medium 22 FPS, High 17 FPS, and Ultra 16 FPS. The 4K data serves as a reference point for how the combo scales, but no user should attempt 4K with this hardware.

The best experience per the measured rows is unequivocally 1080p Low. It provides the highest average FPS (48) and the most headroom for dips. If a user insists on Medium settings, 1080p Medium at 37 FPS average with a 32 FPS minimum is acceptable for non-competitive flight simulation, but the risk of stutter during heavy scenery loads is real. The data does not support any settings above Medium at any resolution.

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

The measured FPS data is as follows:

1920x1080 (1080p):

• Low: 48 FPS average
• Medium: 37 FPS average, 32 FPS minimum, 43 FPS maximum
• High: 28 FPS average
• Ultra: 27 FPS average

2560x1440 (1440p):

• Low: 39 FPS average
• Medium: 30 FPS average, 26 FPS minimum, 35 FPS maximum
• High: 23 FPS average
• Ultra: 22 FPS average

3840x2160 (4K):

• Low: 29 FPS average
• Medium: 22 FPS average, 19 FPS minimum, 26 FPS maximum
• High: 17 FPS average
• Ultra: 16 FPS average

The 1080p Low result of 48 FPS is the only average above 40 FPS in the entire dataset. The 1080p Medium minimum of 32 FPS is the highest minimum recorded, indicating that this setting has the most consistent frame pacing among the higher presets. The 4K Ultra average of 16 FPS is the lowest, with no minimum or maximum recorded, suggesting the GPU is completely saturated.

At 1080p, the spread between Low and Ultra is 21 FPS (48 to 27). At 1440p, the spread narrows to 17 FPS (39 to 22). At 4K, the spread is 13 FPS (29 to 16). This narrowing spread at higher resolutions confirms that the GPU is the limiting factor — as resolution increases, the settings have less impact because the GPU is already overwhelmed by pixel count.

The Medium preset is the only one with minimum and maximum values recorded across all resolutions. At 1080p Medium, the range is 32-43 FPS (11 FPS spread); at 1440p Medium, 26-35 FPS (9 FPS spread); at 4K Medium, 19-26 FPS (7 FPS spread). The shrinking range at higher resolutions further indicates GPU saturation — there is less variance because the GPU is consistently at its limit.

# FAQ

Q: Is the AMD Ryzen 5 7500X3D a bottleneck in this combo?

A: No. The CPU ranks in the 89th percentile among all CPUs with an average benchmark score of 44,573, within 0.7% of its nearest rivals. The FPS drops across resolutions (48 at 1080p Low to 29 at 4K Low) are consistent with GPU-bound scaling, indicating the GTX 1650 is the limiting component.

Q: Can this combo run Microsoft Flight Simulator at 4K?

A: Technically yes, but not playably. The best 4K result is 29 FPS average at Low settings, and Ultra averages 16 FPS. The 4 GB VRAM and 128.1 GB/s memory bandwidth of the GTX 1650 are insufficient for 4K rendering in this title.

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

A: The data shows 1080p Low delivers 48 FPS average, the only playable result. 1080p Medium at 37 FPS average (32 FPS minimum) is acceptable for casual flight, but no preset above Medium at 1080p, or any preset at 1440p or 4K, provides adequate performance.

Q: How does the GTX 1650 compare to its nearest GPU rivals?

A: The GTX 1650 has an average benchmark score of 7,472, placing it in the 40th percentile. It is 0.3% faster than the AMD Radeon HD 8850M (7,447), 0.4% faster than the Intel UHD Graphics 750 (7,441), 0.6% faster than the AMD Radeon R7 350 (7,425), and 1% slower than the Intel Arc A310 (7,550).

Q: What is the FPS difference between 1080p and 4K at Medium settings?

A: At 1080p Medium, the average is 37 FPS (minimum 32, maximum 43). At 4K Medium, the average is 22 FPS (minimum 19, maximum 26). This is a 40.5% drop, consistent with the GPU being the primary bottleneck.

Q: Is the CPU's 96 MB L3 cache beneficial for this game?

A: The CPU's benchmark scores suggest strong cache performance, and the 89th percentile ranking indicates overall capability. However, the measured FPS shows the GPU limits performance, so the cache's potential benefit is not realized in this combo. A stronger GPU would be needed to leverage the CPU's advantages.