Nautis said:/me skips page 5
Im a little curious what it would take for some people to "use" 3dmark again?
It seems to me many people are able to post critacisms but not discuss solutions. Why?
ByteMe!!!!!!ByteMe said:Hello Dig,
Just wanted to say hi.
digitalwanderer said:ByteMe said:On topic: What would it take for me to trust FM again? A firm commitment to protecting the integrity of their benchmark and strict enforcement of that with prompt replies to exposed cheats and an open policy.
Ever here the expression "Fool me once shame on you, fool me twice shame on me" ? I ain't going to even give them the chance.
Some of you say that their "business model" won't work. I would say it seems to have worked just fine until recently. If futuremark had the will to do what was right they would of been just fine. Too bad they sold out and set the stage for complete business failure.
ByteMe said:Some of you say that their "business model" won't work. I would say it seems to have worked just fine until recently. If futuremark had the will to do what was right they would of been just fine.
Joe DeFuria said:ByteMe said:Some of you say that their "business model" won't work. I would say it seems to have worked just fine until recently. If futuremark had the will to do what was right they would of been just fine.
We don't know that.
If FM did the "right thing", for all we know nVidia wouldn't have re-joined...and that could have been enough revenue loss to make their business non-viable.
As opposed to them taking the course they did and just losing credibility, which can make their business just as non-viable.Joe DeFuria said:If FM did the "right thing", for all we know nVidia wouldn't have re-joined...and that could have been enough revenue loss to make their business non-viable.
What? I'm really curious and not trying to flame you, what do you think it will be?PaulS said:TBH, i'm fairly sure you can guess what the statement is going to say
ByteMe said:Wait a sec. How long was nvidia not in the program?
I don't have Futuremark finicial statements... but where they losing money?
Futuremark was in a bad situation, some would call it a no win.
I'd say the only chance they had of winning was to stay with the no cheat at all.
digitalwanderer said:As opposed to them taking the course they did and just losing credibility, which can make their business just as non-viable.Joe DeFuria said:If FM did the "right thing", for all we know nVidia wouldn't have re-joined...and that could have been enough revenue loss to make their business non-viable.
I'm not really trying to argue with you Joe, just to point out that they had a choice between a financial hardship or a credibility hit and they chose the latter and will have to live with the consequences of that.
I'm kind of still waiting to see what their announcement is, hasn't there been enough time to double-check the changes with their beta members? (I really do get a little irked at their inability to enforce a policy review deadline and I think it's fair to be disheartened by it. )
I'm not real good with the whole "patience-thing" being Dig, I use all me patience at me day job.Joe DeFuria said:Just take a deep breath and give it a few days.
digitalwanderer said:What? I'm really curious and not trying to flame you, what do you think it will be?
Sorry, reflex. For some weird reason people keep thinking I'm flaming them whenever I get into an nVidia/FM discussion lately...PaulS said:You don't have to keep saying you're not flaming me every time you ask anything
In contrast to generic optimizations, application specific driver optimizations enhance performance in one specific program only. The performance enhancement may be done by discarding or replacing instructions, data or calculations. While this practice may be acceptable for games, it does not result in any benefit for a benchmark like 3DMark, but rather manipulates benchmark tests. Futuremark deems thus all 3DMark specific driver optimizations unacceptable.
In order to clarify its stance on driver optimizations and to help those companies who wish to have their products benchmarked with its industry standard 3DMark benchmark, Futuremark hereby publishes the following set of guidelines for creating drivers.
1. It is prohibited to change the rendering quality level that is requested by 3DMark.
2. It is prohibited to detect 3DMark directly or indirectly. In its sole discretion, Futuremark may approve detection in order to fix a specified hardware error.
3. Optimizations that utilize the empirical data of 3DMark are prohibited.
4. Generic optimizations that do not violate the above rules and benefit applications in general are acceptable only if the rendering is mathematically consistent with that of Microsoft® DirectX® reference rasterizer.
In its sole discretion, Futuremark may approve detection in order to fix a specified hardware error.