🔒 Locked

Texture setting

Started by The C modest god Feb 21, 2005 at 12:35 PM 3 replies 400+ views

Original Post

Feb 21, 2005 at 12:35 PM

What does the following lines of code do?


        pD3DDevice->SetTextureStageState( 0, D3DTSS_COLOROP,   D3DTOP_MODULATE );
        pD3DDevice->SetTextureStageState( 0, D3DTSS_COLORARG1, D3DTA_TEXTURE );
        pD3DDevice->SetTextureStageState( 0, D3DTSS_COLORARG2, D3DTA_DIFFUSE );
        pD3DDevice->SetTextureStageState( 0, D3DTSS_ALPHAOP,   D3DTOP_DISABLE );

Evil Steve

Feb 21, 2005 at 1:01 PM

It causes the colour generated to be texture * diffuse, and disable alpha. Texture * diffuse is the default for stage 0 anyway, so it does nothing except disable alpha - unless the texture stage has already been changed.

DrunkenHyena

Feb 21, 2005 at 1:36 PM

Quote:
Original post by Evil Steve
It causes the colour generated to be texture * diffuse, and disable alpha. Texture * diffuse is the default for stage 0 anyway, so it does nothing except disable alpha - unless the texture stage has already been changed.

Not that explicitly stating what you want is a bad thing. Never rely on the defaults, so if that's what you want, that is what you should set.

As a side-note, setting alpha to DISABLE in an active stage is illegal. Don't do it.

Evil Steve

Feb 21, 2005 at 2:19 PM

Quote:
Original post by DrunkenHyena
Quote:
Original post by Evil Steve
It causes the colour generated to be texture * diffuse, and disable alpha. Texture * diffuse is the default for stage 0 anyway, so it does nothing except disable alpha - unless the texture stage has already been changed.

Not that explicitly stating what you want is a bad thing. Never rely on the defaults, so if that's what you want, that is what you should set.

True. However, it doesn't really make sense for the default to be anything else in this case.

DrunkenHyena

Feb 21, 2005 at 3:48 PM

Quote:
Original post by Evil Steve
True. However, it doesn't really make sense for the default to be anything else in this case.

If you rely on the drivers to always be right, you're in big trouble. And yes, I've run into cases where drivers were NOT setting these to the defaults. Things are better, but even if it only happens once it can cause you a lot of grief. So considering how little effort it takes to set those states yourself, why wouldn't you?

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.