Jump to content
HWBOT Community Forums

Leeghoofd

Crew
  • Posts

    13448
  • Joined

  • Last visited

  • Days Won

    710

Everything posted by Leeghoofd

  1. Giving up is for pussies, Greeks are not quitters K it's a U CPU not a H, but it is still a 6 core.... look what happened if I pull this one from the compo... his 3100 score pops up...
  2. only one 6 core will count , the 5600x outperforms the 5600H
  3. @Doomed83 @Solid State Alchemy @Forks @TASOS @Mr.Scott @Cali_amr @Hilderman @Goku is Gei @exaberries @Hudson13 @Bavor K we tested the average fix on the UAT test server, it looks good, but we would request from you to submit also at the uat.hwbot.org ( remember it is slow ) for the Country Cup. this will allow to quickly find errors by your feedback. Take note that not all current scores are there, so if possible submit all the scores you subbed already at the standard HWBOT to the UAT one too plz (bewerkt) So Team USA we count on you! Other countries can also submit at https://uat.hwbot.org/ The sooner we can finish the testing, the sooner we can push this to production and leave another bug behind us...
  4. euh the stage mentions : Use 4,6,8,12,16 processor core(s) in total. 5600X and the 5600H are both 6 cores.... so only one score will count, you need to submit with the other processor cores too For the average score it took your score into account: 81 seconds divided by 5 is 16 seconds something... If it was the Ultraex2005 score of 130 seconds it would be 26 seconds average...
  5. yes The average score listed at the stage page is correct. The programmer is fixing the shown submissions that are part of this correct average score, as currently they are not properly listed if you click the average score in the stage ranking... Easiest thing for the teams to follow up is to make an excel and verify our average with yours... But keeping in mind if users submit multiple hardware scores that they can block other country members' scores...
  6. Thanks for the picture, interesting PCIe riser, what brand is that ?
  7. UL benchmarks is contacted about this score, keep you posted
  8. A setup picture would be recommended to verify the cooling setup
  9. no worries removed from the compo sir
  10. Your score got reported sir for missing screenshot, plz check out the rules and sample screenshot at: https://hwbot.org/benchmarkRules
  11. Your score got reported sir for missing screenshot, plz check out the rules and sample screenshot at: https://hwbot.org/benchmarkRules
  12. Your score got reported sir for missing screenshot, plz check out the rules and sample screenshot at: https://hwbot.org/benchmarkRules
  13. Plz check out the rules on how to submit at HWBOT ( https://hwbot.org/benchmarkRules ), even with BenchMate scores we require 2 X CPUZ tabs , one for CPU and one for Memory
  14. Plz check out the rules on how to submit at HWBOT ( https://hwbot.org/benchmarkRules ), even with BenchMate scores we require 2 X CPUZ tabs , one for CPU and one for Memory
  15. Plz check out the rules on how to submit at HWBOT ( https://hwbot.org/benchmarkRules ), even with BenchMate scores we require 2 X CPUZ tabs , one for CPU and one for Memory
  16. Plz check out the rules on how to submit at HWBOT ( https://hwbot.org/benchmarkRules ), even with BenchMate scores we require 2 X CPUZ tabs , one for CPU and one for Memory
  17. Plz check out the rules on how to submit at HWBOT ( https://hwbot.org/benchmarkRules ), even with BenchMate scores we require 2 X CPUZ tabs , one for CPU and one for Memory
  18. yes its divided per CPU CORE (not processor cores), so a Vermeer, Renoir, Cezanne, ...
  19. @_mat_ which benchmark ?
  20. You already have a better ddr4 sub. Only one sub counts per user.
  21. Plz check out the rules and sample screenshot at: https://hwbot.org/benchmarkRules , each 3D verification screenshot also requires 2 x CPUZ tabs (CPU
  22. Plz check out the rules at: https://hwbot.org/rules?referenceId=5169 , each verification screenshot also requires 2 x CPUZ tabs (CPU
  23. If there's somehting else unclear, lemme know anyway our coder is working on the average score listing. Plus we are trying to get rid of that blocking score thingy too, but the latter might not be fixed this weekend, it will require some extra testing
×
×
  • Create New...