Lots of replies I see.
You definitely need to get somebody that knows what he's doing working on your machine, if you have a "highest end" machine and videocard, and your framerates become unplayable at 4xFSAA. I can turn 4xFSAA on on my Athlon 1800 with my ti4200 and still remain playable, so either your definition of playable and mine are stupendously different, or you have a very shitty machine.
Also, some people might have noticed that I tend to exxagerate a little sometimes
Hence, if I say going from 800 to 100fps, I'm exxagerating. In case you didn't notice, it's still a drop by a factor of 8, which is pretty steep.
I happened to put together a top of the line machine for a rather well off acquaintance of mine, put a 9700PRO in it, and tested a couple of games on it (Elite Force 2 among them, not the newest of engines, but still a very new game) with all bells and whistles pumped up to the max, and it ran at around 40-60fps. That's MORE than enough for my taste. Perhaps not for you, so be it.
Xombie, Brick, JediLuke :
Screaming was perhaps an oddly chosen word. I was more referring to the fact that they had to release a press statement about how it wasn't working, and how they seemed to imply that it was Nvidia's / Microsoft's fault. I wasn't referring to the amount of noise they were making...
Please do everyone a favor, grab yourself a dictionary, and look up the definition of the sentence "It seems to me".
A lot of people on these boards also still seem to have a very hard time understanding that what people post here are opinions
So while you are leafing through that dictionary, look that word up as well.
It is my opinion
, hence I said "It seems to me", that this was caused by a bug in the Engine itself, not by anything else.
Funny enough, your statement " but from reading the information released, it seemed quite clear "
indicates you're doing the exact same thing. Ever heard of the saying "What's good for the goose is good for the gander?"
No, I'm not "making shit up", I'm posting an opinion. Just like YOU
are. Next time, try to keep that difference in mind, it might help.
So, to explain once again, it just SEEMS to me to be more of a bug in the Source Engine, since NOTHING changed on either Nvidia's side or Microsoft's side, and the problem is now fixed. Who was the only one who could have done any fixing on it? Valve. So, in all likelihood, where did the problem originate to begin with? In Valve's engine.