Futuremark Releases 3DMark Time Spy DX12 Benchmark - Update to Benchmark Rules

Futuremark has just released its very first DX12 benchmark, titled 3DMark Time Spy. Time Spy is the latest benchmark test in the 3DMark suite and follows Fire Strike as top benchmark. DirectX 12 brings features such as asynchronous compute and explicit multi-adapter to the table. As usual, the 3D benchmark looks stunning.

The first submissions of 3DMark Time Spy have already arrived at HWBOT. Iji from Russia is currently leading the Hall of Fame scoring 12079 points with a pair of GeForce GTX 980 Ti at 1500/1900 MHz.

For those contemplating competitive overclocking, there is an important note coming from the moderation staff. To improve the experience for competitive overclockers, it is now required to ensure your benchmark result is validated by the 3DMark website in order to participate in the rankings. You can still validate using a screenshot or verification link. If you have any questions, drop a message below.


16

Belgium Massman says:


Sweden Rauf says:

Nice, but why different rules? Will it have hwbot-integration? No LOD should be stated clearly in the rules. And my opinion is that all 3Dmarks which require systeminfo enabled should have the same rules. If not, competitions will probably turn ugly...

Indonesia Lucky_n00b says:

Question: For this statement "For those contemplating competitive overclocking, there is an important note coming from the moderation staff. To improve the experience for competitive overclockers, it is now required to ensure your benchmark result is validated by the 3DMark website" Does that mean: - no LOD - no disabling Tesselation Or we simply have to validate through 3DMark website? Thanks!

Poland DeathRabit says:

Benchmark used 1745MB Vram my poor 7790 1GB take heave loses in score ;)

Australia Sgt Bilko says:

Lucky_n00b said: Question:

For this statement "For those contemplating competitive overclocking, there is an important note coming from the moderation staff. To improve the experience for competitive overclockers, it is now required to ensure your benchmark result is validated by the 3DMark website"

Does that mean:
- no LOD
- no disabling Tesselation

Or we simply have to validate through 3DMark website?

Thanks!


From what I can gather it looks like it's going to be bone stock runs with no LOD/Tess tweaks at all.

I would also like to ask how strict the "Valid" tag is as well since for AMD cards using a non-WHQL driver will give you an invalid score.

Denmark Nicklas0912 says:

any update of the rules?

Australia zeropluszero says:

Lucky_n00b said: Question:

For this statement "For those contemplating competitive overclocking, there is an important note coming from the moderation staff. To improve the experience for competitive overclockers, it is now required to ensure your benchmark result is validated by the 3DMark website"

Does that mean:
- no LOD
- no disabling Tesselation

Or we simply have to validate through 3DMark website?

Thanks!

I for one dont give a shit what Futuremark thinks is a valid submission. we should be able to disable tess and change lod for hwbot.

Indonesia speed.fastest says:

I think no problem if have non WHQL driver, disabling tesselation, and lod. Only validation link required with System Info enabled?

United States Splave says:

why not take all the tweaking out of it and just have the highest clocks win (not srs)

K404 says:

I don't care what the rules are as long as: They are written clearly. They are shown with examples of do/do not if the rule is somehow complicated to understand. They are posted in an obvious place. They are enforceable. They are enforced.

Denmark Nicklas0912 says:

Splave said: why not take all the tweaking out of it and just have the highest clocks win (not srs)


+1

Australia newlife says:

Huge move backwards if it doesn't allow tess/lod especially given I know how to trick 3dmark into thinking tess isn't disabled

Denmark Nicklas0912 says:

newlife said: Huge move backwards if it doesn't allow tess/lod especially given I know how to trick 3dmark into thinking tess isn't disabled


With LOD settings, the run will never be vaid...

Australia newlife says:

Nicklas0912 said: With LOD settings, the run will never be vaid...


I never said otherwise relating to lod, only tess

Denmark Nicklas0912 says:

newlife said: I never said otherwise relating to lod, only tess


So you dont think LOD should be allowed, but tess should :)?

Australia newlife says:

Both should be allowed but what I am saying is that 3dmark can tricked into thinking tess is enabled when in fact it's not

Please log in or register to comment.