Massman

Uh-oh ...

Ehr, no. R5 = R5.

Hm. Did you try flashing the BIOS again? Maybe something didn't go entirely correct during the flash. Try this Atiflash version: http://downloads.hwbot.org/downloads/tools/atiflash.exe

But not all boards have 3x PCIe x16. The Asus one has too, I now found out.

Yes, I agree with you Roman. We discussed the timeframe already and went from 3m to 6m timeframe. I'm not set on 6 months; if 1 year would be better, then that's fine for me too. I'm all for consistency - anything else besides the points we should work on ?

Seems like the ASRock is the best option for full out Trinity. Only board with 3xCF support?

For the voting, we should develop a new voting mechanism in our backend that would allow voting through the frontpage. In that way, we can just allow the XOC members to vote, or only Team Captains.

Introducing new benchmarks doesn't work. People complain there are too many benchmarks.

Bios size is not the problem. It's probably going to be Vgpu or so. Let's try to figure out what the problem is. If you change to the backup BIOS (bios switch), can you then install the driver without any problem?

Huh - I'll try today as well .

The main issue is that it is becoming very difficult to introduce new benchmarks without saturating the bot. We can't continue like we do now and end up with 100 benchmarks that get points ... but we do need to be open for new benchmarks too. The rule that "everyone can choose what to bench" is relatively fine, but it does mean that everyone will just stick to what he likes and (almost never) try something new. I like the idea that we can push new benchmarks that may seem boring in the beginning but after a while get really interesting and competitive. The points wouldn't be "removed" as such, they'd just be inactive for 6 months. Visually, they would still be there and if after 6 months the benchmark is voted back in, the points will just become active again. If we do this only for global benchmarks, I think it wouldn't be that big of a problem? I do think the community would love to have more say in this kind of stuff .

Towards the end of the R5 development cycle, we want to introduce a tool that allows the community to control which benchmarks generate points and which no longer generate points. This would allow new, popular, benchmarks to come up by community request. Practically, we will move to a system where there are a fixed amount of benchmarks generating points (10, 15, 20 - not sure yet) and every 6 months a certain amount of these benchmarks can be replaced by others. A couple of benchmarks will always account for points. The exact implementation is still under debate. Currently we're considering cycles of 6 months. Also still up for debate is whether to do this on global points only, or on both global hardware. Also, still under consideration is what Leagues it would affect. Probably just XOC and EL - maybe Teams League too. An example: Cycle 1: list Bold = fixed benchmarks - Spi 1M - Spi 32M - Wprime 32M - Wprime 1024M - CPU frequency - 3D01 - 3DM03 - Heaven DX11 - Vantage - Memory Clock Cycle 2: Spi 1M, Wp 32M, 3DM03, Vantage, Memory Clock are up for replacement. After a vote, the 5 most wanted benchmarks for points by the community are: - Borandi's SystemCompute v0.4 - 3Dmark06 - Spi 1M - Wp 32M - CatZilla Your thoughts?

No, the BIOS is for sure for the GV-R797TO-3GD card . I mean - what is the Vgpu now at? What driver/os are you trying?

Yeah - might be. What about the Vgpu?

I'll check with GBT tomorrow morning (~ in 9h)

Moved the bugs thread to the Rev.5 subforum.

No, pro oc will not have to bench a lot of obscure mid-end garbage ...

Apart from the UGP/GTPP exotic class fix, we only plan a complete make-over for the Pro OC League. All the other HWBoint-related stuff (rankings, points, leagues) will see no change

We're just a small organisation, Roman. Patents cost a lot of money and even if you have a patent, you still need an army of lawyers to actually protect the patent. To be honest, it's actually quite flattering that a large company like that is "stealing" our innovative and creative ideas ... seems like we're doing something alright . It would have been interesting to cooperate on the project, though. I wonder why they never asked ...

The exact point scheme isn't fixed yet, but the scheme Borandi (again!) suggested seems pretty good. Currently the scheme is 1 - 60 2 - 45 3 - 33.6 4 - 26.2 5 - 22.4 6 - 21.7 7 - 21.1 8 - 20.5 9 - 19.3 If we follow the community suggestion from Borandi, if there are 9 participants in a ranking, the scheme would be: 1 - 10 2 - 7.5 3 - 5.6 4 - 4.4 5 - 3.7 6 - ... ... Any comments?

Following Borandi's request, R5 will have improved API support. Currently, we're looking into adding API support for: 1) RELEASED: Benchmark Ranking API The new API will allow benchmark developers to easily create benchmark rankings at HWBOT similar to the ones we already have. 2) RELEASED: Data-mining API Mainly focussing on opening up the data regarding submissions, points and user/team details. Not everything is set in stone yet, so feel free to give suggestions

