February 5, 201214 yr Installed sp1 and sp2, and the sim was running on all 4 cores (2500k) all on it's own. Yesterday I noticed lower framerate, some stutters and sub-par graphics and happend to take a look at the affinity setting and sure enough only core 0 was in use. So now I'm having to manually set affinity every session.I deleted the fsx.cfg and let FSX create a new one but that didn't fix it.Addons installed and tweaks just before the issue began were:EZDok (EZCA)Realair dukethe online.cfg tuning tool by Bojote Bud Estrada
February 5, 201214 yr the .cfg tuning tool has probably added an affinity mask setting to your fsx.cfg.Open the cfg file and check in the section headed 'Task Scheduler'It sounds like the wrong affininty mask number has been added. Glenn Ryzen 3700X, X570 Pro Wifi, 32GB 3600mhz RAM, Nvidia Titan Xp "Galactic Empire", RM750x PSU, H700 case, 2x NVMe M2 SSD, 1x SATA SSD
February 5, 201214 yr I use the desktop gadget that tells how much each core processor is being used and each core temperature.It can be resized larger or smaller.http://www.alcpu.com/CoreTemp/ 5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.
February 7, 201214 yr Author Update:success -for some reason even after recreating a fresh .cfg the sim was running on a single core. Deleted/created yet another .cfg , then ran the tuning tool again (I left out the JobScheduler tweak for now) and I couldn't believe my eyes when I loaded up the sim and flew the RA Duke 60 around theTucson AZ area. Now running properly on all cores, smooth as glass. FPS locked and steady at 30 (external limiter).The difference this time ( I think ) was I rebooted he pc at some point between deleting the fsx.cfg and running the sim with the newly created tuned cfg. I just don't remember exactly when I rebooted during the process. the .cfg tuning tool has probably added an affinity mask setting to your fsx.cfg.Open the cfg file and check in the section headed 'Task Scheduler'It sounds like the wrong affininty mask number has been added.No it was running fine on cores 1,2,3 with affinitymask=14, as set by the tuning tool. I later removed the job scheduler entry to go back to running on 4 cores, and that's when the sim reverted to running like pre-SP1 on a single core, unless I manually set affinity.But I'm very happy that's resolved! Edited February 7, 201214 yr by bud7h7 Bud Estrada
Create an account or sign in to comment