I have AffinityMask=14 entered in my FSX.cfg. I thought that would make the quad disbursement to be 1,2,3 for FSX and 0 for the rest of the applications. However, when I run FSX, I see all cores are assigned to FSX. I have to change the affinity manually.Is there anything else I should do to have FSX boot up with the correct affinity?Thanks.Abe

>I have AffinityMask=14 entered in my FSX.cfg. I thought that>would make the quad disbursement to be 1,2,3 for FSX and 0 for>the rest of the applications. However, when I run FSX, I see>all cores are assigned to FSX. I have to change the affinity>manually.>>Is there anything else I should do to have FSX boot up with>the correct affinity?>>Thanks.>>AbeThe affinityMask only effects the cores used for scenery loading! The core APP is still running on Core 0 unless you set that in the task manager!

Not on my system... Core 1 is running at 100% and core 0 is pretty much idling. {JOBSCHEDULER} ........ square brackets !AffinityMask=14

on a dual core, using a quad core affinity mask setting does not make sense. the range of values for a dual core isn num of cores scheduled bitmask1 = 1 core 0001 core 0 only3 = 2 cores 0011 core 0 and core 1if you were trying to restrict jobs to core 1 in a core-0, core-1 system, then 0010 would be the proper mask, eg 2. schedule on core 1 only.what happens if you remove 14 on a dual core? or use a proper setting for 2 cores?

Sorry Phil,Should have been more specific. This is on a Q6600 and FSX performance is very good with this setting. No complaints :-)

I use a program called "SeeSaw Pro" to set all running processes to core 0 prior to starting FSX.Once I start FSX I set it to run on cores 1-3.Unlike the Task Manager, this utility will set the affinity of ANY process. Taks Manager won't let you change the system tasks.I see core 1 running around 25-50% in flight and cores 2-3 sittingat from 5-25% . They peak out at 100% during the initial scenery loading. Paul

That really surprises me... my experience has been that the main FSX process will use 100% of whatever processor it runs on.Are you sure that you are not looking at "total CPU"?

When you say all cores are assigned to FSX, do you mean that if you go to set affinity using windows task manage it still shows CPU0 as selected or do you have some other measure that FSX is using core 0 (eg. core 0 is pegged at 100%)? If the former, that's how it is supposed to be. Basically, with AffinityMask set to 14 with FSX running and no addons running you should be seeing minimal (<15%) activity on core 0, core 1 pegged at 100% and cores 2 and 3 running anywhere from 25-100%.Gary

>That really surprises me... my experience has been that the>main FSX process will use 100% of whatever processor it runs>on.>>Are you sure that you are not looking at "total CPU"? I'm looking at each of the cores plots in the Task Manager performance window. Paul

>Not on my system... Core 1 is running at 100% and core 0 is>pretty much idling. >>{JOBSCHEDULER} ........ square brackets !>AffinityMask=14Hi Bert,Can you tell me where the {JOBSCHEDULER} entry is, I have looked up and down on my FSX cfg and can't find it anywhere. Is this a new 'Tweak' post SP1 & Accl SP2?

>Can you tell me where the {JOBSCHEDULER} entry is, I have>looked up and down on my FSX cfg and can't find it anywhere.>Is this a new 'Tweak' post SP1 & Accl SP2?>It is a new entry and according to the tweaks at http://www.highflightsimulations.com/fsxcfg.html most of which I have implemented and now have a stable locked FPS of 30 with no stutters, for a Quad Core Affinity Mask should be 15 not 14.

>>>Can you tell me where the {JOBSCHEDULER} entry is, I have>>looked up and down on my FSX cfg and can't find it anywhere.>>Is this a new 'Tweak' post SP1 & Accl SP2?>>>It is a new entry and according to the tweaks at>http://www.highflightsimulations.com/fsxcfg.html most of which>I have implemented and now have a stable locked FPS of 30 with>no stutters, for a Quad Core Affinity Mask should be 15 not>14.>Wonderful stuff Bill,Will go and make the necessary adjustments to my cfg file.I suspect these items were omitted from SP2 due to time factors.

You have to add this section.As to 14 vs 15, that depends on which cores you want to do what...I use 14 to keep core 0 free for background tasks, windows housekeeping and such.