Model.shaderList() and lightwave export 2003-11-16 - By andries odendaal
Back
thanks so much for taking the time to post such a comprehensive reply.
>1. Don't worry about the order of shaders in a model. Its highly unlikely
>they would ever be consistant, small changes to the source file might result
>in wholesale changing of the shader order. Instead then you need to write
>your own manager, to control the shaders in a conveient manner for your
>project.
this is what I have at the moment and it works ok, but felt that this was an
extra step I could do without if I could just export
the models correctly ... but guess not.
>You could try using loadfile, but I'm suprised that you can't prevent
>duplicate shaders. Perhaps this is a bug i've not come across as I don't use
>clone very often.
yep also found it a bit strange ... say I have a model in the scene, with a
shader called "myShader" ... and delete the model,
modelresource and all shaders, textures, modifiers etc. When I clone that model
back into the 3d member, then the new model will
have a shader called "myShader-clone1" and so on even though testing for shader
("myShader") proves false ... so this had me a bit
baffled.
> 2. Rebuild the meshes.
thanks for the extensive walkthrough ... will definitely give this a try as
soon as I have some time on my hands ... it seems like
quite a work around, but I'll be interested to know whether this works ...
thanks so much (again)
a.
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
Dir3d-l mailing list
Dir3d-l@(protected)
http://nuttybar.drama.uga.edu/mailman/listinfo/dir3d-l
|
|
