Ridley5 opened this issue on Jul 26, 2010 · 1724 posts
adp001 posted Mon, 02 August 2010 at 2:29 PM
Quote - i'd be fine if this case was ignored entirely for the first version. geometry switching isn't used by a lot of products, and it seems like one of those issues that can wait until after version 1.0.
Geometry switching is something that happens to an actor. So, at least for the geometry-export part it doesn't matter if the original or another geometry is used. Which material a geometry is bound to can be requested via **actor.Geometry().Polygons()[0].MaterialName() **(assuming an actor is using one material only). If more than one material is bound to a geometry, this geometry must be splitted.
Preparing materials must be done before the geometry is touched. There is no other way to find out which parts of the geometry have actually the same (Lux) material attached or needs splitting. Same name is no guarantee we have the same material - see what LaurieA wrote about her actual project. And different names may even point to the same (Lux) material after preparation, so splitting may be not required.
Quote -
i hope you and your mother are doing well.
Thanks. Surgery isdn't easy for an 88 year old woman. But she is fine now and in a good condition.