On 09/04/06, Ivan Gyurdiev <[EMAIL PROTECTED]> wrote:
> What's broken with shaders? Are there known problems, or bugs that
> haven't been found yet?
>
There's quite a bit of functionality that isn't implemented, or isn't
implemented correctly, in particular v2 and v3 shaders. It also looks
like in
H. Verbeet wrote:
On 09/04/06, Ivan Gyurdiev <[EMAIL PROTECTED]> wrote:
1) The following pixel shader opcodes appear to be implemented with
fragment_ARB, yet they are marked REQUIRE_GLSL.
This generates errors, and they are skipped. Is this intentional?
D3DSIO_TEX (texld), D3DSIO_CND, D3DSI
On 09/04/06, Ivan Gyurdiev <[EMAIL PROTECTED]> wrote:
> 1) The following pixel shader opcodes appear to be implemented with
> fragment_ARB, yet they are marked REQUIRE_GLSL.
> This generates errors, and they are skipped. Is this intentional?
>
> D3DSIO_TEX (texld), D3DSIO_CND, D3DSIO_CMP.
I'm not
1) The following pixel shader opcodes appear to be implemented with
fragment_ARB, yet they are marked REQUIRE_GLSL.
This generates errors, and they are skipped. Is this intentional?
D3DSIO_TEX (texld), D3DSIO_CND, D3DSIO_CMP.
2) D3DSIO_CMP appears incorrect according to info online - the Openg
