Thanks mate.

Changed config to this and see zero difference to the way it was before.

Looked at task manager and 4 threads are definitely being utilised the other 4 much less so if at all. I don't know much about hyperthreading so this might be normal.

Think I'll put it back the way it was in that case.

One can always be hopeful of discovering something that will make a massive game changing improvement :p

its a binary system, so keep in mind that;

Core 0 (1st core) = binary 1
Core 1 (2nd core) = binary 2
Core 2 (3rd core) = binary 4
Core 3 (4th core) = binary 8
Core 4 (5th core) = binary 16
Core 5 (6th core) = binary 32


so basically you have a software dipswitch setting, so if you wanted to run your sim on all cores available, you would add up all the binary associated with those cores.

So to have your ProcessAffinityMask setting to use all four cores, you would addup the binary for cores 0 through 3, which is 1 + 2 + 4 + 8 equaling 15.

For all six cores (0 through 5) you would have 1 + 2 + 4 + 8 + 16 + 32 = 63.

Some say a four core processor is best when Core 0 is left for the Operating System and run the sim on Cores 1, 2 and 3 only, this would involve adding binary 2 + 4 + 8 eaqualing 14.

If the user wanted to run the sim on core 3 (4th Core) only, the PAM setting would be 8

Having said all that, it appears that the ProcessAffinityMask line has been removed from the latest Config file, which is fine because (at least on my machine and according to some others) the sim runs much better without the setting because the sim is utilising cores much better than it did when the sim was frst released.

I checked mine and found that it had been set to '14' after the last update. Disabling it or setting it to '15' seems to have no apparent effect on either performance or core-loading though.

I've just noticed and maybe someone could confirm [when game running: Task Manager/ Services Tab/ game.exe/ Set Affinity], the PAM process appears to see the (with hyperthreading enabled) virtual cores as real cores.
eg a 6 core (with HT enabled) presents as a 12 core, so I'm assuming a 4 core (with HT enabled) presents as an 8 core


Core 0 (1st core) = binary 1
Core 1 (2nd core) = binary 2
Core 2 (3rd core) = binary 4
Core 3 (4th core) = binary 8
Core 4 (5th core) = binary 16
Core 5 (6th core) = binary 32

Core 6 (7th core) = binary 64
Core 7 (8th core) = binary 128
Core 8 (9th core) = binary 256
Core 9 (10th core) = binary 512
Core 10 (11th core) = binary 1024
Core 11 (12th core) = binary 2048



@ TonyD...

are you running a fresh config file? ie the ones contained in the 1CSoftClub folder, located in the (Windows7) Documents folder of the desktop

Hi How do you go about getting a fresh config file ? Cheers

Delete the files in the 1cSoftClub folder and let the sim re-write them...

possibly may have to delete the same files in the Steam game folder, then do a Steam File Integrity Check and then let the sim re-write the deleted files in the softclub folder

Do not forget to save your controls settings (and info-windows positions if you wish too) in a separate file before deleting all config files or you would have to assign controls again.

I understood that one of the changes in the last update was to ‘refresh’ the config file when the update was applied. I have never changed it, apart from trying the PAM setting previously and setting it back to disabled on completion. I assumed that the update had resulted in this being generated with its current setting of 14.

Thanks for the explanation of the binary values, by the way – the numbers used now make sense.

Thanks guys- all done and its all going great :grin: