Simviation Forums

Hello again!

After a couple of weeks of messing around with my new system, I'm pretty much settled on how I want it set up for FSX, and how I want FSX set up.

So, just for giggles, I figured I'd do some benchmarks using FSMark07 (which provides for a repeatable five minute flight.)

First, my OC'd system settings:

FS Version      FSX SP2 DX9
CPU      i7 920 @ 4.0
GPU      GTX 260 Maxcore @ 700, 1200, 1560
Memory      6GB DDR3-1600 @ 7-8-7-20-1600
Motherboard      Asus P6T Deluxe
Sound      Integrated
AA/AF      nHancer as per Nick
Resolution      3540x1024
Screen Mode      Full Screen
OS      Vista 64 SP1
Settings      See screen shots
Add-Ons      FSGensis, Traffic X, UTX, GEX

The cpu has been oc'd from 2.67 to 4.0 ghz, the memory is at it's rated speed and timings, and the GPU has been oc'd 20% (core, memory, shader) from 590, 999, 1296 to 700, 1200, 1560.

Here's some screenshots for the OC:





Next up are the FSX settings I settled on (following Nick's most excellent instructions):







For benchmarking, I did five passes in each of four setups:

CPU stock, VC stock
CPU stock, VC OC'd
CPU OC'd, VC stock
CPU OC'd, VC OC'd.

The five passes from each setup were then averaged and graphed.

From all stock to all OC, my max, min, average frame rates went from 12,24,20 to 16,29,23.

Here's the graph:



Now, keep in mind that I had the target frame rate set at 30 for benchmarking purposes. For normal flying, I set it to 24. Much smoother at that setting.

Hope you find this interesting. I had fun putting it together.

for FSM07 benchmarks to have any value the frame lock is to be set to unlimited

Nick, I would agree with you if I was doing the benchmarks to compare different systems.

In this case, it is to compare different levels of overclocking, all on the same hardware/software/settings. With the target frame rate at 30, and the benchmarks not reaching that point, I consider the results valid.

Regards,
...jim

Hi Jim,

So you got a 4.0ghz clock on 1.4 Vcore?

Wups, nevermind Jim, I saw 1.4 vcore and thought 1.24 vcore, my bad.

(But, what is your QPI set at?)

[quote]Wups, nevermind Jim, I saw 1.4 vcore and thought 1.24 vcore, my bad.

(But, what is your QPI set at?)

So all this overclocking gave you 4 FPS (according to screenshot)?

And how come you have such poor frame rates with that system? I know, silly question ... I don't have UTX and GEX.. it it possible those two addons have such imapact?

So all this overclocking gave you 4 FPS (according to screenshot)?

And how come you have such poor frame rates with that system? I know, silly question ... I don't have UTX and GEX.. it it possible those two addons have such imapact?

As I pointed out in my post above

Jims use of the benchmark tool and locking the frame counter does not show anything about overclocking and FSX

The frame lock tool in FSX is messed up, always has been, and it was made worse by Aces changes in FSX SP1/SP2 which effected vertical sync and the frame lock. It is not possible to make any assesments about overclocking and the FSX benchmark FSMark07 result when frames are locked

period

So in essence nick what your saying, is that we should not play fsx with lock frames, only in the unlimited position.

As I pointed out in my post above

Jims use of the benchmark tool and locking the frame counter does not show anything about overclocking and FSX

The frame lock tool in FSX is messed up, always has been, and it was made worse by Aces changes in FSX SP1/SP2 which effected vertical sync and the frame lock. It is not possible to make any assesments about overclocking and the FSX benchmark FSMark07 result when frames are locked

period

No.. its exactly as I said.. a user can not 'benchmark' FSX locking frames and get any real data from it


In free flight user must find what runs best where they fly.. typically with FSX locking frames outside of large urban areas works better where inside large urban running unlocked tends to display a better result, and, that is not set in stone as the system defines what works best.

You must find the frame lock that works best for the scene you are flying. There were many times in the past when I will start out locked at 30 at an airport in the mountains and then move my framelock to unlimited when I reach a large city in that same flight


however i7 tends to like frames locked at 28-30 all the time