On a Quad core, AffinityMask=15 is effectively the default.

 

So much false information around here. The default since Prepar3d v2.3 is all cores are being used. On a quad core with HT=on the default AM is 255. On a quad core with HT=off the default AM is 15. Jay explained in one of the previous posts that the myth around leaving core 0 free for Windows is just useless as Windows is optimized to spread load across different cores. But again: Why not stop the AM discussion and focus on OPTIMIZE_PARTS?

We are not talking about a myth about core zero left for other processes - give it up! The AM in HT=On is not so much a "tweak" rather than it is an essential step to take to allow the main P3D thread to keep a core to itself. It's not something I thought of on the loo, it's a fact. BTW 255=0 on a 4core 8LP CPU.

Definitely seeing improvement in my p3d. If we are going off of fps counter, I increased by roughly 20%. But more importantly, so smooth in the ngx. Thank you!

Great find.

 

The LM explanation doesn't really define "model". I have the exterior model of the PMDG 777 deactivated in the model.cfg due to VAS (+400 MB) but I still see a huge increase in FPS when flying the 777 (ca. +8 to 10 FPS) in the VC.

 

Completed a flight in the Aerosoft Airbus without any issues and also had increased FPS with this tweak (+3 to 4 on average I'd say).

Couldn't detect any downside so far.

I must admit I was a skeptic. I have version 2.5 with no add-ons other than PMDG 737NGX. At Honolulu with sliders maxed out I went from 24 to 29-31 FPS. Everything smooth as can be. Made a believer out of me.

Really sorry to bring up AffinityMask again, but on my 2500K there is absolutely no question that the sim performs better without any AM setting (which, I reckon would be the same as AM=15) than with AM=14.

 

I tend to fly mostly low and fast, and with AM=14 textures just don't get processed as quickly and reliably.

 

This is different from what I observe in FSX-MS, here AM=14 is more advantageous, at least on my system.

 

To me it seems like P3D is better at hogging core 0 than FSX is, and/or maybe able to better utilize more than two additional cores.

 

PS: OPTIMIZE_PARTS=1 rocks! Thanks!

Tested the OP=1 and noticed a +10 FPS increase in NGX (from 35 to 45) but the ground textures tend to become blurred.

Haven't noticed anything more blurry than usual. I always get blurry ground textures when changing views. Think it has to do with the tower view

I have i7 4790k without OC, Which the best Affinity mask for the processor? 

So much false information around here. [...] On a quad core with HT=off the default AM is 15.

 

Which is exactly what I said.

I was replying directly to the post I quoted. He mentioned not having HT on so I didn't think I had to specify HT on or off. Nevertheless, I've edited my post to specify HT off for those who don't read the full post

Which apparently means PMDG didn't optimize things... Everyone is saying it's a great tweak for PMDG planes while everyone should be saying PMDG missed something here. It's a tweak you shouldn't really need.

Your quite correct. I found that with the PMDG planes the most benifit was gained from this tweak. This was when I didn't know what it did.

 

Hopefully, I feel a hotfix coming out to fix this issue from certain developers. We shall see!

Guys,

We'll need further guidance from LM on this if there's something that needs fixing - our models most certainly are optimized to reduce draw calls and our P3D models are not just the FSX ones thrown into the P3D folder - they were adjusted and exported using the P3D specific tools provided in the P3D SDK. If there's something LM's realtime optimizer is doing that we don't know about then they will need to make that information public so that we (and other devs) know about it.

Ya'll are tempting me to make the switch.  But my FSX looks sooo good with DX10, ORBX and O/C at 4.8.  Plus, I probably have a gazillion add-ons that won't work in P3D.  Anyhow, congrats on the new discovery.  I'm excited for you, and maybe me fairly soon.

Guys,

 

We'll need further guidance from LM on this if there's something that needs fixing - our models most certainly are optimized to reduce draw calls and our P3D models are not just the FSX ones thrown into the P3D folder - they were adjusted and exported using the P3D specific tools provided in the P3D SDK. If there's something LM's realtime optimizer is doing that we don't know about then they will need to make that information public so that we (and other devs) know about it.

Agreed. Up until recently knowone was aware of this. We don't even know if it's a 'feature' that is here to stay. we dont formaly even know what it actually does. We do know it has an effect though, hence my comment regarding a hotfix. If it implied that someone had done something wrong or missed something that was not my intention. A hotfix is issued to make things better.

Guys,

 

We'll need further guidance from LM on this if there's something that needs fixing - our models most certainly are optimized to reduce draw calls and our P3D models are not just the FSX ones thrown into the P3D folder - they were adjusted and exported using the P3D specific tools provided in the P3D SDK. If there's something LM's realtime optimizer is doing that we don't know about then they will need to make that information public so that we (and other devs) know about it.

 

I'm not sure this has anything to do with PMDG as this Optimize tweak works with factor F-22 also - one would assume that model is optimized so may be chasing something that doesn't need chasing - anyway you look at it changing a 0 to a 1 is a lot easier than PMDG doing a lot of work for no gain