I've just checked the default processor affinity on my system for P3D without any tweaking and, by default, it uses all cores
![Dunno :dunno:](./images/smilies/102.gif)
Moderators: Guru's, The Ministry
Did you read his second post in the second link that I gave you? He says that P3D is optimised to use every other core (i.e. one thread of two on each core) as using every core is inefficient so what they are trying to achieve is no threads on core one, reserving it for the OS, and one thread each on cores two, three and four. That's what they're trying to achieve. If you read it through it might make more sense to you.TSR2 wrote:I've just checked the default processor affinity on my system for P3D without any tweaking and, by default, it uses all cores
I wouldn't have posted it if I thought it was idle conjecture (oh, alright, I might have doneBen wrote:Its also worth mentioning that depending on which post you read on which forum, FSX / P3D can only use physical cores so the hyper threaded ones don't count (I don't have any HT ones )
And to prove it, here's my CPU resource manager showing hyperthreading being used in P3D with the affinity mask set to 84. (I'm back home nowZach Heylmun, Prepar3d Software Engineer wrote:Prepar3d 2.0 is targeted at improving performance. We are working to take better advantage of multi-core processors by threading off more of the computation to background threads. That being said, prepar3d 1.3 is actually able to use hyperthreading today. By default, Prepar3d will usually only use every other core on a hyperthreaded processor ( i.e. one thread per physical core ). This is the desired behavior because most of the tasks offloaded to background threads are related to I/O, and hyperthreading does not perform well when both threads are waiting on I/O tasks.