The EVGA software won't work with my ASUS GTX 780.... the frame rates remain unlocked despite settings to the contrary in EVGA Precision. Also on my system (i7-4770 OC'd at 4.5Ghz, HT on) the AffinityMask settings make no measurable difference in performance. I used values of 84, 252, and 254 to no avail. All of these values were no better than not having the AffinityMask entry in my Prepar3D.cfg file. So much snake oil.....

 

For my system what works best is turning off cloud shadows in overcast or rainy/snowy weather and locking FPS within P3Dv2 at 20 fps. Even with almost all of my other display sliders maxed to the right, I can maintain a solid 20fps and smooth flight in bad weather with lots of clouds and precip. If the weather is nice, I flip on cloud shadows and all is well.

 

Scott

Actually Scott, the AM=84 setting is for running in HT on a 4 core CPU.  It drives P3D as though you were NOT in HT, but then, with the added benefit that the other 4 virtual cores gives for system-wide head-room.  P3D will run on the same core strategy, as if not running in HT mode..and will basically ignore the virtual cores, so they may be used as your system call-demand sees fit. If you use the other numerals that you posted you had tried, it forces P3D to run on virtual cores as well...and that does not mean it will run any better, or disperse the texture work load as some people think.  Those virtual cores are software call routines..and NOT true hardware registers.  They don't generate primary computations, but run as a slave mode to the 4 true hardware cores and their sub-logic on the down cycle of one clock interval. That is why my using AM=84 is giving me such great performance.  The actual hardware registers (cores) are being used to drive P3D...and the virtual 'cores' render/compute on the off cycle of the hardware cores.  That is what H.T. is...it does not magically double a CPU's core count, but through software-ROM dictates, simulates double the core count. That is an important distinction. HT allows you the use of the up and downside of a clock-cycle, where not running in HT mode of the CPU, will generate on the up cycle and 'rest' on the down side. It is for that reason that in HT mode, you generate more heat out of the CPU...but...but...'good heat'...in that you have maximized every precious performance 'drop' out of the old girl.  To not run in HT mode on a CPU that is so equipped, to my way of thinking, is a serious waste of core engineering....despite that some won't, to try and squeeze an extra percentage point in an overclock scenario.

I concure that AM=84 or 85 is pretty good. I'm running an AMD FX8350 with HT on, but only using the physical cores with AffinityMask set to 84 or 85. From what I've noticed this has given me the best FPS results and stability. When running with using logical cores with the physical ones, I found that the game crashed more often. AM=84/85 is the way to go for anyone running an AMD 8-core CPU.

My testing and P3D performance also concurs!  AM=84 is now also sitting in my FSX .cfg

 

Mitch

I've almost decided to reinstall P3Dv2 (again) due to stutters. But this EVGA tool got me a little interested. Think I'm gonna try that on my GTX780 and see if it can help out. I really don't care much about FPS anymore, those are easy to manage by adjusting eye-candy. And blurries are effectively killed with the AffinityMask tweak.

 

The only real remaining enemy of my hobby is stutters. 

I've almost decided to reinstall P3Dv2 (again) due to stutters. But this EVGA tool got me a little interested. Think I'm gonna try that on my GTX780 and see if it can help out. I really don't care much about FPS anymore, those are easy to manage by adjusting eye-candy. And blurries are effectively killed with the AffinityMask tweak.

 

The only real remaining enemy of my hobby is stutters.

 

 

Try adaptive VSync in Nvidia Control panel And limited fps in NI AT 58 FPS. WORKS GREAT with a 60HZ monitor on my system. All the way down to 20-22fps with very low if not complete stutter free.

 

 

EDIT Testet with EVGA GTX780SC

Michael

Try adaptive VSync in Nvidia Control panel And limited fps in NI AT 58 FPS. WORKS GREAT with a 60HZ monitor on my system. All the way down to 20-22fps with very low if not complete stutter free.

 

Thx, I've read about this solution in the forums here lately. I've tried the adaptive VSync setting and it didn't improve the stutters for me. Makes me wonder if I'm doing something wrong or leaving some detail/setting out. I don't use NI at all, as I'm only flying P3Dv2 now and I'm not sure it's needed anymore.

 

It seems this adaptive VSync has helped alot of fellow simmers with stuttering. Just not me, so far.

 

 

