I am working on the Ogre exporter for blender25.  The issue i am having is with 
fully supporting all of Ogre's texture-unit options, right now i store some 
options at the material level, others at the texture level, and still others by 
hijacking rarely used options in texture-slots.  Some options of texture-slot 
objects can be directly mapped to an Ogre texture unit, others can not.  This 
problem could easily be solved with custom property (IDProperty) support for 
material slots, then i can attach any data i need to the texture-slot objects 
and not have to over-ride existing options.This feature may be useful for other 
exporters as well.
-brett

_______________________________________________
Bf-committers mailing list
[email protected]
http://lists.blender.org/mailman/listinfo/bf-committers

Reply via email to