Re: Can this loop be made faster ?

From: '\\\\o//'annabee ('\\o//'annabee)
Date: 02/28/05 

Date: Mon, 28 Feb 2005 08:40:01 +0100

På Mon, 28 Feb 2005 06:58:26 GMT, skrev Beth
<BethStone21@hotmail.NOSPICEDHAM.com>:

I am still pissed off at you Beth. :))

But as it seems you able to dig out info on just about anything. Could you
not take some time to post even more _details_ about for instance how the
pixels shaders work ? How does one avoid to have one pixelshader per
texture ? What is it the pixelshader do exactly ? If one need diffrent
pixelshader code for diffrent effects, do one need a lot of them ? hmm. I
could start reading those docs, but its not that time yet.

I just want to know, if the games that uses this is constantly changing
the pixels shader code, per texture, or if the pixelshader code remains
the same, or if theres many variants or what ?
If the pixelshader code is doing a _set_ function, and the result is
decided by the combinations of the textures why not have the hareware do
it ? and just select the function? And if you have to constantly replace
the pixel shading code, based on the type of surface, or texture, then how
the hell can this be done resonably fast ?

Do you have links to tutorials or even PDF files about how to understand
pixelshaders ? I mean links you have confirmed to be good, of course.

> Beth :)
>
> 

-- 
http://TheWannabee.org
Quantcast