View Single Post
Old 05-18-03, 07:13 PM   #111
Nv40's Avatar
Join Date: Aug 2002
Location: everywhere
Posts: 2,216

Originally posted by jjjayb
You are one hundred percent correct. If you can increase the speeds by not rendering what is not necessary that is a good thing. That is what occlusion culling is all about. This is done on the fly by videocards every day.

BUT, and this is a very big BUT, you need to be able to do that on the fly. If your drivers can tell what does not need to be shown by what the program tells it, that is great. If you have to manually go in and tell the drivers "in this specific benchmark the camera moves here, then here, then here, then stops, don't render anything else". That is cheating.

Once again because some of you just don't seem to get it yet. By preprogramming the drivers to ingore parts of the test because you have studied the test beforehand and tell the drivers exactly where the camera is going to go in a specific benchmark that is CHEATING. There is no other way to put it. It is NOT an optimization.

If I go in and take a test with the answers written on my hand that is considered cheating. This amounts to the same thing.

ANd what tells you that ATI is not doing the same thing?
they already know the answers of what its going to happen ,maybe not using the camera rail path ,but using another technique?

what you dont realialize is that KNOWING what is going to be rendering
ahead of time , is part of the strategy of NVidia and ATI for optimizations in
that benchamark and in all games .

Last edited by Nv40; 05-18-03 at 07:17 PM.
Nv40 is offline   Reply With Quote