Actually Scott, the AM=84 setting is for running in HT on a 4 core CPU.  It drives P3D as though you were NOT in HT, but then, with the added benefit that the other 4 virtual cores gives for system-wide head-room.  P3D will run on the same core strategy, as if not running in HT mode..and will basically ignore the virtual cores, so they may be used as your system call-demand sees fit. If you use the other numerals that you posted you had tried, it forces P3D to run on virtual cores as well...and that does not mean it will run any better, or disperse the texture work load as some people think.  Those virtual cores are software call routines..and NOT true hardware registers.  They don't generate primary computations, but run as a slave mode to the 4 true hardware cores and their sub-logic on the down cycle of one clock interval. That is why my using AM=84 is giving me such great performance.  The actual hardware registers (cores) are being used to drive P3D...and the virtual 'cores' render/compute on the off cycle of the hardware cores.  That is what H.T. is...it does not magically double a CPU's core count, but through software-ROM dictates, simulates double the core count. That is an important distinction. HT allows you the use of the up and downside of a clock-cycle, where not running in HT mode of the CPU, will generate on the up cycle and 'rest' on the down side. It is for that reason that in HT mode, you generate more heat out of the CPU...but...but...'good heat'...in that you have maximized every precious performance 'drop' out of the old girl.  To not run in HT mode on a CPU that is so equipped, to my way of thinking, is a serious waste of core engineering....despite that some won't, to try and squeeze an extra percentage point in an overclock scenario.

 

Thanks Mitch - that's a very helpful explanation.  I wish that I could get the EVGA software working with my ASUS GTX 780.  Meanwhile I'll try AM=84 again.

 

Scott

Actually Scott, the AM=84 setting is for running in HT on a 4 core CPU.  It drives P3D as though you were NOT in HT, but then, with the added benefit that the other 4 virtual cores gives for system-wide head-room.  P3D will run on the same core strategy, as if not running in HT mode..and will basically ignore the virtual cores, so they may be used as your system call-demand sees fit. If you use the other numerals that you posted you had tried, it forces P3D to run on virtual cores as well...and that does not mean it will run any better, or disperse the texture work load as some people think.  Those virtual cores are software call routines..and NOT true hardware registers.  They don't generate primary computations, but run as a slave mode to the 4 true hardware cores and their sub-logic on the down cycle of one clock interval. That is why my using AM=84 is giving me such great performance.  The actual hardware registers (cores) are being used to drive P3D...and the virtual 'cores' render/compute on the off cycle of the hardware cores.  That is what H.T. is...it does not magically double a CPU's core count, but through software-ROM dictates, simulates double the core count. That is an important distinction. HT allows you the use of the up and downside of a clock-cycle, where not running in HT mode of the CPU, will generate on the up cycle and 'rest' on the down side. It is for that reason that in HT mode, you generate more heat out of the CPU...but...but...'good heat'...in that you have maximized every precious performance 'drop' out of the old girl.  To not run in HT mode on a CPU that is so equipped, to my way of thinking, is a serious waste of core engineering....despite that some won't, to try and squeeze an extra percentage point in an overclock scenario.

My testing and P3D performance also concurs!  AM=84 is now also sitting in my FSX .cfg

 

Mitch

 

 

I concure that AM=84 or 85 is pretty good. I'm running an AMD FX8350 with HT on, but only using the physical cores with AffinityMask set to 84 or 85. From what I've noticed this has given me the best FPS results and stability. When running with using logical cores with the physical ones, I found that the game crashed more often. AM=84/85 is the way to go for anyone running an AMD 8-core CPU.

 

I was using AM=15, then went to AM=84, but then, back in April I read what Beau wrote, and I've been using AM=242 ever since, which gives me the best overall results of any AM I've tried.  I've posted this several times before, but I'm not sure you guys have seen it yet:

 

Quote from Beau on April 24, 2014, 08:24

A few other observations we have made in our testing:

- For some processors core 0 is clocked a bit higher.  There isn't actually a dedicated windows core.  Windows and other windows applications may schedule work on any core at any time.  The OS does however try to load balance work, so if you leave a core open, it is much more likely to schedule work on that core.  I don't think it considers a core open unless both HT cores are open.  This is why masking off an entire core tends to help with stutters.  We haven't done a lot of testing to back this up, but some initial findings suggest that you can leave open whichever core you choose.  It might be better to use the first core and leave open a different core:

 

eg for a quad core with hyper threading try: 241/242 ( 11110001 / 11110010 ) or 61/62( 00111101 / 00111110 ).

 

We also noticed that the AMD Phenom processor doesn't like having any cores masked off as anything but using all cores caused odd stutters which seemed to be related to hardware and OS rather than simply having one less core to play with.

