Jump to content
HWBOT Community Forums

Frito11

Members
  • Posts

    51
  • Joined

  • Last visited

Posts posted by Frito11

  1. I'll take em if you can wait till Friday for payment, i've been needing to get another b-die kit anyways and would rather get something known to be decent and help a bro out but gotta wait till i get paid :)  no worries either way @Splave

    side note team USA discord is active for CC if you wanna drop in and say Hi :) 

    • Like 2
  2. 4 hours ago, ObscureParadox said:

    Well no it's not because Fermi is 400/500, Kepler 600/700 etc etc

    /ah right indeed forgot about the 600/700 thing. in any event must be by card series 6xx/7xx/9xx/10xx/20xx though because that is how the hwbot database is setup and I don't think cards under 6xx can even run TS Extreme, i know my 780 Ti was barely able to do it and basically all textures were just glitches due to not having enough VRAM to run the bench properly.. 

    in related news it looks like that same stage is miss configured because our team (USA) now has 4/5 subs and two of them that are counting are 10xx series cards so something to look into when you get time @Leeghoofd

    • Thanks 1
  3. I think its like i said a few days ago, most likely for some reason they have the stage set to only allow one sub per architecture code-name even though it does not state so in the rules. this is the only thing that i can think of that seems to fit what i see in every teams scores, everyones top 3 is some combination of 1x coffee lake, kabylake-S, kabylake-X and skylake, none ever have two kabylake-s subs counting even if they have a 2nd lower kabylake-s sub that will beat out a sub from one of the other architectures. 

  4. The other possibility i notice is that this stage is taking into account for some reason the cpu architecture codenames perhaps as there is no sub with multiple scores in the top 3 with the same arch, exception being kabylake-s(7700k etc) and kabylake-x (7740x) this would also explain why both our team (r/overclocking) and MLG are encountering the issue as both of us have 7700k subs that beat out the 7350k sub 

  5. ??? what the heck lmao whos vanno, anyways @richba5tard or @Leeghoofd ever sense the move to these forums my hwbot site account vs here has been screwed up, maybe my fault because i somehow had two hwbot accounts under frito and frito11 (never used frito11,  forgot password or something and made frito. anyways if you can sort it out whenever you have time Frito should be my one and only account across all hwbot things. 

  6. sad to see you leave Michael, you have been very fair IMHO and a great moderator in general from what i have seen in my relatively short time here on the bot, Alby i've seen you stepping it up in past months and you'r doing very well so please do keep it up! Also to you and the remaining staff if help is needed reach out, i'm not in a position to volunteer necessarily but i know there are others active on here that may be willing to help so if help is needed it can i'm sure be found!

     

    best to everyone and I hope the OC scene can continue to be a fun and interesting hobby for everyone that participates!

  7. i think the context of that rule change is for clock limited comps but it indeed does help with benches like this one that will bug out scores if you crash during a run and the only way to tell for sure that someone didn't crash out is if the gpu freqency monitoring is visible thru end of the run at full clocks at least on nvidia cards because if you do crash you ether loose the driver altogether and have to reboot or in many cases the driver recovers and your card is back at stock clocks but power state will stick if you forcing a higher power state (k boost etc)

×
×
  • Create New...