You should also see more stable performance over the course of a flight. Giving the primary core a little breathing room made a huge difference in my experience, just as with FSX.

I am glad to read that you have sorted the issue, and I apologize for my lack of patience earlier in this thread,

 

AM 14 (or 84) absolutely is a night/day difference versus no setting at all. With no AM set, P3D2 uses the correct cores, but appears to do next to no load balancing across them. This results in the primary core sitting at 99% and choking the system a bit.

 

Setting an AM fixes this.

 

 

Very strange... So technically AM=14 is doing the same thing as default but in practice it's actually doing something completely different operationally?

Pretty much yeah.

 

By default the primary core chokes to death. This effects of this were especially apparent, for me at least, over time. It is using the correct cores mind you, but the primary is just saturated.

 

With an AM of 14 or 84 (no HT vs HT) Core 0 does become primary for whatever reason, but, load balancing across physical cores is much better.

I just finished a KPDX - CYEG flight (ORBX Regions) using the shadow tweaks (the one with higher numbers) and did not encounter blurries... So far I really cant complain about P3DV2, I only wished the NGX would work, I tried installing it using the migration tool but a few things are not working (auto throttles, PFD TCAS RA alerts, etc)

John.