HardOCP's position on the 3DMark2003/Nvidia issue

[Evildeus]

Grrr mistake between edit/quote

 

[MuFu]

I suppose this could blow your chances of getting an NV35 direct from NVIDIA. I am surprised you made that decision DaveB, as you could have pissed two parties off with one shot

My money says he grabbed one and ran with it.

MuFu.

 

[Luminescent]

I see nothing wrong with how B3D handled the situation.

 

[Dave Baumann]

ED,

We are not spokespeople for FM, we are reporting something that can be found in 3DM03, however because of the nature of the Beta program we have to liase with FM to release pictures because they are technically all under NDA.

 

[jjayb]

But the fact that FutureMark endorsed the exposé surely invalidates your argument

******off topic******

Mufu, how did you get the ' above the "e" in expose? Anybody feel free to jump in and answer this.

 

[MuFu]

I'm sorry, but futuremark where did futuremark said they endorsed it? They didn't say anything just they are aware and investigating.

They must have, otherwise the ET article would never have been allowed to be published. Posting pics from the dev build like that is otherwise a breach of NDA.

Edit - ok Dave said that already, doh.

MuFu.

 

[Joe DeFuria]

I also doubt that FutureMark would post a link to the ExtremeTech article on their site FutureMark didn't endorse it...

 

[Evildeus]

Believe me nobody benefits from this situation. Quite frankly I hate that we have been put into this sutuation.

From our part we have played it completely straight - I saw this a week ago and I sent both screenshots to NVIDIA (something which did actually get me into a little hot water with FM seeing as they are supposed to NDA'ed) and I've asked them to provide an explaination, to which they haven't as yet. What else are we supposed to do?

Then it should have been the case till the end of the story no? We did had hit that there were issues, and then that ET was doing the article.

Why did you get into hot water and ET didn't 1 week after?

PS: I do understand what you are saying and moreover that's why i like B3D and await from you guys. But i have a feeling with this affair that you are being used in some way that i don't really like. Hope to see B3D stay on this line

 

[MuFu]

I also doubt that FutureMark would post a link to the ExtremeTech article on their site FutureMark didn't endorse it...

Well I dunno man, maybe that is accidental.

MuFu.

 

[Ostsol]

But the fact that FutureMark endorsed the exposé surely invalidates your argument

******off topic******

Mufu, how did you get the ' above the "e" in expose? Anybody feel free to jump in and answer this.

Hold down the "alt" key and type 130: é. The number correspondes to ASCII character codes: http://www.asciitable.com/

 

[gkar1]

All i can say is wow. They have sunk to a new low. Brent should leave Kyle to his pathetic rantings and baseless accusations and find a website more suited for his caliber in hardware reviews(hint hint Dave). Simply pathetic. [H] has lost another reader.

 

[Joe DeFuria]

Why did you get into hot water and ET didn't 1 week after?

Presumably, because ET got FM's permission first.

PS: I do understand what you are saying and moreover that's why i like B3D and await from you guys. But i have a feeling with this affair that you are being used in some way that i don't really like. Hope to see B3D stay on this line

I honestly don't see how B3D is being used at all....I mean , B3D hasn't done anything, except perhaps give nVidia a HEADS UP.

 

[Evildeus]

I also doubt that FutureMark would post a link to the ExtremeTech article on their site FutureMark didn't endorse it...

Well it's a beta member isn't it? I don't see any endorsement, but as i said, i don't think there will be any. That's making the game of Futuremark and ET

PS: It wasn't here 2 hours ago, and in Sweden it's late right now

 

[Evildeus]

Future will tell us

Well the behavior of Futuremark has greatly changed in 1 week from getting mad to advocating something 8)

Why did you get into hot water and ET didn't 1 week after?

Presumably, because ET got FM's permission first.

PS: I do understand what you are saying and moreover that's why i like B3D and await from you guys. But i have a feeling with this affair that you are being used in some way that i don't really like. Hope to see B3D stay on this line

I honestly don't see how B3D is being used at all....I mean , B3D hasn't done anything, except perhaps give nVidia a HEADS UP.

 

[jjayb]

Thanks Ostol. Just put that site in my favorites.

 

[Joe DeFuria]

Well it's a beta member isn't it? I don't see any endorsement...

Um, FM wouldn't link to an article that they had any issues with. I don't think anyone is saying that FM endorses the conclusion that it's cheating, but FM certainly has no issues with the article being written, and the use of screenshots from the developer release to provide the evidence.

 

[Evildeus]

Sure, i've nothing more to say on the subject. They should have themselves produced the pics, IMHO.

 

[Hyp-X]

******off topic******

Mufu, how did you get the ' above the "e" in expose? Anybody feel free to jump in and answer this.

Hold down the "alt" key and type 130: é. The number correspondes to ASCII character codes: http://www.asciitable.com/

Even simpler way is to press the <É> key on your keyboard. 8)

If you don't have that, you can install the "US International" keyboard locale (assuming you use Windoze), and press <'> followed by <E>.

 

[Joe DeFuria]

Sure, i've nothing more to say on the subject. They should have themselves produced the pics, IMHO.

They did re-produce the issue. What do you want? For FM to actually e-mail their own pics for ET to use?

 

[ZoinKs!]

Some folks are questioning whether ExtremeTech has broken any rules by posting info from the developer's build. I saw this on the ET forums:

FutureMark specifically gave us permission to run this article. We worked closely with them to develop this story, as they have been aware of this issue as well. And while the licence agreement would normally preclude our doing a story using the developer's version, FutureMark made an exception in this case.