Jump to content
HWBOT Community Forums

AKM

Members
  • Posts

    546
  • Joined

  • Last visited

Everything posted by AKM

  1. Question for the first stage.. Say you have Geek 5 Pro version and run the bench in CLI (with tools that Primate Labs provides and is open to use in the bench) to only run the single core portion of the bench. Is this okay/allowed? Or is full bench run with regular wrapper needed? Just an open question as this saves a BUNCH of time on reruns ? don't want to be doing something wrong with this much money up for grabs
  2. Throwing in my two cents here.. I personally don't think disabling/re-enabling CF/SLI for multi-card benches should be a thing. Like Stavros mentioned, disabling cores on a 8 core cpu to compete in the 2 core rankings is definitely not a thing. Seems the logic should be the same all around? Then again, 3D01 is so unique because what other bench can you run in any order you please and still get a valid score? What other bench can you legit change settings between subtests and still continue on? Imagine if we could run Geek 3 test by test, etc. So in that regard, its all very grey because the bench and scores themselves date back so far before all the various rule changes and what not. Idk what the line between "cheat" and "tweak" is, or what it should be, but I think that in this context this should not be considered a tweak at all. Requiring proof for competitions I can understand as there are legitimate prizes on the line, but for every top score just seems like a huge pain. I'm sure we all have regular lives as well and time is already limited for a lot of us, and this just seems super extra for regular subs. But honestly, I myself don't have any valid ideas to police it. In my opinion we just nuke the globals for 01. It sucks because legacy 3D is my favorite but at this point don't see any other way to avoid situations like this. Maybe let it ride out until the end of the year/season and then change for next year? Hardware points should be good still because of how big the sub database is for 01, but we would hopefully not run into things like this again.
×
×
  • Create New...