Learn how FSX uses multiple CPU cores, why one main thread limits frame rates, and which settings and affinity changes improve CPU performance.
Yes. A fully updated boxed copy of FSX and FSX: Steam Edition can use multiple CPU cores, chiefly for terrain and texture work, but the main simulation and rendering thread remains heavily serial. Faster per-core performance matters more than a large core count; reduce CPU-heavy settings before experimenting with processor affinity.
How does FSX use multiple CPU cores?
FSX splits some scenery work across worker threads while keeping much of each frame on one main thread. This prevents it from distributing its workload evenly across a modern processor.
| Workload | Typical CPU behaviour | Practical result |
|---|---|---|
| Main simulation and rendering | Dominated by one main thread | One busy logical processor can limit frame rate |
| Terrain texture synthesis and scenery loading | Can use additional worker threads | Other cores may become active as scenery loads |
| AI traffic, gauges and add-ons | Varies; much of the work can still burden the main thread | Complex aircraft and airports often expose the bottleneck |
| Windows, drivers and external add-on processes | Scheduled separately across available processors | Total CPU usage may look spread out without FSX itself scaling evenly |
The original unpatched boxed release is the exception because later official updates added important multicore terrain improvements. Bring boxed FSX to the SP2/Acceleration code level. FSX: Steam Edition already incorporates the later engine code, so it does not need the boxed service packs.
Windows may move the main thread between logical processors, so no single Task Manager graph necessarily remains at 100%. Low total CPU usage also does not prove there is spare FSX performance: one saturated thread on a many-core processor can hold up the entire frame.
How can I improve FSX CPU performance?
The biggest CPU gains come from reducing settings that create objects and AI calculations, not from lowering screen resolution. Make one change at a time and repeat the same aircraft, airport, weather and view so the comparison means something.
- Update boxed FSX first. Performance tweaks cannot replace the multicore improvements included with the later official engine updates.
- Reduce AI and ground traffic. Lower airline and general aviation traffic, airport vehicle density, road vehicles, ships and leisure boats. Busy hubs with dense AI schedules are among the heaviest CPU scenarios.
- Lower Autogen Density and Scenery Complexity. These settings increase the objects and draw calls that FSX must process. Reduce them until performance remains stable at your most demanding airports.
- Use a sustainable frame-rate target. Setting Target frame rate to a value the system can hold often produces steadier frame pacing than making the main thread chase an unlimited rate. Test both behaviours because aircraft and scenery combinations differ.
- Test complex add-ons separately. Detailed glass cockpits, gauge code, weather tools, traffic packages and large airports can each add CPU work. Disable one category at a time rather than blaming the whole installation.
- Prevent avoidable throttling. Use a Windows power mode that permits full processor performance, close unnecessary background workloads and check that cooling problems are not reducing clock speed.
Lowering resolution, antialiasing or texture filtering mainly helps when the graphics card is limiting performance. Our FSX CPU-versus-GPU bottleneck checks explain how to distinguish the two, while our broader FSX performance adjustments cover the remaining simulator settings.
Should I set AffinityMask in FSX.cfg?
Leave AffinityMask absent unless controlled testing shows that a specific mask improves your installation. Without it, FSX and Windows can schedule work across the available logical processors automatically.
The setting belongs under [JOBSCHEDULER] in FSX.cfg and uses a decimal bitmask to select logical processors. It does not create extra multithreading. A copied value intended for another CPU can exclude useful cores, crowd work onto simultaneous multithreading siblings, or cause worse frame pacing and slower scenery loading.
Before testing a mask, close FSX and back up FSX.cfg. Compare the same demanding flight with and without the entry, judging minimum frame rate, frame-time consistency and texture loading rather than the highest momentary FPS. Do not disable Hyper-Threading or SMT globally, or assign Realtime process priority, without repeatable evidence of a benefit.
How can I tell whether one CPU core is the bottleneck?
A main-thread bottleneck is likely when frame rate falls at detailed airports or with heavy AI traffic, one or more logical-processor graphs approach full use, and reducing resolution produces little improvement. Lowering AI or autogen should help more noticeably than changing graphics resolution.
Remember that Task Manager's overall percentage is averaged across every logical processor. On a processor with many cores, FSX can be CPU-limited while the total figure still looks surprisingly low.
Will more cores, a faster CPU or an SSD help FSX?
For FSX, stronger per-core performance and sustained clock speed usually matter more than adding many extra cores. Extra cores remain useful for Windows and external add-on processes, but they do not remove the simulator's main-thread limit.
When choosing hardware, compare modern single-thread performance rather than core count or advertised frequency alone; our FSX processor and graphics-card guidance explains the balance. An SSD improves start-up, flight loading and texture-read responsiveness, but it rarely raises CPU-limited frame rates, as covered in our FSX SSD-versus-HDD advice.