der8auer

Guys first we will try to find a solution for this issue. I already have an idea what causes this and also an idea how to verify it. I will do some testing straight tomorrow and tell you if it works or not

Mh is the performance that much off if XTU reports 5,1? Doesnt look that bad to be honest.

XTU reports a frequency of 5,7 GHz. I think if we set the limit there to 5,1 it could solve the issue. I think there is a problem with reading out the frequency wrong and XTU does some "score calculation" (which we know doesn't exist ) Maybe you can recheck that?

Does this issue only happen in Windows 8.1 / Windows 8? If yes the solution would be simple to ban the OS (again). We can always switch to another benchmark and also extend the qualification timeframe if required. That would not be an issue. Also switching from XTU 5 GHz to XTU full-out might be a solution. Depending on what exactly caused the bug we're talking about.

yea this would be invalid. Don't use capture.exe for a XTU screenshot. Good old paint helps

Whahaha

bout fiddy pointz

Sergio I can understand that you are angry but like Massman already mentioned in the other thread we don't want to see discussions like that in public. I already sent a warning/notification to both, draco and xevi so it should be sorted. If not they can still contact the HWBot stuff via email/PM. *closed*

Indeed Thanks man!

First of all HWBot is a neutral community open for all people no matter what kind of political or religious background they have. This also implies that we do not want to see any kind of political or religious discussions on hwbot. Just to make sure everybody feels comfortable and welcome in our community without any exceptions. We also don't accept any kind of racist behavior. I sent out a warning to XEVIPIU and hope it will stop now. Please feel free to contact me if you experience any other issues like that.

Well that escalated quickly

exactly my way of thinking!

via Imgflip Meme Maker

18th and 19th of October

When I first saw your score I was really excited that someone from Iran would make it to MOA. I have a lot of respect for what you guys manage to do over there. However we have to be strict with the rules and apply the same to everyone. Same goes to the rule about a live rebench. We only requested that in the past if the results were valid but either suspicious or hardware sharing involved. In your case the results are not valid so there is nothing we can do. Belive me I'm really sorry about that. Edit: I recall: Tesselation tweaking is related to the driver tesselation. It has never been allowed to change the benchmark itself. That's why you see "use default settings" on top of the rules.

Please do not mix up the case of cyclone with your case! Nobody said you were cheating. This does not apply to your case at all.

Yes it's possible to do that. However I will not explain how to do it exactly obviously. We can check in the database if somebody used this bug to disable tesselation. Since everybody is requesting more details: The result data contains all stuff like system data, benchmark and score details and so on. One little part is "d3d11_render_use_tessellation 1" which indicates the tesselation of the benchmark (not the tesselation of the driver!). In this case the detail was "d3d11_render_use_tessellation 0". So the tesselation of the benchmark was disabled which is a similar thing to change the resolution of the benchmark (not default settings). Don't get me wrong please! I'm not saying that he did it on purpose. Even if this happened by mistake or bug of the benchmark it would not be a run at default settings. The reason for the block would just change from "not ran at default settings" to "impossible score at given settings, possible bug or other". The result would be the same. We checked the unigine heaven score of all other submissions and all of them had tesselation enabled in the benchmark. If it was bugged it would be the same result like for example the black level scores of 3DMark03. Not caused by the user but in the end still not valid. Keep in mind that this is just the issue about the unigine heaven result. Like Massman explained already the 03 result does not have a valid link. We had this issue several times now during the qualifier and we cannot accept the result without a valid link. Futuremark just "confirmed" it via email that the result could be valid but they can't provide a link. It was clearly written in the rules that you have to be careful with the systeminfo and provide a valid link. Since the competition is over we also can't accept valid and lower scores which have not been submitted to the competition in time. Just my personal point of view: This is also a result of sandbagging. If these scores were submitted few days ago we could've looked into it and maybe helped you to get a valid score in time. Few minutes before the competition was over this is impossible. I'm really sorry this happened to you and can understand that you must be very disappointed and angry but since we are talking about a ticket to MOA with a lot of money involved we can't do any exceptions when it comes to the rules. I hope you understand that. I hope this is enough explanation for you guys.

Please contact Christian Ney, he will explain everything to you. I don't think we should have this discussion in public.

It's allowed to disable tesselation in the AMD driver but not to disable tesselation in the benchmark itself. The result was not done at default settings which is the reason for the result-block. There is no way this happens by accident so unless you are disabling the tesselation manually everything is fine. You don't have to worry. If you apply a "tweak" to disable tesselation of the benchmark your result will be blocked.

http://forum.hwbot.org/showthread.php?p=327214 To quote myself:

It looks like it's just the Xtream Team logo which screwed the screenshot a little. But since it has not been submitted to the contest it doesnt matter anyway.

Result removed from contest and blocked. Not ran at default settings. Tesselation has been disabled inside the benchmark.

Very well done guys. Congratulations to everybody who made it. Well deserved!

this is sick! dayum