That's right. The Canvas3D textureUnitStateMax property gives you the number of texture units supported by the hw. So if the number of texture unit states specified is greater than textureUnitStateMax, COMBINE mode will fall back to REPLACE.
Charmaine Lee Sun Microsystems > Date: Tue, 04 Jun 2002 00:06:29 +0200 > From: Artur Biesiadowski <[EMAIL PROTECTED]> > Subject: Re: [JAVA3D] Multitexturing combine bug ? > To: [EMAIL PROTECTED] > MIME-version: 1.0 > Content-transfer-encoding: 7bit > X-Accept-Language: en-us, en > Delivered-to: [EMAIL PROTECTED] > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9) Gecko/20020311 > > Charmaine Lee wrote: > > > It is a limitation with multipass texturing in Java3D1.3. > > TextureAttributes.COMBINE is not supported with multipass > > texturing, ie, if number of texture unit states > number > > of texture units supported by the hw, TextureAttributes.COMBINE > > will fall back to REPLACE. > > And textureUnitStateMax Canvas3D property will give this number, or some > kind of total number of unit texture states for non-combine combinations > ? If former, then how can I detect how many units can I use safely with > .COMBINE ? > > Artur > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff JAVA3D-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
