On 06.03.2007 13:17, Sebastien Marchal wrote: > I will fix that by using an existance check on the hilite color. > But that does not sound like the right way in general.
It depends; using an existence check means that no shader assembly code for the addition will be emitted... however, whether a single instruction less has any measurable impact is another question. > I am not up to speed on modern GPU speed optimisation, but > in term of functionality, would'nt it be better to allow some shader > vars to be initialised to some default value when the material > referencing it > is created ? This is already possible: add a shader variable to the shader itself (an example for the XML to use can be found in e.g. splatting_scattering, the very beginning). A material SV will override a shader SV; so if you add one to the material, this is the one used. If you don't add one, the value defined in the shader is used - so it just acts like a default value. -f.r.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
