View Single Post
Old 11-11-03, 02:59 PM   #71
Sittin in the Sun
Nutty's Avatar
Join Date: Jul 2002
Location: United Kingdom
Posts: 1,835
Send a message via MSN to Nutty

As i said before be thankfull that Game Developers are not releasing anti dection code for their games as well. We have already seen through unwinder what the result is when that happens.
The point is, they wouldn't. Unless IQ is being sacrificed. If its not, then wheres the problem?

I mean I dont care that NV is cheating if the IQ stays the same. I really dont.

I dont see the difference with having a compiler in a driver making shaders work better, or a driver engineer making shaders work better. Ideally the former is preferred, but until they get a miracle compiler built, it aint gonna happen.

The whole issue of benchmarks is just totally flawed. I thought everyone agree'd ages ago to stop paying attention to PenisMarks.. sorry 3dmarks?

You should judge a card on what you're gonna use it for. If you're gonna play games, bench it with games. If you're gonna be a 3dmark bragger, then yeah use 3dmark. But frankly, I couldn't care less if NV said, yeah we cheat our ass off in 3dmarks.. I mean I just dont care. As long as my games run fine, and my programming works, thats all I care about.

Whats also annoying is that Futuremark are being paid by IHV money, which comes from you ppl that buy cards, to just sit there and churn out more anti-cheat patches that in the grand scheme of things just dont mean squat.

Why is it okay for JC to code a path for NV3X, but Benchmarks wont?

I'm starting to sound like a right nvidiot now, (which I prolly am) but I'm just soo bored of this 3dmark thing.

I can see the point of view of having a program that is supposed to run identical on hardware, to test performance. But that _isn't_ how things work!

I cant emphasise the point enough, whats the difference between the compiler optimizing a shader, and a person optimizing it, _provided_ the shader never changes? Which it most probably wont in a game.

Shader compilers are here to stay. The next generation of shader systems will be totally high-level, meaning there will be big differences in how each IHV compiles it down to suit their hardware. You just cant have a 1 path fits all valid comparison anymore.
Nutty is offline   Reply With Quote