Jump to content
HWBOT Community Forums


  • Posts

  • Joined

  • Last visited


  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

yee245's Achievements


Rookie (2/14)

  • Dedicated Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare

Recent Badges



  1. I was looking at some of the stages, and for something like the 3dmark11 Physics stage, the rules mention SystemInfo 5.43 only. It appears there was actually a new version of SystemInfo that released a few days ago (on the 29th) that's version 5.44. should the rules be adjusted to be something like "5.43 and newer"? Edit: looks like a number of the other GPU stages have this as well. https://benchmarks.ul.com/systeminfo
  2. Just wanted to check in to see about the clarification regarding Xeons, like on the y-cruncher stage, and whether they're allowed or not.
  3. Accidentally subbed as a cloudgate rather than a skydiver. Already made a corrected sub in the correct category Please delete: https://hwbot.org/submission/4839693 Thanks. (Turns out if you had selected something other than the first item in the dropdown from the box (which automatically goes to the submission page for that benchmark), then navigate back to the page (back button in the browser), despite it visibly showing that other option on the page you navigate back to, if you click the "submit" button, it will actually then take you back to a benchmark submission page that is for whatever the first item in the dropdown is, not the other one you had previously selected (before navigating back in the browser). I did this accidentally, and then didn't notice that I was effectively subbing under cloudgate (which is the 1st option in the 3dmark dropdown) instead of a skydiver.)
  4. Not that I think they'd necessarily be part of the "optimal" set in any given stage as they stand at the moment, but it would be interesting to see how/if they'd affect that y-cruncher 2.5B stage. I figure the "optimal" set of subs would be something like 7350K, 5300G/5350G (forgot it was an Intel cpu only stage, but point somewhat still stands), 11600K, 9920X/10920X. It would be interesting to see if some random LGA 3647 Xeon could throw a wrench into things. Was just kind of curious, but not necessarily asking for them to be allowed in any given spot.
  5. Similar to socket count, are Xeons not allowed, except where explicitly stated as being allowed?
  6. Yeah, I noticed that happened too with a previous Superposition result when I subbed something for the team cup. It would appear that Unigine's site only allows for single submission to be public facing/published at any given point.
  7. Okay, thanks for the clarification. Just one last one, but once you pick a platform, can you change CPUs on the one mobo, or is that considered part of the base platform? Basically, the only changeable part across stages would be the RAM (or other unrelated parts, like maybe a PSU for whatever reason)?
  8. So, hypothetically speaking, if over the course of the three stages, an Intel platform is more optimal for one stage, and an AMD platform is more optimal for another, to be eligible for any of the overall prizes (the 1st through 5th place ones), a participant must pick either Intel or AMD to use for all three stages? And then, hypothetically, would that also mean that you must stick with either a desktop/main stream platform for all three stages, and you can't use a desktop platform (e.g. z490) system for one stage, but then a HEDT platform (e.g. X299) for another stage? I just wanted to clarify the "All participants have to use the same platform for all 3 stages" limitation regarding whether "platform" means more like "Intel platform" or "AMD platform" or if more specifically means "the same specific motherboard with one specific CPU". And related, for the lucky draw raffle, there would be no such restrictions, just as long as you entered something in each of the three stages, or again, is it that same restriction as what would be used above? And, just checking in advance, but does the same set of DDR4 have to be used for all three stages as well? I'm not sure if it would necessarily come into play, but if perhaps a 2x4GB kit of Corsair memory worked best for one stage, but a different 2x8GB kit of Corsair memory worked better for another stage, would using the two different kits for different stages be allowed, or would it then disqualify you for those overall 1st through 5th places?
  9. Can you please add? Thanks. Asus WS Z390 PRO http://valid.x86.fr/m337fp
  10. When Intel goes with the big.LITTLE with Alder Lake next gen on the mainstream platform, do we know how that's going to affect frequencies and stuff, as reported by CPU-Z? And/or, how might it be affected next year by these potential rule changes to CPU-Z validation? So, somewhat related to the third question of this poll, if the little cores don't/can't clock as high as the big cores, wouldn't that sort of effectively be like the situation where you're running some cores at lower frequencies (if not disabled entirely)?
  11. Looks like the changes must have gotten applied a little under 2 weeks ago, since it seems like there had been some submissions for it as recently as Feb 13. Good to know.
  12. I'm not sure if it's a hwbot submission page issue, or if it's a Benchmate issue, but lately when I try submitting y-cruncher Pi-25m results done with Benchmate (I think I've tried it 2 or 3 times), I've been the following error: Runs done on the same system for Pi-1b seem to go through just fine (no error about version number). It appears that some of my Pi-25m submissions (from BM were going through fine a few weeks ago, so I'm not sure if maybe something just got messed up on the hwbot end. A similar error message pops up and indicates that hwbot rejected the submission if I submit it directly through the program as well. I've attached an example set of files from a submission that gets this error. y-cruncher_Pi-25m_1.326.hwbot y-cruncher_Pi-25m_1.326.json
  13. Oops, forgot to change the wallpaper for the competition. I'll re-run the benches.
  14. Oops, forgot to change the wallpaper for the competition. I'll re-run the benches.
  • Create New...