May 3, 20179 yr Using the windows task manager to set affinity is very different from using the affinity mask in fsx.cfg. With the fsx.cfg mask, fsx is told what cores it can use to run its threads, and it will specifically assign threads to the cores identified by the AM. Whereas when the task manager assigns a process an AM, it tosses out the application's core assignments, and schedules all of the process threads to run on any core that is in the mask with the intent to load balance the threads over all of the AM cores. This is why it appears that using the Windows TM AM gives a "better" uses of the cores. But in reality this is really a bad idea for FSX since it carefully orchestrates the execution of its threads to avoid data clashes and race conditions. When windows tosses this orderly procession of threads into a single big "free for all", those data clashes and race conditions will certainly happen, resulting in chaotic performance. As far as fsx.cfg AM usage, I don't bother. With my setup, I use cmd scripts to launch apps, such as AS16 and TrackIR, with AM masks that force them off core 0. IMO this works very well, but of course YMMV. CPU: AMD 9800X3D PBO MB +200 CO -25| Motherboard: MSI MAG X870e Tomahawk WiFi | GPU: MSI RTX 5090 Ventus 3X OC | RAM: G.Skill 2x32GB DDR5 6000 cas 30 | M.2 SSDs: Samsung 990 EVO Plus 2T, WD Black SN750 M.2 1T | Hard Drive: WD Black HDD 6T 7200 | Optical Drive: LG Bluray writer, internal | Cooling: Thermalright Phantom Spirit 120 EVO | Case: Fractal Design Focus G | PSU: NZXT C1200 1200W Win 11 Pro 64|HP Reverb G2 revised VR HMD|Asus 25" IPS 2K 60Hz monitor|Saitek X52 Pro & Peddles|TIR 5 (now retired)
Archived
This topic is now archived and is closed to further replies.