Jump to content
HWBOT Community Forums

FireKillerGR

Members
  • Posts

    1754
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by FireKillerGR

  1. I understand why 01 multi-GPU might be killed at this point but eventually this would result in the same punishment for those who spent the money & time to have it figured out properly & fair with the one(s) that cheated. Additionally, what is funny is that the one(s) who cheated on 01, couldn't get proper scores on 03 cause there the scaling is much higher/more evident. This results in your "3x/4x" runs (single gpu) to be far lower compared to the actual/proper runs. That alone should be a dead giveaway that others weren't cheating; it was just yourself failing to figure things out and turning to cheating as the solution.
  2. Jokes aside there needs to be a distinctive line to whats punishable and what isnt and to what extent. Recall @Raufgetting banned cause he altered a screenshot of a legit score as he added a memory tab that was missing.
  3. Yes tbf maybe its coming from us as its easy to hook up the capture card, hit record and bench normally. It just sucks that some manage to ruin it for everyone else. For 03 its quite clear as the scaling is evident. Can do some further tests to confirm but its basically visible here: Recent 1x GPU score with alder cpu: https://hwbot.org/submission/4858339_chispy_3dmark03_radeon_r9_290x_273295_marks Our 3x: https://hwbot.org/submission/5020268_ogs_3dmark03_3x_radeon_r9_290x_420566_marks vs our 4x: https://hwbot.org/submission/5020272_ogs_3dmark03_2x_radeon_r9_295x2_446238_marks For 01 its a bit more tricky but its also evident by judging based on Nature's FPS. 2+k FPS on 21.5.2 drivers with 290x4 should be easily done with cpu at 5G or so (2.3k fps at 5.6G cpu). Cant comment about older cards/drivers. Below you can see 4x xfire vs single gpu with cpu clocked at 5.6GHz in both cases. I believe single gpu scales better on most tests when pushing the cpu (or requires different LOD) but either way the gap in Nature is massive.
  4. Hi everyone, after the recent discussion about the loopholes of old benchmarks (especially 01) and how they can be tricked by running them with less GPUs enabled in SLI/Crossfire while subbing with full Crossfire/SLI enabled, we did some research today to see whats up. We recorded a video of 21 mins non-stop testing showing enabled 4x GPU Crossfire vs Single gpu and their differences & also sent a comparison screenshot to the moderating team (full video available to them at any point of time) As the performance gap between single and multi-GPUs on 3DMark2001 is quite close, some seem to have taken advantage of it and run the benchmark with one GPU as they couldn't figure out how to get the performance to work on multi-GPU configurations. Thinking that everyone is cheating and instead of raising the question towards the mod team or reaching out to other users in a discrete way to check what's up, chose to take advantage of the small performance differences in order to run the benchmark with a single GPU before enabling the Crossfire for screenshot purposes. Eventually this is not just about figuring a potential concern but also about deliberately running a false configuration on purpose for personal gains. The performance difference being small or the lack of system info should not be the reason to call it anything differently than what it is. To our eyes this is NO different than disabling cores on a 12900K/12900KS and ruling the 1c/2c/4c/6c cpu categories other than this being visible to the eyes of the community and the moderating team. Same way one could do the exact opposite and run 2x GPU in SLI/Crossfire and disable it to sub it under the single gpu category of any 3D benchmark. How visible it is makes no difference to the action itself. NOTE: It is SO visible as a specific test of 3DMark2001 performs worse with a high clocked LN2 CPU (running single gpu) vs a run at 5.6 GHz with Crossfire enabled. With new competitions coming in and HWBot slowly growing again, it is also on the users to maintain a certain level of transparency and avoid clear wrong-doing and not just on the moderating team. We are coming out publicly on this as killing a benchmark cause some(one) CHOSE to cheat while others invested time & money to figure it out shouldn't be the way. Additionally, thinking that everyone is cheating and submitting scores with wrong configurations on purpose for personal gain should not be left as is either. We mentioned it before and we are mentioning it again as we stand by it; we are always open to make video-proof a necessity for top-10/20 scores & comps to maintain fairness towards all users. Regards, Stavros & Phil
  5. Always down to have video verification mandatory
  6. As a naive person, I suspect that the timing of this being raised is just unlucky. ? Even though we are on a tech world/hobby and changes are expected with the pace things move, I believe we can agree that the changes happening are in some cases a bit random and also too often (format changing annually at this point). There is no way this wasn't foreseen 6 months ago when the initial changes came in and now opting for a mid-season change after people have spent $, time and ln2 to bench these. 01 is the perfect example as it should have never come back into the game for these exact reasons/concerns you mentioned. Instead, you have other benchmarks that scale nicely (2x, 3x, 4x +) that don't get points (on multi-gpu configs) due to low popularity. This kicks off a never-ending loop where no points are awarded -> nobody benches these -> they wont become popular.
  7. Won't be able to participate by the looks of it as a 2 month staggered comp during the summer time is a bit harsh. Sick comp nevertheless; good luck everyone!
  8. Since market prices have dropped significantly, new and final price -> 470€ shipped
  9. For sale a G.Skill DDR5 6400C32 kit bought from Alternate.de a couple months ago. Does 7400+ Geekbench 3 full ambient and most likely 7500+ as well (no maxmem, 8C/16T) 470€ shipped + fees if any.
×
×
  • Create New...