Jump to content
HWBOT Community Forums

Devroush

Members
  • Posts

    174
  • Joined

  • Last visited

Everything posted by Devroush

  1. How the hell do people find that tiny link at the bottom before they find the giant submit score button at the top . Alpha (hidden) is default so if they made it visible, they probably knew what they were doing.
  2. We pass on the e-mailaddress that you use on hwbot to Gigabyte, they then get in contact with you. Haven't you gotten any e-mail yet?
  3. I'll ask Frederik on monday about that since I'm not sure what you guys are talking about .
  4. Done, seems like he doesn't have a forum account though?
  5. You'll all be the judge of what benchmark will get points, read more about that here: http://hwbot.org/forum/showthread.php?t=62091 (if we go forward with it that is, reaction is... mixed)
  6. All submissions made this week are eligible to win, you don't have to submit to the competition itself. Just make sure that you're using the Gigabyte CPU-Z skin. 2 weeks left to win, keep submitting . Congratulations to this week's winner: Johni5!
  7. Fixed the bug, I also already edited your submission's mem batch to Hynix CFR.
  8. Yeah this was already reported, I fixed it today but you won't see it just yet on the main site, we'll let you know when it's deployed. I changed the behaviour a bit: - m.hwbot.org will always shows the mobile version of the site (still without search) - hwbot.org will show the regular version by default but if you're on a mobile device, it will show a red banner with a link to the mobile site, m.hwbot.org
  9. Looks good! Can they submit if the number of decimals is changed to something other than the default 80k? That should not be allowed. edit: Just tried out, scales well and submits nicely. Apparently you can submit if you change the slider though, and the slider resets to the default position so there's even no way of telling http://hwbot.org/submission/2356545_ http://hwbot.org/submission/2356544_devroush_multi_core_pi_core_i7_720qm_1min_7sec_768ms Also, you should try to use the API to automatically submit the score and delete the file locally once it's submitted. If you need help with the submission API, just ask.
  10. Old submissions aren't affected by this, they will still have their points .
  11. @ontheair: rankings were screwed up for some reason. You're second again, yay!
  12. It used to be broken, there was a warning message, but everybody still got points (like that submission that you linked).
  13. You don't get any points because for the enthusiast league, you need to provide a picture of your system, so that we can verify that you didn't use extreme cooling. I understand that you probably didn't pour liquid nitrogen on that K6, but well, those are the rules . edit: oh you were right, there was a little bug that it showed "does not participate in ranking for points" when you logged out. That's fixed now.
  14. Fixed for those result tables, let me know if it needs to be fixed anywhere else.
  15. Sorry you feel about it that way. Which combination of hardware that you use doesn't really matter. CPU benchmarks have a ranking for each CPU model, GPU benchmarks have a ranking for each GPU model. Like Genieben said, if we would award points for CPU/GPU combinations, earning points would just be a matter of grinding scores. However, if you look at the CPU ranking for example, there's still not a lot of competition: http://hwbot.org/hardware/processor/k6_2_550mhz_plus/ . Even if you don't overclock it, you'll still get some points if you run SuperPi, PiFast & wPrime (1024m if you have the patient, you'll be the first with that CPU ). To check which benchmark give hardware points, go here: http://hwbot.org/benchmarks/
  16. The code is fixed but it will be a few days before we do another deploy to the production server. Hang on to your score a little longer .
  17. Currently, when you go to your library, we check all your submissions and get the hardware from it with a giant SQL query. If you have a lot of submissions, this can quickly turn into a 5+ second query. For large teams, this would probably turn into a 1 minute query. To make a team library, we would need to keep the library itself stored in the database and update it once a day or so. edit: currently, about 400 such queries a day take more than 5 seconds. Doing such queries for teams would hammer the database pretty hard .
  18. URL fixed: http://downloads.hwbot.org/downloads/hwbot_unigine_heaven_v103/index.htm
  19. Maybe but we would need a more clever way to keep track of the library. User libraries can grow quite big, team libraries would be an order of magnitude larger.
×
×
  • Create New...