System is i7920 @3.8ghz win7making a flight from cyul to keug and noticed unsual stutters, normally my system is very smooth, and sliders are genrally about 60%.The stutters only come on this route , and the route got some heavy weather.So i changed ASA to run only on core 0 and chnaged its priority to lowest, and all was well.All other addons like rc4/asa/fscommander/plang are also set to run on core 0 only with lowest priority.But recently i changed asa to med priority on core 0, and that how it was when i got stutters on this route stutters related to heavy weather i think. But changing asa to lowest priority on core o fixed the stutters.FSX itself is set to affinity = 14 = 1110 so logic being fsx uses top three cores while all addons are set to core 0 lowest priority.by the way fsx is set to high priority.i use prifinitty2 free tool to do all priority and affinity setting, fsx affinity is only set in fsx.cfg . but fsx priority is set in prifinitty to high.The stuff really fixed the asa stutters in heavy weather. google prifinitty2 for free download.

You can raise FSX's priority in the Task Manager (be carefule though). I would suggest an affinitymask of 3 for two cores.

You can raise FSX's priority in the Task Manager (be carefule though). I would suggest an affinitymask of 3 for two cores.

You can change affinity and priority in task maneger. thing is the setting is not retained when you reboot.With prifinitty2 what you set is there forever till you change it, inside prifinitty2.I have tried fsx in all core combinations and 14 = 1110 works best on my system. giving fsx only 2 cores 0011 is not enough juice for the power hungary fsx.this is what i meanthe right side of the box is where all the programs that i have set special affinity or priority for.the left side of the box is just current running programs and thier priority and affinity

Hi All,Run ASA on the highest core, normal priority, and see what happens.

Hi All,Run ASA on the highest core, normal priority, and see what happens.

FSX is running on core 123 and addons on core 0.I suspect if asa runs on core 3 - it will make fsx stutter, since fsx uses that core.From all my tests fsx is smothest on core 123.What i got now is really smooth even with heavy weather, as long as ASA is on core 0 low priority.

FSX is running on core 123 and addons on core 0.I suspect if asa runs on core 3 - it will make fsx stutter, since fsx uses that core.From all my tests fsx is smothest on core 123.What i got now is really smooth even with heavy weather, as long as ASA is on core 0 low priority.

I get chronic stutters with weather added.Might any of those changes make a difference with my dual core chip? (E6850 @ 3.8Ghz)

I run ASA on high priority (option checked in ASA), Affinitymask=14, on stutters.. I always wondered what's the point with priority in ASA.. weather updates every, let's say 15 minutes, what's the point of pritority than? If this works for you, great man!

System is i7920 @3.8ghz win7making a flight from cyul to keug and noticed unsual stutters, normally my system is very smooth, and sliders are genrally about 60%.The stutters only come on this route , and the route got some heavy weather.

Could the stutters (in part) be due to the weather that is added rather than the addon per se?

Could the stutters (in part) be due to the weather that is added rather than the addon per se?

ASA works perfect, but in heavy weather my normally smooth system stutters sometimes.On this occasion i tried something and the the result was immediate success.I had tried same flight about 3 times before and stuttered everytime, but i lived with it.on the last occasion, i was determined to fix the stutter and it worked.It does not matter what system you using dual or quad core, the result of the experiment i performed is simply this. Its best to put addons on lowest priority and running from a sinlge core. Ofcourse this only applies o addons running on same PC as fsx.On dual core ill just assign ASA to core 1 and let fsx use core 0 and 1. And set ASA and all addons to priority lowest.As for the give ASA high priority option in ASA menu, i never use that stuff, seems likely to cause more stutters in fsx.Of all the programs involved in the sim FSX is the only one youll notice if its not running smoothly, so makes sense to give everything else lowest priority, and let them stutter away in the background, while fsx is smooth.if you look at the picture of priaffinity i added youll see on right side that all my addons are on core 0 only and set to run on lowest priority. while fsx is set to high priority.

I get chronic stutters with weather added.Might any of those changes make a difference with my dual core chip? (E6850 @ 3.8Ghz)

On dual core i would suggest you download priaffinity and set all addons to lowest priority . And let them use only core 1. While fsx on core 0 and 1.I would also recomend Gamebooster for shutdown uneeded windows services.You can also set other stuff running on yourt pc to low priority on restricted core but better google to findout what the task does before you mess with it, if you look at my pic above youll see some windows programs i left as they were on core 0123 and priority normal. I recomend only messing with priority and affinity of fsx addons only , and things you know well and often use while simming like adobe and explorer, excel etc.

I guess I need to ask: why would anyone purposely add "stuff" to the core that we know FSX uses the most? FSX "mostly" uses core zero and I know the other cores are somewhat used. Why wouldn't you instead assign the "stuff" to run on your highest core to allow FSX as much as core zero as possible?

