***Official Unigine Heaven DX11 3.0 Benchmark Scores***

[Devious]

2500k @ 4.5Ghz GTX 670 @ 1244/7460



http://img24.imageshack.us/img24/5723/gtx670120730heaven.jpg




http://www.techpowerup.com/gpuz/8pm65/

 

[GoogalyMoogaly]

I wish Vega would give this a run with his 4 x 7970s!

Unless he already has?

 

[FMTopfan]

Either the fastest card ever or basic mistake of adding the cores together as its a sli setup ?

That reading is from Afterburner 2.2.0 beta15 via OSD because of the dynamic nature of Kepler - that was with a single GTX680 on 301.42s as I never tested single GTX680 overclocked - certainly no SLI going on there.

I recently moved on from AMD, with all the changes Nvidia made I didn't think anything of it but now my attention has been drawn to it, it does look high. If those clocks are combined in Afterburner then it is odd how when using single GPU, the boost information is the same.

Currently using 304.48 betas and boost information is not displayed/supported in Afterburner, either because they are betas or the driver fix of correcting the cards using lower clocks: "Fixes an issue where some manufacturer's factory overclocked cards default to and run at lower clocks."

Here is a couple archived screenshots from the 301.42s at the time, first one single GPU no overclocking - the second screenshot SLI overclocked. This shows exactly what I've been reporting and any issue is to do with Afterburner and not myself making a basic mistake whyscotty

 

[F1aw1ess]

The first number is your boost clock, the second is your shader clock

 

[OCPete]

The first number is your boost clock, the second is your shader clock

AFAIK there are no longer hot clocked shaders for team green in Kepler based cards. As such shader clocks are no longer relevant. All core clocks are identical. The doubled shader clock if shown is a error within the programme used the view the data. Earlier series NV cards had double speed shaders.

 

[Yaayuh!]

AFAIK there are no longer hot clocked shaders for team green in Kepler based cards. As such shader clocks are no longer relevant. All core clocks are identical. The doubled shader clock if shown is a error within the programme used the view the data. Earlier series NV cards had double speed shaders.

This.
The application is bugged if it's showing double the GPU clock speed.

 

[HankScorpio]

CPU clock doesn't seem to move scores at all for me. I ran at 4.2Ghz and got a 2045 score. Ran it again using 4.6Ghz and got a 2049 score.

 

[CivilDrone]

CPU clock doesn't seem to move scores at all for me. I ran at 4.2Ghz and got a 2045 score. Ran it again using 4.6Ghz and got a 2049 score.

same here, not much of a difference. I recon you only need to oc ur cpu if its a bottleneck for the card

 

[FMTopfan]

Quick update with 304.48 betas as they do give boost. Top GPU voltage dipped towards the end due to thermal limiting, however boost was constantly at 1228MHz.

GPUs - POV-TGT GTX680 Ultra Charged-SLI (overclocked to - Core: 1121MHz, Boost: 1228MHz, Mem: 1727MHz, Power: 112%, Voltage: 1.175).

CPU - 4.8GHz, 1.40vcore - validation

GPU-Z validation

Score: 4317 - 1680x1050 (old 301.42 score = 3908 / +10.46% approx change)

Link to full-size

Score: 3921 - 1920x1080 (old 301.42 score = 3585 / +9.37% approx change)

Link to full-size

 

[whyscotty]

That reading is from Afterburner 2.2.0 beta15 via OSD because of the dynamic nature of Kepler - that was with a single GTX680 on 301.42s as I never tested single GTX680 overclocked - certainly no SLI going on there.

I recently moved on from AMD, with all the changes Nvidia made I didn't think anything of it but now my attention has been drawn to it, it does look high. If those clocks are combined in Afterburner then it is odd how when using single GPU, the boost information is the same.

Currently using 304.48 betas and boost information is not displayed/supported in Afterburner, either because they are betas or the driver fix of correcting the cards using lower clocks: "Fixes an issue where some manufacturer's factory overclocked cards default to and run at lower clocks."

Here is a couple archived screenshots from the 301.42s at the time, first one single GPU no overclocking - the second screenshot SLI overclocked. This shows exactly what I've been reporting and any issue is to do with Afterburner and not myself making a basic mistake whyscotty

Apologies,no offence meant

 

[FMTopfan]

Apologies,no offence meant

No problem

 

[remy87]

3570k @ 4.4ghz

VALIDATION
http://www.techpowerup.com/gpuz/a55d3/

 

[Stelly]

Hey,

Know that this is a noob question but how do you take a screenshot... print screen gives me a black screen

Stelly

 

[Devious]

Normally F12

 

[remy87]

And it is located under C:\Users\xxxx that haven folder with the pictures.

 

[CivilDrone]

dead thread is dead, don't think anyone updating it

 

[F1aw1ess]

dead thread is dead, don't think anyone updating it

It does get updated, just the lad only drops by once every couple of weeks

 

[ChrisD.]

I'll have an interesting comparison for this thread tomorrow. I scored 2021 with a 7950 OC, I believe it's one of the quickest in the thread.

I've just bought a Windforce 670, which will be going into the same PC, so I'll have a direct card to card comparison in the same environment.

 

[F1aw1ess]

I'll have an interesting comparison for this thread tomorrow. I scored 2021 with a 7950 OC, I believe it's one of the quickest in the thread.

I've just bought a Windforce 670, which will be going into the same PC, so I'll have a direct card to card comparison in the same environment.

Interestingly they will perform about the same

If you get a good clocker you should be able to break 2100 mark, if your really lucky 2200

 

[BodgeITandRun]

dead thread is dead, don't think anyone updating it

LOL, I was waiting for someone else to say it this time. I said it last time and didn't want to be the one always complaining about it. It will be updated soon I am sure. I may as well try for an even higher score while trying.