IMPORTANT NVIDIA PETITION - ALL GEFORCE FX OWNERS PLEASE SIGN THANKS
 

http://www.petitiononline.com/nvidiafx/

wrote:
http://www.petitiononline.com/nvidiafx/

Already have. But I think one critical thing to affecting any change
will be a developer voicing the same who also just happens to be in
NVIDIA's developer relations program.

Even several thousand fan votes wouldn't affect as much change as a key
or vocal developer. Plus they also have access to many more resources.

As far as NVIDIA is concerned, I'm pleased to see they now have a
general community based forum on their own site, but I wonder how much
fan opinion weighs with them -- since it is very likely they could be of
the opinion that our quarrel is with an inaffectual Valve.

wrote:
http://www.petitiononline.com/nvidiafx/
DONE.....................

Half-Life 2 is ATI's game. Nvidia has Doom3 and that's where the FX cards
shine. We have known it would be this way for more than a year now. So you
just now getting it?

DaveL


wrote in message
...
http://www.petitiononline.com/nvidiafx/

DaveL wrote:
Half-Life 2 is ATI's game. Nvidia has Doom3 and that's where the FX cards
shine. We have known it would be this way for more than a year now. So you
just now getting it?

DaveL


wrote in message
...

http://www.petitiononline.com/nvidiafx/



It's not quite that simple. About a year ago or whenever the hell it
was, Valve had a "Shader Day". During this each company tried to demo
their best in the current build of the Source engine. At that time,
Valve had a mixed mode driver in place for FX class hardware. This used
partial precision hints where needed and a modified PS2.0A path to
greatly optimize the default FX performance without any image quality loss.

Editors at the time commented that it ran just as fast in DX9 as an
equal ATI card. This specifically concerned a 5900/U I believe. But
for final release (even after the source code and E3 leaks!), Valve
implemented a single PS2.0 DX9 path requiring full precision for
everything.

Ba-dump... FX performance goes down the ****ter and only driver
optmization or application detection to reorder the instruction in the
dynamic recompiler can help pull it out.

This is in addition to the problems the FX has anyway with instruction
order, pipeline stalls, a multitexture oriented architecture (pixel
shaders are single texture), and being heavily based upon a different
high level shader API, cG.