Jump to content
HWBOT Community Forums

websmile

Administrators
  • Posts

    5822
  • Joined

  • Last visited

  • Days Won

    58

Everything posted by websmile

  1. Tasos now manages the proposals and you can re-post your ideas when you checked them again how much sense they make and how doable this all is. As he wrote, please do not go for expensive or unobtainable unicorn hardware and not stuff that is too new, have fun and I hope we can accelerate things a bit. Plan is to lauch the comp early january, so it would be good if we can sort this out until early november
  2. Watchdog, yes, required, it comes with XTU (monitoring and recovery). MEI should also be OK when you install it with XTU.
  3. I tested 6.4.12 and it worked with M5G and 3770K, Luumi tested 3470 Ivy bridge and it worked as well
  4. This now leads nowhere - if it would be the frequency only that determines result we would not have 4,5ghz 300000 point results like we saw at bugged runs btw. Before we end up speculating more I will lock the thread for a while until we can make more announcements
  5. Because we can fix the loophole on XTU which Intel did and we cannot fix the hole at Hwbotprime up to date - simple as it is
  6. We should find a mix. We have five rounds, each is a standalone competition. So feel free to use ooold stuff at one or two rounds and stuff that is a bit newer^^ at others. I am aware of the fact that 775 and after are not what we need, we had this and it is not really old school like
  7. The screenshot is something we should consider for sure, maybe in the way Albrecht proposed after rookie or Novice time is over and peope are deeper into the benchmark verification. We already made quite big progress at eliminating bugged runs, number has gone down drastically, but needs to lower this even more, to zero at best. This is the main problem we face that people still can talk about bugged runs when they cheat, we face this at other benchmarks as well btw
  8. It is easier to see out of line runs than you think.
  9. We might have to remove all top scores done with skl-x and also remove some other scores of different platforms that are "too good to be true". I am not sure disabling points for all xtu or disabling the benchmark makes sense. 99,9% of benchers did legit scores and only a few, maybe even some of those who already caused trouble at other benchmarks in the past, mainipulated scores. Why punish all when only a few did wrong?
  10. We need a solution sooner or later and I see no progress at reaching a final decision.
  11. Good run - please prepare for a rules change that results without frequency and temp info will not be accepted in the near future
  12. I asked a member to take over, under the premise that he uses the proposals offered in this thread. Four or five rounds by four or five different members, merged by him into the contest. I enjoy the discussion and brainstorming but we need a result in the end. If the member accepts and posts his result, you can give feedack of course, if he refuses to do the job I will find another solution
  13. Not for hwbotprime, but for x265 - we will release Havlis new version 2.1 soon and make it mandatory so checking is even easier and safer P.S. I want your ES :v
  14. New rookie rumble will start of saturday - sorry for the delay
  15. As said, a stage for server hardware only or with focus on server hardware is no problem for me. We give points for old school hardware, for modern gen, for sponsored guys, for low clocks to even chances and so on. The only problem in fact is mixing it like you said, and that times change is not only at desktop. We have a lot of new challenges ahead at divisions on road to pro with new core count gens, and servers will get more cores as well and so on. I9 is new and 2k now, times change and it is not hwbot that does it, and we all do not want progress to stop, getting 6 cores for price of four before is good. But times change and we have to find new solutions
  16. Closed, the vengeance are now offered locally. Thanks to the buyers and to hwbot for the space
  17. Fixed, link was https which sometimes doesnt work for parts of verification, try to remove s then and try again
  18. If you plan to sell another 7700K please make a new thread - this cpu is sold
×
×
  • Create New...