richba5tard

Ok i may be mistaken about CC points. But even though your seasonal points are reset in 2020, competitions at the end of 2019 still give you a boost for your 2019 ranking, which is set in stone on dec 31st.

CC points is a country based competition, they don't count toward member points anyway. Neither do team competitions.

After discussing the member points algorithm (both seasonal and carreer) with George for a bit I'd like to make a suggestion: Instead of top X total points which count towards your member points: top X global points top X hardware points (preferably same X to keep things easy to explain, but I can be convinced if need be) no benchmark/worldrecord points for crazy quad sli/crossfire setups, but an award/achievement instead This would close the gap between $$$ and skill further.

The reason has been explained earlier in this topic: because career points accumulate forever and new members would never have a chance beating old (and maybe inactive) members who participated in competitions. On top of that, nearly every other sports ranking resets yearly. Keeping all points forever and no way to beat them creates a closed and stale ranking system.

HWBOT Prime 1.0.2 added java 7 compatibility for old systems https://s3-eu-west-1.amazonaws.com/hwbotdownloads/downloads/hwbotprime-1.0.2.jar

Which old systems do not support java 8? I'll add java 7 compatibility if I must.

No offense taken. My focus was not hwbotprime the past years, and I hate shifting focus between projects. Should have done the clock cheat fix earlier, I know. Byte code alteration or adjusting memory is a whole other story though. As long as you allow your app to work offline, it can be hacked.

Newsflash, pretty much every benchmark can be hacked given enough time and skill. Question is is it worth spending dev time actively combatting hackers when the only gain is temporary internet fame? Benchmark makers should prevent easy cheating (like adjusting the windows clock), but injecting dll's/modifying code?

We have been supporting HTTPS for a long time but never redirected to HTTPS when using HTTP. This has now changed. Some old images or newspost might look bad, but it's more secure! API calls made by benchapps are an exception, I'm waiting for 3rd party devs to update their benchmark until forcing https.

I follow your reasoning @ObscureParadox but v1.0.1 is a tiny bit slower (due to cheat detection), not faster. As long as there are no algorithm changes I don't see a good reason to go through a beta period, same for the other benches.

I've made a new build which does not rely on javasysmon library, which is the cause of errors for @skulstation and @bigblock990 https://s3-eu-west-1.amazonaws.com/hwbotdownloads/downloads/hwbotprime-1.0.1.jar

I've updated the java sysmon library but it seems to give issues on some windows machines. I'm going to revert the change.

Thanks! Which cpu are you using?

Can you please run the benchmark via command line and tell me the output: java -jar hwbotprime.jar

The source of HWBOT Prime is under our control, so it's the easiest to fix.

Any feedback welcome. :)

No plans no, but if the community votes to add a specific benchmark I won't stop it.

Thanks all for casting your votes. No benchmarks will be disabled for hardware points, and Geekbench3 - Single Core and Geekbench4 - Multi Core will be eligible for points in the next update. ETA this week.

Thanks all for casting your votes. All Catzilla benchmarks will be disabled for hardware points, and GPUPI v3.3 - 1B, GPUPI v3.3 - 32B and 3DMark - Time Spy Extreme will be eligible for points in the next update. ETA this week.

Thanks all who voted and helped us decide which benchmarks should be applicable for gpu global points. VRMark, Aquamark and Catzilla(all), will no longer be applicable for global points when the next update is pushed to production. ETA this week.

Thanks all who voted and helped us decide which benchmarks should be applicable for cpu global points. The bottom 2, XTU and PiFast, will no longer be applicable for global points when the next update is pushed to production. ETA this week.

Happy new year!

No, I just took the list of current benchmarks with points enabled. Adding Heaven to the poll would be late now, but I sure consider it for the final list.

How many GPU benchmarks should get hardware points? If less, mention those who should be dropped.