I concure that AM=84 or 85 is pretty good. I'm running an AMD FX8350 with HT on, but only using the physical cores with AffinityMask set to 84 or 85. From what I've noticed this has given me the best FPS results and stability. When running with using logical cores with the physical ones, I found that the game crashed more often. AM=84/85 is the way to go for anyone running an AMD 8-core CPU.

 

 

8350 has 8 physical cores. It is just that pairs of cores share resources so it isn't quite a real 8 core chip.

Thx, I've read about this solution in the forums here lately. I've tried the adaptive VSync setting and it didn't improve the stutters for me. Makes me wonder if I'm doing something wrong or leaving some detail/setting out. I don't use NI at all, as I'm only flying P3Dv2 now and I'm not sure it's needed anymore.

 

It seems this adaptive VSync has helped alot of fellow simmers with stuttering. Just not me, so far.

 

You should really try Nvidia Inspector and limit to 58 FPS. It makes a huge differents in both FSX and P3dv2 on my simular system. (337.88)

 

The limiter in PrecisionX can be set to 30 at the same time. Try it! (windowmode user)

 

Michael 

AM=84 resulted in a CTD for me! Back to the drawing board.

Thanks Mitch - that's a very helpful explanation.  I wish that I could get the EVGA software working with my ASUS GTX 780.  Meanwhile I'll try AM=84 again.

 

Scott

 

AM=84 resulted in a CTD for me! Back to the drawing board.

 

Oldar...any change you make in the .cfg file, normally needs also, ONE deletion of the SHADER folder, to rebuild as it parses the altered .cfg file on first run. So...try that.   Set your AM=84 again, and then DELETE your SHADER folder.  Fire up P3D, and you will see the Raptor on the runway...lol.  Do not take away, or add to your .cfg file...and all will be good.  If so though...merely, and always (in P3D, and not so much for FSX...) automatically do a SHADER folder deletion as part of your P3D 'Modus Operendi'.

 

Mitch

Mitch,

Is it necessary, or advisable, to back up the Shader folder before deleting it?

Thanks, Howard

Mitch,

Is it necessary, or advisable, to back up the Shader folder before deleting it?

Thanks, Howard

Howard, when you delete, just do not SHIFT-Delete Key...and all is well. It will 'delete' fail safe to your Trash Bin.  It will still be in there. Do not immediately delete your Trash Bin.  I recommend that you delete it (a current Shader Folder), and then fire up P3D right away, for a load cycle..which will immediately generate an 'in-house' SHADER FOLDER anew.  If you get to see the Raptor ready to burn rubber...then you can safely delete the Trash Bin contents.  That works for me.  You only need to delete, to let the Shader Folder rebuild, is if you alter anything in your P3D v2.2 .cfg file. It seems that unlike FSX, P3D 'assumes' that you have NOT changed anything anew...and runs with a Shader build that might rub against any new line additions or numerical changes within the .cfg file.  That has been my experience as to compare with FSX...

 

Mitch

Thanks a lot Mitch.

 

 

You should really try Nvidia Inspector and limit to 58 FPS. It makes a huge differents in both FSX and P3dv2 on my simular system. (337.88)
 
The limiter in PrecisionX can be set to 30 at the same time. Try it! (windowmode user)

 

While it didn't eliminate p3d stutters for me, it did seem to reduce them and did seem to work well in FSX as well.  I'm surprised.

Thanks a lot Mitch.

You are most welcome.  I am presently at FL190 having taken off 15 minutes ago from Phoenix's Sky Harbor, headed to KFNT (Flint-Bishop, Michigan)...and with ORBX-G, Vector 1.15, ASN.REX 4 Direct, all in play...what a most fantastically real, virtual world is below my 737-800.  This flight simulator, with the clouds even darkening my wings, (in left wing view), as I fly just under them... is utterly amazing. 

 

ORBX G has never looked so good. I saw the Superstition Mountains below the left wing on climb-out...and all I can say..is that I am absolutely hooked right through the mouth with this flight simulator. Once you have P3D dailed in....OMG!   OMG!   Back to the flight....the clouds via REX4 and ASN...over the desert...OMG!

 

Sheer simulation-aviation heaven....wow. Wow.

 

Post Edit:  Half way through my Flight Planner generated flight path.  I am popping 45-73 FPS, (unlimited within P3D, hardware 'FPS target' at driver level set to 30 via Precision X by EVGA)  today!  Razor sharp graphics, ever since leaving the runway at Phoenix Sky Harbor, Arizona  From Arizona to Michigan, ORBX G puts out quite diverse scenery...I highly recommend this flight:

 

KPHX-KFNT

 

Mitch