June 20, 201411 yr Post Edit: Oh by the way...for those gritting their teeth about micro-stutter in P3D v2.2...you even get this phenomena at an FPS of 45 FPS as well. Not too bad..but it is there. Bummer....hope this is addressed in 2.3. 20,40 or 50fps doesn't matter. It's all same below 60fps.
June 20, 201411 yr Author Hey Mitch, really curious why you run such a conservative memory overclock - i run the same card as you and set the memory offset between 250-300 Mhz without a change in stability or temperature. OK, Dylan...I just changed my mem to 250 Mhz...and will try that. Let's see if anything improves beyond what I already show in P3D.....
June 20, 201411 yr Hey Mitch, really curious why you run such a conservative memory overclock - i run the same card as you and set the memory offset between 250-300 Mhz without a change in stability or temperature. Would be more informative to tell what clock you're running the GPU. Spirit
June 20, 201411 yr Author Would be more informative to tell what clock you're running the GPU. Spirit I had been running 110,100,60....tried 110,100,250....and no better performance in FPS, than my softer original over-clock. I went back to 110,50,30...and had the exact same, or actually even better FPS performance. My findings, are that a very aggressive overclock, does NOT necessarily offer greater performance over a slightly tweaked 'plus a few' from default. P3D is still a CPU's world....and yes...with a little help from its friends....GPU...lol.
June 20, 201411 yr I had been running 110,100,60....tried 110,100,250....and no better performance in FPS, than my softer original over-clock. I went back to 110,50,30...and had the exact same, or actually even better FPS performance. My findings, are that a very aggressive overclock, does NOT necessarily offer greater performance over a slightly tweaked 'plus a few' from default. P3D is still a CPU's world....and yes...with a little help from its friends....GPU...lol. This is the OC offset for the GPU clock but I mean the real GPU clock you're running. You can monitor this with EVGA Precision X. My GPU is max running with 1235 MHz. What MHz is yours running? Spirit
June 20, 201411 yr Author This is the OC offset for the GPU clock but I mean the real GPU clock you're running. You can monitor this with EVGA Precision X. My GPU is max running with 1235 MHz. What MHz is yours running? Spirit Between 1200 and 1300 MHz, of course shifts with demand load. How are you keeping your PX window on top of P3D? I have tried..with both window formats. How are you doing it? It's hard to catch the peak....
June 20, 201411 yr Between 1200 and 1300 MHz, of course shifts with demand load. How are you keeping your PX window on top of P3D? I have tried..with both window formats. How are you doing it? It's hard to catch the peak.... Hi Mitch, no need to have the EVGA Precision X open all the time, it must be active but can be hidden. On the left side of PX there's a button "monitoring". Click this and activate what you want to see. Chose where you prefer to see it. I've "in OSD" and it is shown on screen. The RivaTuner is doing this and you can adjust color, position etc. Fortunately it won't be in any screenshot so I've it all the time on. Spirit
June 20, 201411 yr Author Hi Mitch, no need to have the EVGA Precision X open all the time, it must be active but can be hidden. On the left side of PX there's a button "monitoring". Click this and activate what you want to see. Chose where you prefer to see it. I've "in OSD" and it is shown on screen. The RivaTuner is doing this and you can adjust color, position etc. Fortunately it won't be in any screenshot so I've it all the time on. Spirit Ahhh...ask a question, and you get an answer...ok...yeah...will be interesting to see what gives. Thanks, Spirit. You know..as I already stated in a post a few above, I have not truly found any benefit to go wild in the GPU overclocking of the off sets. I am (on my particular system) getting a ceiling max (for peaks) in the 75-78 FPS range (but never over 78 in any texture load scenario) with my thread .cfg in play. I do sustain now...in the 42-47 FPS range, and what I mean about sustain, and I think you understand what I am typing here...is that it will see those figures one after another in that range, with P3D always trying to give me the 47 FPS. I can not complain, and am not. My system was built and purchased with 2009 components, with the GTX680, purchased to replace the stock GTX285 about two years ago. All in all, it drives P3D, XPX, FSX and of course FS9, very well for my suit. The only thing that would have me swap out the motherboard as placed by Dell, is the fact that I am at the max for 12 GB's of system RAM. In a motherboard swap out...I'd could realize 32 GB or more.....a purchase (XPX-blah, blah....) for another year... :) Cheers! Mitch
June 20, 201411 yr The only thing that would have me swap out the motherboard as placed by Dell, is the fact that I am at the max for 12 GB's of system RAM. Ah ha ... the real reason you don't want 64bit now ... hehehe ... just messin' with ya Mitch. Glad you are enjoying yourself. Cheers, Rob.
June 20, 201411 yr I must be doing things wrong... I try all these tweaks, get frustrated - then reset all the nvidia stuff to stock and start with a fresh CFG file... ...and I end up with the best performance of all.
June 20, 201411 yr Side note... Just left squ....aaa.....mmmmiiish.... ....and once I got a touch out of town the flight to Whistler was simply gorgeous!!
June 21, 201411 yr I must be doing things wrong... I try all these tweaks, get frustrated - then reset all the nvidia stuff to stock and start with a fresh CFG file... ...and I end up with the best performance of all. That's the beauty of P3d2. People were so used to fiddling with FSX that they can't stop themselves from doing the same with P3d2. The rewards are both so modest (if any at all) and so so system dependent that they are usually masked by the ever popular placebo effect. So far I have seen one "tweak" that even makes a minor difference to fps/smoothness and that is setting the affinity mask to allow P3d2 to use all cores. Why LM blocked core 0 in the first place is a mystery that even they now can't explain. The only "tweak" that truly improves performance is upgrading one's hardware.
June 21, 201411 yr Author That's the beauty of P3d2. People were so used to fiddling with FSX that they can't stop themselves from doing the same with P3d2. The rewards are both so modest (if any at all) and so so system dependent that they are usually masked by the ever popular placebo effect. So far I have seen one "tweak" that even makes a minor difference to fps/smoothness and that is setting the affinity mask to allow P3d2 to use all cores. Why LM blocked core 0 in the first place is a mystery that even they now can't explain. The only "tweak" that truly improves performance is upgrading one's hardware. You know...there is merit is what you are typing here. I started by curiosity, stripping out any and all 'tweaks' from the P3d.cfg file. Even the JOB SCHED. Guess what? You are right...the code pretty well as been squeezed by LM....and you only might pick up one or two FPS, for all your trouble..or, even add boon-doggles... I had the biggest laugh..in that I practically had the same FPS performance with a stock .cfg. The performance truly was in what I had done in N.I. So, with a slight overclock of my G card...and what I have now in N.I....along with a few changes inside the actual nVidia driver mask...it's a wash. Just fly...and forget. I also found that if you truly leave the .cfg alone...you have a much more stable P3D, anyway.....
June 21, 201411 yr There's usually no harm in tweaking, because one can usually undo any changes. Sometimes people do discover tricks that work. The biggest problem is that there isn't a way of realistically benchmarking a specific tweak on a variety of setups. A legitimate P3d2 benchmark is really needed, but apparently no one has the time to create a good one. The secondary problem is maintaining the database and hunting down "cheaters" who submit bogus scores. Lastly, even if one could standardize a benchmark to take into account the wide variety of hardware being used to run P3d2, there are so many different combinations of add-ons that it would be difficult to develop a consensus on a specific tweak.
June 22, 201411 yr Another thing to consider, is that there's an extent to faulting your cpu/gpu/cfg. What I mean by that? simple, in order to avoid blurries, you need a FAST storage drive. Like an SSD, or few fast mechanical in RAID. There's just no way around that. To emphasis my point, reach out to serious developers, Orbx for instance, you'll find out they all use high-end machines, with SSDs of 0.5tb or more.
Create an account or sign in to comment