Jump to content
HWBOT Community Forums

websmile

Administrators
  • Posts

    5822
  • Joined

  • Last visited

  • Days Won

    58

Everything posted by websmile

  1. The point is not to put the blame on someone but to make a correct analysis why this happened to avoid making similar mistakes in the future again. Asking for something that has been done like putting the challengers online early (as said, concept is ready for two months nearly and the stages were online several weeks before 1st of february) will not help prevent stuff like this in the future because it was simply a bad call by one person. This could have been prevented by a simple thing like believing that staff knows what they talk about after running challengers for four or five years now. Frederik does an awesome job at re-organizing things including rev7 and new upcoming forum and so on, but especially if you already have too much work it is better to rely on decisions done by people who have the experience and knowledge at certain topics, otherwise this ends at fiiasco and tons of extra work for Albrecht for example like it did here.
  2. What you write is simply wrong - the comp is ready for 10 weeks and was online for a month - if you want to complain complain to new general manager who caused this chaos because he was unable to make and provide a background like it was planned and tasked weeks before the challengers started but simply decided one day before the start that "a background is not crucial". So send him a pm instead of discussing this with people who did nothing wrong
  3. Rules are final, I did some bug fixing and correction today, and unless there are bugs not found yet, the rules will stay as they are. No need to prefer single core, so we balanced the stages on all divisions with single threaded, multi-threaded benchmarks and normally one stage that is divided per core. Core limit no need if you plan stages correctly. For further questions, other mods now will help you
  4. After a discussion why the background is needed and that not using it would lead to re-submits the general manager accepted the need for the wallpaper later. Sorry for the inconvenience, this can happen when new leadership is installed, opinions need to settle on some things
  5. Try again, seems the configuration was messed up like on pro oc because someone took wrong prefix for wallpaper obligation. I hope it is fixed now.
  6. Hi everyone, on february 1st I officially stepped down from hwbot duty. Unfortunately I could not make an official post at the news section (doesn´t work^^) but here is the copy of my facebook announcment For emails or pms, please refer to richbastard, leeghoofd or strunkenbold in the future. Thanks for your support and best regards
  7. Christian Ney is not active for nearly a year now. In fact I made his job on top of mine. Due to the fact the forum does not work at all I also could not make an official announcement at news-section, but I stepped down from my duties on 1st of february, so if you have questions and PMs, please send these to richbastard or leeghoofd in the future.
  8. D – Hardware Unlocking Again this is a subject where we have to trust on the honesty of the submitter; if you have a CPU with unlocked multiplier, please only submit results under the hardware category of its original model. Don’t emulate other models to gain HWboints, if you are caught you will get penalized or even banned. The same goes for video cards which are modified either with a flashed BIOS or modded software, post your scores in the category of the original hardware. It is allowed to unlock extra cores and cache if your processor allows that. Again, you do have to submit your result to the category of the original hardware.
  9. Funny you did not delete your scores as well, slinky... I see no si 5.4 at any of your scores. There was no official news si 5.4 is mandatory now, and you might believe it or not but you just mess with a guy who helped clarifying the issue with Galax and FM for example
  10. HEDT was always forbidden at challenger I - the problem is configuration does not work because i7 is not submittable for what reason it may be
  11. No wallpapers for any division
  12. OK, there will be no wallpapaer anymore for Challengers. Happy benching
  13. websmile

    R15

    Nagging here will not help you - contact richbastard, I already tasked and informed him days ago.
  14. This is final from my side, what richbastard changes I can´t forsee
  15. Did the comp already start?
  16. We thought a lot about this, but we will not change things anymore. When skylake came, same core count Haswell and DC became more or less worthless, when 7350k came i3s were worthless, when ryzen came all older amd were junk. Some of the stages are single core or gpu limited, others are multicore and on one or two I made core division, but coffeelake is released for half a year now and we cannot limit it especially when you know that for older single threaded benches coffeelake does not support xp
  17. We can´t stop progress and we cannot make 20 divisions. 8700K will be division I and so on
  18. More testing, less reporting of old results is a good tweak as you already saw
  19. The season starts midth february
  20. CPUZ headline is reading cpu wrong - look at soecification line, there 1607 is shown correctly. We sometimes see this at cpuz, but mostly with new cpus. x265 just gets the wrong header info by cpuz, hence the wrong cpu is shown there
  21. General rules 1.6, all fm benchmarks can be benhed with win8 or 10 if you have a link, sysinfo enabled etc. You can check the table and amendments
  22. Your cpu is a 1607- there are no 2637s with 4 cores and you can see the real cpu at specification field.. I edit the results, thanks for the information http://www.cpu-world.com/CPUs/Xeon/Intel-Xeon%20E5-2637.html http://www.cpu-world.com/CPUs/Xeon/Intel-Xeon%20E5-1607.html
  23. We have a problem againn with a xeon http://forum.hwbot.org/showthread.php?p=504423#post504423
  24. https://www.futuremark.com/benchmarks/pcmark10 You can check requirements here and also trouble shoot at technical support
×
×
  • Create New...