Archive Thread of Screenshots of Ridunkulous Quality and Size [2007-2015]

Status
Not open for further replies.
No doubt. Will switch my SSD and SATA3 6GB/s drive to my Marvell controller today and just ordered (for pickup) a Highpoint PCI-E x1 SATA3 controller card to move my other drives to (off of the Intel SATA3). Ugh. You always assume the on-board OEM controllers are going to be BETTER than third party ones!

Now back to screenshots.
 
Any chance you can run a bench of Crysis?

1920x1080
DX10 Stock Very High
8xAA

Curious as to what your slow ass cards will pump out :p

And if you're running RAID you'll have to format as the add in card won't run the Intel RAID...
 
so just running the built-in gpu bench...8xMSAA, DX10 all settings to Very High...at the crap resolution of 19x10 ( :) ) I get:
Running GPU benchmark 1
Results will depend on current system settings
Press any key to continue . . .
Running...
==============================================================
TimeDemo Play Started , (Total Frames: 2000, Recorded Time: 111.86s)
!TimeDemo Run 0 Finished.
Play Time: 38.07s, Average FPS: 52.53
Min FPS: 38.87 at frame 1968, Max FPS: 68.21
at frame 974
Average Tri/Sec: -28297308, Tri/Frame: -538688
Recorded/Played Tris ratio: -1.70
!TimeDemo Run 1 Finished.
Play Time: 36.06s, Average FPS: 55.46
Min FPS: 38.87 at frame 1968, Max FPS: 70.29
at frame 96
Average Tri/Sec: -29707944, Tri/Frame: -535682
Recorded/Played Tris ratio: -1.71
Press any key to continue . . .

I will run with AAA later...have to go pick up my SATA3 card and head back to the office for a bit. What are you getting on those water-cooled 5850s?
 
Heck if I know. First time I've run a Crysis benchmark :) I see quite a few other "negative" tri/frame reports out there...maybe it runs backwards? :)

Seems that the ones with negative numbers are dual gpu...
 
itsmydamnation, nice shots. Funny thing, Bethesda originally had planned for full dynamic shadows but it was cut for performance reasons. Nice to see mods finally putting this back in.
 
Mods: could you please break-off the Crysis benchmarking into a new thread?

Here's something odd. I up the AA to AAA and the rez to native (19x12) and my marks went up?
==============================================================
TimeDemo Play Started , (Total Frames: 2000, Recorded Time: 111.86s)
!TimeDemo Run 0 Finished.
Play Time: 31.56s, Average FPS: 63.37
Min FPS: 46.27 at frame 1974, Max FPS: 81.97 at frame 930
Average Tri/Sec: -3307903, Tri/Frame: -52198
Recorded/Played Tris ratio: -17.56
!TimeDemo Run 1 Finished.
Play Time: 29.84s, Average FPS: 67.03
Min FPS: 46.27 at frame 1974, Max FPS: 82.79 at frame 875
Average Tri/Sec: -2493720, Tri/Frame: -37200
Recorded/Played Tris ratio: -24.64
!TimeDemo Run 2 Finished.
Play Time: 29.81s, Average FPS: 67.10
Min FPS: 46.27 at frame 1974, Max FPS: 83.06 at frame 983
Average Tri/Sec: -2393463, Tri/Frame: -35669
Recorded/Played Tris ratio: -25.70
!TimeDemo Run 3 Finished.
Play Time: 29.70s, Average FPS: 67.33
Min FPS: 46.27 at frame 1974, Max FPS: 83.06 at frame 983
Average Tri/Sec: -2396632, Tri/Frame: -35594
Recorded/Played Tris ratio: -25.75
TimeDemo Play Ended, (4 Runs Performed)
==============================================================
Press any key to continue . . .

Will add dx9 benchmarks next.

TimeDemo Play Started , (Total Frames: 2000, Recorded Time: 111.86s)
!TimeDemo Run 0 Finished.
Play Time: 37.29s, Average FPS: 53.63
Min FPS: 36.74 at frame 168, Max FPS: 101.19 at frame 909
Average Tri/Sec: -33110690, Tri/Frame: -617412
Recorded/Played Tris ratio: -1.48
!TimeDemo Run 1 Finished.
Play Time: 31.48s, Average FPS: 63.53
Min FPS: 36.74 at frame 168, Max FPS: 103.62 at frame 899
Average Tri/Sec: -39226428, Tri/Frame: -617462
Recorded/Played Tris ratio: -1.48
!TimeDemo Run 2 Finished.
Play Time: 31.32s, Average FPS: 63.86
Min FPS: 36.74 at frame 168, Max FPS: 103.62 at frame 985
Average Tri/Sec: -39403256, Tri/Frame: -617005
Recorded/Played Tris ratio: -1.49
!TimeDemo Run 3 Finished.
Play Time: 31.25s, Average FPS: 64.01
Min FPS: 36.74 at frame 168, Max FPS: 103.62 at frame 985
Average Tri/Sec: -39459048, Tri/Frame: -616498
Recorded/Played Tris ratio: -1.49
TimeDemo Play Ended, (4 Runs Performed)
==============================================================
Press any key to continue . . .

