Why? The FP render targets are only useful for storing immediate results. What do they have to do with depth buffering?antlers4 said:So no FP depth buffer without using shaders? That's a little disappointing. I thought it would come naturally with the 128-bit frame buffer.
antlers4 said:So no FP depth buffer without using shaders? That's a little disappointing. I thought it would come naturally with the 128-bit frame buffer.
antlers4 said:So no FP depth buffer without using shaders? That's a little disappointing.
It's only 1-Z because "someone" decided to put a subtract in the 'standard' projected depth calculations. It would have been cheaper and more accurate to leave them out in the first place!DeanoC said:You can use a 1-Z floating point depth buffer using just vs 1.1. Which can be handy (its has many of the same properties as a W buffer).
ET said:Just checked the 9500. It doesn't have the control panel option that the 7500 has, for example, to allow a 32 bit Z buffer.
Because it is true. R300 does not support 32bit Z-buffer.ET said:antlers4, why do you say that?
Xmas said:Because it is true. R300 does not support 32bit Z-buffer.ET said:antlers4, why do you say that?