Jump to content

Featured Replies

  • Replies 207
  • Views 22.2k
  • Created
  • Last Reply

Top Posters In This Topic

All want to ban PCMark 05 because of all the tweaks lol, and now all want to keep costum settings for Ucbench :( Dissallow all costum settings expect SSE settings and done :)

All want to ban PCMark 05 because of all the tweaks lol, and now all want to keep costum settings for Ucbench :( Dissallow all costum settings expect SSE settings and done :)

 

Nono in my opinion pcmark 05 is THE BENCH

Because overclocking and benchmark is not only change frequency and CPU voltage, win7 64bit and run bench like XTU >.<

I love pcmark!

But ucbench is different...

It is differned, but also mostley OS Tweaking :D So why still keep on this threat count? Clear all lists with threat change, only leave auto scores and lets start from beginning :)

Otherwise RIP Ucbench...

moose - Auto produces bug runs the most due to the core/thread formula Geni posted..

 

run only 2x thread sets

no affinity set

manually select SSE type

  • Author
Auto does not make bugged runs ;)

So what is ok to use for 4670k? 4,60,64 ok?

Or 3 core, whats ok to use :D

 

1,4,64 4670K

1,3,60 tricore

  • Author
Is this safe Genie? No bugged runs with it? What about -ri :D

 

Yes they are safe. Didn't try them with -ri.

Can we please remove this bench? People still put bugged scores on :(

Where is Problem to dissallow threat stuff i dont get it :(

  • Author
Can we please remove this bench? People still put bugged scores on :(

Where is Problem to dissallow threat stuff i dont get it :(

 

Because it was allowed in the first place.

Allmost all scores in 1 core ranking bugged, and nearly 90% scores of Topdog in HW points are bugged :(

Disable it completly otherwise we one day have 50p cathegorys with bugged scores...

I kind of agree that if a wrapper is being developed then all current scores should just be disabled and we start again with the benchmark.

 

Sure there will be a lot of unhappy people but it is impossible to get a solution to suit everyone because most people will have a different idea on what needs to be done to resolve the matter.

 

Surely the amount of work and effort that will have to go into getting every single submission checked and validated would simply be impossible with the amount of current submissions and more people adding submissions every day. That's the main reason why I personally think getting rid of what we have and adding a wrapper is the only way forward :(

Why not work directly with the author and avoid creating additional complications/bugs with a wrapper?

I guess he could easily modify the ui to suit hwbot needs, then only that version would be allowed.

  • Author
Why not work directly with the author and avoid creating additional complications/bugs with a wrapper?

I guess he could easily modify the ui to suit hwbot needs, then only that version would be allowed.

 

No he wouldn't, asked him over 2 years ago for a fix to my exploits, still nothing.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...