Afrom1 Posted January 15, 2018 Share Posted January 15, 2018 Hi I cant summit from the website it says "No client version given, required version: 2.1.0" but it works when I submit from the benchmark and I am running 2.1.0. Quote Link to comment Share on other sites More sharing options...
Administrators websmile Posted January 16, 2018 Administrators Share Posted January 16, 2018 This often happens when cache of the browser or cookies are not cleared, it can also be a general browswer problem we saw lately. Using another browser or clearing cache and cookies often helps to solve this Quote Link to comment Share on other sites More sharing options...
Administrators websmile Posted January 21, 2018 Administrators Share Posted January 21, 2018 A note on unlocked cpu scores - because of whatever reason hwbot does not recognize 3 and 5 core results done with unlocked (useless ) AMD cpus, and users and staff can´t edit these. This also is a problem at the moment for other benchmarks, but for these we usually could fix it in the past. We will see if we can fix this, but now we are all busy with rev7 and other stuff Quote Link to comment Share on other sites More sharing options...
Administrators websmile Posted January 24, 2018 Administrators Share Posted January 24, 2018 We have a problem againn with a xeon http://forum.hwbot.org/showthread.php?p=504423#post504423 Quote Link to comment Share on other sites More sharing options...
havli Posted January 24, 2018 Author Share Posted January 24, 2018 It seems CPU-Z detects this CPU as Xeon E5-2637, while in reality it is E5-1607. Unfortunately not much I can do here, as x265 relies on CPU-Z detection... so if CPU-Z fails to detect properly the CPU used, the same mistake appears in x265 also. Sometimes this happened to me too, but should be possible to edit the submission manually and select the correct CPU once it is uploaded. Quote Link to comment Share on other sites More sharing options...
havli Posted February 17, 2018 Author Share Posted February 17, 2018 At the moment, I'm finishing my work on small update of x265 bench. Not so long ago there was some discussion concerning the granularity of the score. Since the beggining there were (and still are) just two decimal places. For most systems this is good enough to reflect even very small change in the performance. But not all of them - and since the attention is shifting more towards the 4k preset, maybe it is time to consider adding 3rd decimal place. Getting 3 decimal places is easy and after quick test it seems HWBOT API supports it also. So the question is - switch to 3 decimal places or stay at 2? This is double-edged sword, some people might benefit from it, others would lose points. 1 Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted February 17, 2018 Share Posted February 17, 2018 3 places. Excellent bench BTW. Becoming one of my favorites. 1 Quote Link to comment Share on other sites More sharing options...
yosarianilives Posted February 18, 2018 Share Posted February 18, 2018 I am all for it. Gives me more reason to rebench my g470 with ram on dice so people don't take my gold with .611 fps Quote Link to comment Share on other sites More sharing options...
havli Posted February 19, 2018 Author Share Posted February 19, 2018 Ok then - 3 places it is. Other than G470 it should also make benchmarking of very old HW more interesting. With the legacy mode even PIII / first gen K7 should be able to run. Who is brave enough to run 4k on slot A Athlon? 2 Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted February 19, 2018 Share Posted February 19, 2018 I will. 3 Quote Link to comment Share on other sites More sharing options...
yosarianilives Posted February 20, 2018 Share Posted February 20, 2018 19 hours ago, havli said: Ok then - 3 places it is. Other than G470 it should also make benchmarking of very old HW more interesting. With the legacy mode even PIII / first gen K7 should be able to run. Who is brave enough to run 4k on slot A Athlon? I think I've found your man as long as he has a slot A athlon around. https://hwbot.org/submission/3735265_mickulty_hwbot_x265_benchmark___4k_mobile_celeron_800mhz_(coppermine)_0_fps 1 Quote Link to comment Share on other sites More sharing options...
Guest Posted February 20, 2018 Share Posted February 20, 2018 Heaps of slot A ... how solid is your wallet Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted February 20, 2018 Share Posted February 20, 2018 6 hours ago, yosarianilives said: I think I've found your man as long as he has a slot A athlon around. https://hwbot.org/submission/3735265_mickulty_hwbot_x265_benchmark___4k_mobile_celeron_800mhz_(coppermine)_0_fps I have 4 slot A boards and a box of processors. GFD too. I wouldn't have said I'd do it if I didn't have the gear. Quote Link to comment Share on other sites More sharing options...
Guest Posted February 21, 2018 Share Posted February 21, 2018 That timing worked out well. Reminded me to hunt for a bigger slot A. Found a 850 Thunderbird cheap $15US. All win today Quote Link to comment Share on other sites More sharing options...
havli Posted February 25, 2018 Author Share Posted February 25, 2018 Version 2.2.0 is ready for release. http://hw-museum.cz/data/hwbot/HWBOT_X265_2.2.ZIP What is new: 1. there was a mistake in HPET detection of V2.1.0 - on systems that require HPET only error message was shown but the Run button wasn't deactivated... Therefore it was possible to run and submit the benchmark even without HPET (such results can be still recognized on screenshot - they contain red message "HPET timer not active"). This issue is now fixed. 2. Coffee Lake added to the non-HPET whitelist. Currently the list contains: Skylake, Skylake-X, Kaby Lake, Kaby Lake-X, Coffee Lake. 3. added option to select CPU name to submit. The first two options are 1) name like CPU-Z detects it 2) BIOS string. The third options leaves the field empty - this should solve the problem with unlocked AMD CPUs that are misdetected and can't be edited later. 4. increased the score precision to 3 decimal places. There is is a catch however. It seems HWBOT doesn't support it properly after all. Internally there are 3 decimal places - as they can be seen on the pre-submit screen... and also later when editing the submission. On the score page there are only two and how the rankings are calculated I'm not sure. Let's see if better precision can be implemented on the HWBOT side at some point in the future, x265 is now ready for it. http://hwbot.org/submission/3793276_ 5. updated CPU-Z to version 1.83. 4 Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted February 25, 2018 Share Posted February 25, 2018 (edited) Awesome. Can we use this for subs now or does it have to be approved. Edited February 25, 2018 by Mr.Scott Quote Link to comment Share on other sites More sharing options...
havli Posted February 25, 2018 Author Share Posted February 25, 2018 Yes, the new version is already allowed to submit scores. And if there are no problems with v2.2.0, it should be made mandatory after some time. 2 Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted February 25, 2018 Share Posted February 25, 2018 Thanks 1 Quote Link to comment Share on other sites More sharing options...
mickulty Posted February 26, 2018 Share Posted February 26, 2018 5 hours ago, havli said: 4. increased the score precision to 3 decimal places. There is is a catch however. It seems HWBOT doesn't support it properly after all. Internally there are 3 decimal places - as they can be seen on the pre-submit screen... and also later when editing the submission. On the score page there are only two and how the rankings are calculated I'm not sure. Let's see if better precision can be implemented on the HWBOT side at some point in the future, x265 is now ready for it Nice! Looking forward to rebenching this: http://hwbot.org/submission/3735265 Quote Link to comment Share on other sites More sharing options...
unityofsaints Posted February 26, 2018 Share Posted February 26, 2018 7 minutes ago, mickulty said: Nice! Looking forward to rebenching this: http://hwbot.org/submission/3735265 7.5 hrs Quote Link to comment Share on other sites More sharing options...
yosarianilives Posted February 26, 2018 Share Posted February 26, 2018 1 hour ago, unityofsaints said: 7.5 hrs You missed the 6 days preceding that Quote Link to comment Share on other sites More sharing options...
richba5tard Posted February 26, 2018 Share Posted February 26, 2018 Precision at HWBOT has been adjusted to 3 digits for new X265 submissions. 2 Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted February 26, 2018 Share Posted February 26, 2018 Nice. Fast too. Thank you. Quote Link to comment Share on other sites More sharing options...
yosarianilives Posted February 26, 2018 Share Posted February 26, 2018 Hmm... I need to finish binning my g470s and get some dice for the mems then. Perhaps I can still break 0.62 Quote Link to comment Share on other sites More sharing options...
yosarianilives Posted February 27, 2018 Share Posted February 27, 2018 Also just had this come in today, so that should help a lot https://imgur.com/a/VymnL Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.