Re: [K3d-development] RE: K3d-development digest, Vol 1 #654 - 3 msgs
Brought to you by:
barche
From: Timothy M. S. <ts...@k-...> - 2004-06-24 08:27:25
|
Joe Crawford wrote: > It seems to me though that the mesh input would just be one of several. > In your example there were two, but that didn't include a material, or > other inputs. XSI does this extremely well. Makes the software very > powerful/flexible. > > Seems that having the instance have several inputs would allow one > instance of a cylender to be brown, while another had a white material > white. Both share the same mesh though. Yes, a mesh instance object includes several properties: * A mesh input * A transformation input * Viewport visible * Render visible * Cast shadows * Motion blur * SDS subdivisions Material isn't one, because our mesh datatype has a relatively high granularity when it comes to materials - a mesh is an arbitrary collection of points, curves, patches, polyhedra, etc. and materials can be assigned to various combinations. Note that this isn't a problem, for your scenario of multiple instances with different materials we already have the SetMaterial filter that overrides material choices in a mesh. There are more updates in CVS, object properties is starting to look pretty good - I'm really pleased with the performance when it comes to building complex property sheets, and collapsing / expanding categories have come together nicely. Cheers, Tim |