Hi Mitch.  I have to ask this question as I am always concerned installing something new that I am not familiar with.   Am I taking a big chance by  installing EVGA Precision X that I could damage my video card?    After installing, do I only make one adjustment, and that is to set the FPS?  Is it possible to monitor the cards temperature and what is the target?

 

Thank you very much,

Howard

Good morning, or I guess good evening, depending, huh?

----------------------------------------------------------------------------------------

 

To anybody that is now using the EVGA Precision X FPS Target Mode....make sure upon firing up the system, that the mode is in fact active.  If you don't press APPLY, it might not have taken as permanent, and also, make sure that Precision X software is also configured to load with Windows.  Just check the software as the first thing you do from the desktop, to see if the FPS Target Mode is active. Then fly away, on any platform, because it will be active for all...

 

Happy Flying....right now in XPX.30b3...but soon to land and take off in P3D!   Honestly, If some one would label me an enthusiast ...it would have to be with a reference to P3D, XPX,FSX, and still of course FS9.9    Yes...I would say that I am an enthusiast of 'em all!

 

I also suggest that you do not use Vsync at all, in P3D. I truly think that with Target Mode in play, and outboard of P3D, you will not have screen tearing, and get smooth animation, all the same. Just a suggestion.  I don't run with Vsync of any mode on...and it is FORCED OFF in N.I.  I have beautiful performance in P3D without its influence.

 

Mitch/Sesquashtoo

Hey Mitch-

 

Still does not work for me. Tried every conceivable combination and after about ten minutes, unlocks itself and goes back to pure unlimited. Same behavior as Inspector limiter which makes me wonder.

 

Anyway, I'm pretty good with AM=15, unlimited and adaptive Vsync so I can't complain.

I think I have a positive on this too.  I'm running 5760 with FSGlobal, Ultimate Terrain, and high res photoscenery.  I put this fix in, along with adaptive v-sync from another thread, deleted the shader cache.  It was OK, but had some microstutter.  But I've had it on pause all night, when I came back and unpaused, I'm seeing something amazing at this resolution.  I'm getting steady 35 fps with no microstutter.  I'm wondering what the pause did, but it's smooth as butter with these settings, AT 5760x1080 (3770k x 44ghz x EVGA GTX 780 ACX)  I'm not even overclocked at my highest stable, and have done none on the GPU yet.  Yes, Disneyland.

 

Actually, I run at AF=255.  It's the adaptive v-sync that is significant here. There is a little micostutter in one of these small town airports in the midwest, but not what I used to have.

I have been a critic of P3D v2x, so I want to say that I get a great improvement using the EVGA Precision X. I set it to 30 fps and that's exactly what I get when I am away from cities, sliders all the way to the right. It still drops down into the low 20's when I am near a large city, but the sim is much better now. I also want to agree that I can turn off vSync when I am running the Precision X program. There is no difference with it on or off. 

 

I am still experimenting with the affinitymask setting. I set it to 224 because that is what had been set in my fsx.cfg by some tuning utility. It seems to work, but I am going to try the various others that have been suggested.

I come here randomly to see if this hobby has moved out of 1995 yet and.. This thread just shows.. Nope.. We're still seeking out magic bullets, tweaks, and redundant debates about what edits do and don't work..  And in the end..  Nothing ever works.. Just another kink in the chain.. I'm so glad I abandoned this hobby a year ago...  Prepar3D was supposed to be the answer to it all and.. Well.. It's just more of the same in a different suit. 

 

The more things change

 

The more they stay the same

What's a good/optimal 6/12 core AF setting based upon peoples experiences?

Both theoretically and empirically 4094 is a dandy AF setting for P3D V2.2.  This is the decimal equivalent of 111111111110, leaving Core0 for OS and other apps you may be running which you can assign to Core0 such as REX4 by making the assignment thru task manager.   P3D will put the main thread on virtual Core1, and the 10 other virtual cores work as texture loaders.  In high demand environments you see this play out w/ utilities like ASUS Suite CPU freq sensor which will show up to 100% use in those high demand areas.  This is the theoretical side and is corroborated by higher temperatures (indicating more processing) as well as more rapid texture update rates and freedom from blurred textures (the empirical proof).  This has been the most meaningful basic configuration change I've had in many moons, and it's held up time after time.  Fortunately my SB-E over clocks at eh same level as pre HT enabled, now w/ the same voltage, however I've amped up the cooling now that the hot summer has commenced.  I think others have suggested there is no downside to running all cores, i.e. not masking any from P3D to exploit.  If you want to try this one, it would be 4095 w/ HT enabled on hexacore.