so 64 fps dx9 AAA

I think AAA doesn't work on DX10...
 
Last edited by a moderator:
Mize : TSSAA doesn't work in DX10, That's why you have to force the game to run in DX9. And that is also why DX9 takes more of a hit with anti-aliasing enabled as it's doing more work as it has to apply AA to the transparent/alpha objects were as DX10 does not. And run your Sandy Bridge at 5Ghz as to me you have some CPU bottlenecking going on.

My results :

Phenom 2 x6 overclocked to 4.1Ghz
2x PowerCooler 5850's overclocked to 950Mhz

crysis.png


I am also CPU bottlenecked, I did a suicide run at 4.3Ghz and my min frame rate went up to 37fps and my average jumped up to 57fps.

Also running the 11.1a beta drivers, might upgrade to the WHQL 11.1 drivers as they have been proven to be faster in reviews.

We need a thread in here were we can just benchmark and babble on about random hardware shit.....
 
what's a "suicide run"?

also, If TRSSAA doesn't work is it still applying MSAA?

As Dr. Evil said, Voltages too high for 24/7 operation but safe enough for a quick 10-15 minute blast.

As far as I can tell from playing the game it still does apply MSAA to polygon edges even if TSSAA isn't working.

I also installed the WHQL 11.1 drivers and got a nice little speed bump and it appears ATI have FINALLY re-added an option they removed about 12 months ago.

In catalyst 9.12 Adaptive anti-aliasing had 2 settings, Performance and Quality.

Performance used multi-sampling for alpha/transparent textures
Quality used super sampling for alpha/transparent textures.

This feature was removed in the 10.1 drivers and has remained absent until the 11.1 drivers, To me the 'performace' settings give a better 'sharper' look to the anti-aliasing quality compared to the quality setting.

Very nice looking system BTW Almighty!

Thank you kindly good sir.
 
Ah yes...I remember what you call suicide runs from my overclocking-benchmarking days. I remember my graphite-pencil-lead volt-modded Radeon 8500 with after-market cooling (thank you arctic ceramic epoxy) and my Athlon XP rig sitting outside my home office window in the dead of winter so I could break 10k in 3dmk2001 :) LOL. I probably "played" 3dmark more than any games in those days.

When I went to water cooling it was for silence as my computer was in a living area and I wasn't gaming then. Had (still have) a snazzy Lian Li silent case and it truly was nearly silent with water and all that sound absorbing foam they use. Ah to be young again.

So my lower 19x10 vs. 19x12 would be a result of scaling to my monitor's native resolution?
 
So my lower 19x10 vs. 19x12 would be a result of scaling to my monitor's native resolution?

To me it appears you have a CPU bottleneck, What speed do you have your Sandy Bridge clocked at? 5Ghz is easy acheived for 24/7 safe useage on these chips.

And going from 19x10 to 19x12 increases the load on the GPU's as it's a higher resolution, thus increases Crossfire scaling and efficiency giving you better results :smile:
 
Crysis, Mix of various mods and time of days...

The shots with a low framerate, It's because I had a stupidly tough config file loaded in terms of draw distance and LOD.

And some of them I capped the framerate to 30 or 35fps using the console.

Photobucket reduced the clarity of them again as the original captures are 2~3mb each..

8xMSAA + 8xTSSAA

Crysis1-1.jpg


Crysis2-1.jpg


Crysis3-1.jpg


Crysis5-1.jpg


Crysis6.jpg


You can see the anti-aliasing is working lovely in shot number 3, Perfect lines on both polygon and transparent game objects.
 
To me it appears you have a CPU bottleneck, What speed do you have your Sandy Bridge clocked at? 5Ghz is easy acheived for 24/7 safe useage on these chips.

And going from 19x10 to 19x12 increases the load on the GPU's as it's a higher resolution, thus increases Crossfire scaling and efficiency giving you better results :smile:

I'm running 4.4 GHz for now. No voltage bump, first try and just left it there.
 
Status
Not open for further replies.
Back
Top