Massman

Is there anyone that is opposed to having the same rules like 3DMark11 and Heaven? If not, a poll isn't really worth the trouble even

Yes, they will

To go over the 1.35V voltage limit, you need to use the Afterburner Extreme. As for the bios, just renaming .sb into .rom should work.

Oh, where are you staying in Taipei?

Done! Send me a PM

Dropbox?

The practical difference between mipmap and tesselation is that mipmap is an on/off switch whereas tesselation (and lod) is a slider. Because it's a slider, you can finetune the tweak to near legit quite easily without anyone noticing. Mipmap was upping the score quite a lot, so it could be detected with a fair amount of certainty. But to answer your question: no, mipmap can not be detected on the screenshot. Fyi, if we enforce "only valid runs", we also can no longer use beta drivers.

Overclockers -love- beta drivers //edit: how can you not see LOD as a major sticking point for the 3DMark benchmark? Tesselation "optimisations" are clearly invalid for 3DMark submissions, but the LOD adjustments are not? Why?

Let's make a poll from this thread. As far as I can see, the problem is: - tesselation on/off allowed - only go for "this is a valid run" in the 3dmark gui or not Main problems: - tesselation cannot be detected in screenshot, only if the result has been uploaded to the ORB. That either requires a functional internet connection of the benchmark rig or a verification link. - if we want to enforce the "valid run only" (for tesselation), know that Nvidia LOD adjustments are not detected and are classified as valid runs in the GUI. Why disallow tesselation tweaking, but not disallow LOD tuning (as that is not detected) - disallowing tesselation would break consistency of rules between the various DX11 benchmarks So, I guess the poll options are: - allow tesselation and lod tuning - disallow tesselation, allow lod, but not enforce "valid run" according to the 3DMark ORB - disallow tesselation, allow lod and enforce "valid run" policy according to 3DMark ORB If we disallow tesselation and rely on the 3DM ORB for decision whether or not it's a valid run, I don't see how we can award points for the benchmark though. As said, LOD is still seen as valid and chances are the tesselation detection might break too with future drivers.

I'll check it out later today, there are a couple of bugs.

Yes, but the general HWBOT rules require a memory tab for all submissions - just for additional information . Just to complete the submission information .

Please add memory tab

I mean the changelogs

Why would your team have no chance in the Team Cup? If a small team from Belgium can participate and even two teams from Bulgaria are close to the top-10, why would it be impossible for a team from Brazil to get all the necessary hardware? It's not because you don't have the overclockers right now, that you can't try to find them. Most of the hardware you need is pretty obsolete and old, so I assume that there will be plenty of that in Brazil too. There should be a lot more hardware enthusiasts (not just overclockers) that can help with the results and scores. In last year's Team Cup, no team had scores entered in all the stages of the competition, I think, so it's not necessary to have all hardware to be able to compete or get close to the top-10. It's just about having fun and having a shared mission.

Hm, I'll add this to the buglist. Do you want it to be removed manually?

Go out on the street and make a video about it. If 20 people see you overclocking, it's fine. The requirement is not to convert people into overclocking - just to show .

Where?

Okay, added to buglist. Low priority.

Combined test has always been a problem. The 6970 had the same Combined issue you're describing. As far as I can remember it was indeed because of a driver issue. What happens if you disable SystemInfo and manually select the amount of cards to use for rendering? Just run combined.

Hm, or is it the comment field under the notifications on the user or team wall?

Okay, updated the stage a bit reducing the required minimum amount of spectators to be 20 instead of 50. But as I mentioned earlier, we will be quite lenient for this stage; all you need to do, basically, is go out and demonstrate your hobby

Which input field?

Okay, confirmed. Titan is not allowed.

The UGP/GTPP fix. It was planned for the sprint that ends tonight, but is postponed to the next development sprint which ends in two weeks. Not really a big change ... hence the "small" update

I can post this as a frontpage article