I guess I need to ask: why would anyone purposely add "stuff" to the core that we know FSX uses the most? FSX "mostly" uses core zero and I know the other cores are somewhat used. Why wouldn't you instead assign the "stuff" to run on your highest core to allow FSX as much as core zero as possible?

Jim,If he indeed is using FSX with the Affintiy Mask set to 14, FSX is running on cores 1,2 and 3 with core 1 being the primary core FSX. This leaves core 0 free for the OS and anything else which you choose to run on core 0. Which BTW works very well. The OPs screnshots are somewhat misleading because they perceive to show FSX running on all four cores.I run with the Affinty Mask set to 14 on my system because FSX just runs smoother. I also use Air Hauler which hits resources pretty hard. I now run Air Hauler on core 0 which limits its effects on FSX substantially.Regards,Bob

Hi,Thanks!I will also post this from Nick from Dec 15 2007:I can tell you that if you need to set an affinity mask which inhibits core0 from being used by FSX, or shift all threads to core2 and core3, that means the program and the OS background activity are overtaxing your system. All the reports you see of people setting different affinity masks and getting results have no linear bearing on anything. Even if you have 2 identical systems hardware wise and FSX settings wise, if person A does not have Windows and their drives optimized for performance, and person B does, the affinity mask setting will produce different results. The benchmarks with conclusions that suggest setting an affinity mask that directs FSX to only use certain cores are flawed, and, only relative to the person who ran/runs the benchmark. Their system and how it is optimized along with driver revisions and disk optimization method will skew the results in one direction. My advice is if you have a dual or single core, leave it out of the config file and if you have a quad or dual quad, assign the affinity mask which uses all cores. [/size [font=Times New Roman]If you notice stutters you can try setting core0 to be ignored by FSX, however, be advised if that has a positive affect and removes the stutters then you are either not system optimized properly, or, your FSX settings are too high for the hardware installed, its as simple as that.[/font] The reason Aces gave us that setting was:

• [*]To ensure all processors, old new and next generation, would be correctly addressed by FSX and if in the future FSX was not properly recognizing a new CPU, we could manually set the affinity, easily eliminating the issue ourselves.
  • [*]A method of quickly allowing the load to be manipulated in case the primary core was being taxed by Windows and background operations. Since most end users are not computer techs and do not know how to set up a computer, how to select the right security software and how to make sure their drive system is properly maintained, the setting allows a method of shifting the load without needing a degree in computer science. As for affinity mask, the following is how that works and is set by converting BINARY to DECIMAL [JOBSCHEDULER] AffinityMask=x EXAMPLES: 1 core (or for single core hyperthread processors) =1 2 cores = 3 3 cores = 7 4 cores = 15 Decimal Binary 1 = 1 core 0001 3 = 2 cores 0011 7 = 3 cores 0111 15= 4 cores 1111 Do you see how it works? Each 1 in the BINARY list represents an active core in use by FSX. Also, it’s backwards from counting the cores right to left so core #1 is the last BINARY digit, not the first. Each 1 represents a core being enabled and each zero represents a core not in use. If you wanted to use 3 cores on a quad and let the system have the first one for any background activity, set to: 1110 <---- core 1 is off (0) Using a binary to decimal converter/calculator (available on the web too) that would convert to a Affinity Mask of =14 Turning off the first core to FSX has had value to some and not work well for others. I do not run that way. Soon there will be Single Wafer Dual Quad cores on the market. For 8 cores, binary to FSX would be 11111111 (8 one’s) which is a decimal affinity mask of =255

Each 1 represents a core being enabled and each zero represents a core not in use. If you wanted to use 3 cores on a quad and let the system have the first one for any background activity, set to: 1110 <---- core 1 is off (0)Using a binary to decimal converter/calculator (available on the web too) that would convert to a Affinity Mask of =14 Turning off the first core to FSX has had value to some and not work well for others. I do not run that way.

Just as Nick said....................Turning off the first core works for some (actually alot). He does not run that way. However, many do. The thought being that FSX and the OS are now both not sharing core 0 and FSX can have its own dedicated core to run on. I can also assure you I have no background activity at all on my FSX PC as it is the ONLY thing it is used and specifically configured for. Who knows why it works for some and not for others. FSX seems to be a never ending learning experience.

Just as Nick said....................Turning off the first core works for some (actually alot). He does not run that way. However, many do. The thought being that FSX and the OS are now both not sharing core 0 and FSX can have its own dedicated core to run on. I can also assure you I have no background activity at all on my FSX PC as it is the ONLY thing it is used and specifically configured for. Who knows why it works for some and not for others. FSX seems to be a never ending learning experience.

Interesting discussion!Forgive my ignorance, but surely the OS itself will not be limited to core 0?What's stopping Windows from using the other cores if it so fancies?I thought at least WinXP Pro/Windows Vista/Seven would make full use of multi-core processors?CheersDavid