Hi all, As you might have read in another forum topic, we have begun our planning and development for HWBOT R5. With Dennis having joined the HWBOT team, we can increase the development pace quite a bit. Therefore, we have also changed the way we approach major releases. R5 is, in contrary to R4 which launched as finished product, a work-in-progress with features being released when ready. The full-blown R5 can thus only be experience in a couple months time. At this point in the development stage we are close to release the first new R5 features. In this thread, we will keep track of the released features as well as announce the ones that are planned for R5. We have no pinned down exactly what will be included in R5, so we're still adding and removing ideas from the backlog. Revision 5 Statistics Last update: 04/02/2013 Total tasks: 121 Finished tasks: 52 Open tasks: 64 RELEASE NEWS 28/04: HWBOT V5.8.0/V5.9.0 Released: Integration of Simplified Chinese Language, League and Benchmark Timeline Features 25/04: Interested In The History of Overclocking? Become HWBOT Archeologist! 11/03: HWBOT v5.5.0/v5.6.0/v5.7.0 Released: Preparation Chinese, Pro OC V2 and About a Gazillion Bugfixes 01/03: HWBOT Pro OC Cup, a new challenge for extreme overclockers. 30/01: HWBOT v5.3.0/v5.4.0 Released: Data Mining API, New Pro OC Preparations and bugfixes 09/01: HWBOT Application API - How to get your benchmark a HWBOT ranking! 04/01: HWBOT v5.1.0/v5.2.0 Released: API development and bugfixes RELEASED FEATURES Competition Tagging: competitions can now carry a tag to group. For example: HWBOT OC Challenge-tag, OC Fanboy-tag, MOA-tag, etc. Team Timeline: the team page will carry an event timeline that displays historical information on points, rank, who left/joined the team, etc. HWBOT Benchmark Ranking API: benchmark developers will be able to use the HWBOT engine to easily create benchmark rankings. Parent/child Benchmark Structure: adding more structure to the benchmark application by introducing parent/child relations. For example: 3DMark11 is the parent application of 3DMark11 Performance, Entry, etc. HWBOT Data-Mining API: open the HWBOT database for 3rd party data-mining purposes. Internationalisation 2.0: translate site and work together with local representatives to give better support to the local communities. Update AM3 Wrapper: GENiEBEN is working on an update for the Aquamark3 wrapper. HWBOT Marketplace: As per community request, we will open a buy and sell section on the forum for overclockers to find new hardware to bench. Pro OC V2: complete make-over for the Pro OC competition. HWBOT Front-page Voting Tool: Develop a frontpage voting tool which allows easy community voting CANCELLED FEATURES Democritise HWBoints: community has the ability to promote new benchmarks for HWBoints as well as demote benchmarks to no longer have points. PLANNED FEATURES Competition Tagging: competitions can now carry a tag to group. For example: HWBOT OC Challenge-tag, OC Fanboy-tag, MOA-tag, etc. Team Timeline: the team page will carry an event timeline that displays historical information on points, rank, who left/joined the team, etc. HWBOT Benchmark Ranking API: benchmark developers will be able to use the HWBOT engine to easily create benchmark rankings. UGP/GTPP For Exotic Categores: improve the HWBoint distribution for exotic global categories. HWBOT Data-Mining API: open the HWBOT database for 3rd party data-mining purposes. Frontpage Revamp: update the look and feel of the HWBOT frontpage. Parent/child Benchmark Structure: adding more structure to the benchmark application by introducing parent/child relations. For example: 3DMark11 is the parent application of 3DMark11 Performance, Entry, etc. Implementation of Penalty Code: create backend options to improve punishment of naughty members. Internationalisation 2.0: translate site and work together with local representatives to give better support to the local communities. Pro OC V2: complete make-over for the Pro OC competition. Democritise HWBoints: community has the ability to promote new benchmarks for HWBoints as well as demote benchmarks to no longer have points. Update AM3 Wrapper: GENiEBEN is working on an update for the Aquamark3 wrapper. HWBOT Marketplace: As per community request, we will open a buy and sell section on the forum for overclockers to find new hardware to bench. Support Live Overclocking: Give more support to live overclocking demonstrations and events in an attempt to make overclocking more accessible and understandible to a larger mainstream audience. Cross-platform Benchmark: Prepare the HWBOT backend to fully support cross-platform benchmarking Describe and Document OC Career Path: Provide an explanation and documentation on how to get started with competitive overclocking in order to help new people to get into oc. HWBOT Mobile App: Create a useful app for Android/iOS users HWBOT Front-page Voting Tool: Develop a frontpage voting tool which allows easy community voting Localisation Map: A map on which you can find fellow overclockers or events in your neighbourhood. More coming soon (?) ...

Oh, interesting. It's pretty similar to what we showed almost 2 years ago ... Newsflash: http://hwbot.org/article/newsflash/1049_

Yes. You just need to flash the BIOS + remove the resistor to unlock full voltage range UVP = undervoltage protection UTP = undertemperature protection OVP = overvoltage protection etc ...

Not sure - just hardmod, it's very easy.