[Bf-committers] Bug or Feature in the Texture IPO curves?

Tue, 10 Aug 2004 12:05:20 -0400

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C47ED2.4EE9E5C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm preparing some overlays for broadcast, and I'm making use of the new =
IPOs for Normal, Secularity and Hardness... but I noticed that the IPO =
only afect the texture placed on the first channel, while the texture =
that I would like to afect is on the second chanel :(

For the time been I found a work around to my situation by using the =
stencil option and moving the FXs texture into the first chanel, but =
maybe you would like to check on this "feature" ?

Apollux.

------=_NextPart_000_0009_01C47ED2.4EE9E5C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'm preparing some overlays for =
broadcast, and I'm=20
making use of the new IPOs for Normal, Secularity and Hardness... but I =
noticed=20
that the IPO only afect the texture placed on the first channel, while =
the=20
texture that I would like to afect is on the second chanel =
:(</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>For the time been I found a work around =
to my=20
situation by using the stencil option and moving the FXs texture into =
the first=20
chanel, but maybe you would like to check on this "feature" =
?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Apollux.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0009_01C47ED2.4EE9E5C0--