Guys, perhaps I am wrong but the latest Nvidia based cards ( 700 series + Titan ) have an automatically boost feature ( GPU Boost 2.0 ) that overclocks the card in GPU taxing situations.

The oc is only limited by the cards temperature.

 

To me it looks the EVGA software is doing exactly that but adds the possibility to lock the framerate.

I come here randomly to see if this hobby has moved out of 1995 yet and.. This thread just shows.. Nope.. We're still seeking out magic bullets, tweaks, and redundant debates about what edits do and don't work..  And in the end..  Nothing ever works.. Just another kink in the chain.. I'm so glad I abandoned this hobby a year ago...  Prepar3D was supposed to be the answer to it all and.. Well.. It's just more of the same in a different suit. 

 

The more things change

 

The more they stay the same

Then why are you still here? :>)

GSalden, on 08 Jun 2014 - 09:04 AM, said:

Guys, perhaps I am wrong but the latest Nvidia based cards ( 700 series + Titan ) have an automatically boost feature ( GPU Boost 2.0 ) that overclocks the card in GPU taxing situations.

The oc is only limited by the cards temperature.

 

To me it looks the EVGA software is doing exactly that but adds the possibility to lock the framerate.

I think this is the case, and my EVGA 760 card does this. However, how useful is this feature in a simulation which most of the time is still CPU limited? I am under the impression, this is indeed the case, at least for my system. I get pretty fluid simulation and great display quality under most situations, but in heavy city areas like Seattle or FB KSFO there seems to be no other way than throttling AI and/or autogen and/or scenery complexity down, all being CPU dominated, the GPU is powerless here.

 

Kind regards, Michael

Guys, perhaps I am wrong but the latest Nvidia based cards ( 700 series + Titan ) have an automatically boost feature ( GPU Boost 2.0 ) that overclocks the card in GPU taxing situations.

The oc is only limited by the cards temperature.

 

To me it looks the EVGA software is doing exactly that but adds the possibility to lock the framerate.

If that is true, than what I and others are seeing is just the result of a better frame-rate limiter than the one that comes with the program, and that could well be the case. 

 

I have also begun to wonder how much perceptions of the sim depend on WHERE you fly it. I live near NYC and fly in that area most of the time. The frame rates suffer accordingly. If I fly in Oregon or Colorado I get much better performance. Just a thought.

 

 

I have also begun to wonder how much perceptions of the sim depend on WHERE you fly it. I live near NYC and fly in that area most of the time. The frame rates suffer accordingly. If I fly in Oregon or Colorado I get much better performance. Just a thought.

 

Without a doubt.  I use P3D as two different sims--one for shorter hops at lower altitudes where I will use easier to process aircraft like RealAir Turbine Duke & Lancair Legacy in FTX regional scenery, and one for tube liners that are more difficult to run.  For these I stay out of hybrid mode, justing using Global, but can usually get away w/ add-on airports just fine.  With this approach I can fly everywhere and do well performance wise.

I don't know what you are doing wrong, as this has always worked perfectly for me:

 

Arwen, that is exactly as I have it...30 and set.

Guys, perhaps I am wrong but the latest Nvidia based cards ( 700 series + Titan ) have an automatically boost feature ( GPU Boost 2.0 ) that overclocks the card in GPU taxing situations.

The oc is only limited by the cards temperature.

 

To me it looks the EVGA software is doing exactly that but adds the possibility to lock the framerate.

I've been trying to tell people..that this is a FPS maintainer...and that is why I also run up in P3D to 40+ FPS, set to unlimited.  This is only telling the card what you want to see in performance, and it will manage the card's hardware assets to give you what you have dialed in.  It works...it sure works... I go higher, but never lower, except under the most taxing of situations, where the card and CPU simply can not output 30 FPS.  This is not a limiter...to cap you..this is a mean-average attempt by the card's hardware to give you NO LESS....on average.  There is a difference between a capper, and a target FPS dial in.

Arwen, that is exactly as I have it...30 and set.

I've been trying to tell people..that this is a FPS maintainer...and that is why I also run up in P3D to 40+ FPS, set to unlimited.  This is only telling the card what you want to see in performance, and it will manage the card's hardware assets to give you what you have dialed in.  It works...it sure works... I go higher, but never lower, except under the most taxing of situations, where the card and CPU simply can not output 30 FPS.  This is not a limiter...to cap you..this is a mean-average attempt by the card's hardware to give you NO LESS....on average.  There is a difference between a capper, and a target FPS dial in.

Still does not work on my box.

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

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.