Has anyone else had a problem where the texture domains reassigned themselves? I'm working on yet another scout ship (see attached) in C5 and just had the texture domains scramble on me. I have a single shader since most of this is a single object so far broken the root level is a layer list with each seperate domain "broken out" by parametric mapping. Everything seemed fine until I added another section to an existing domain and they all seemed to scramble up. Each domain has a seperate name, not 1, 2 or3 etc. Selection by domain selected the areas as they were redesignated. It only took a few minutes to put the domains back to how I wanted them, but I was wondering if anyone else has had this problem? mike

I have had problems which have a similarity but yours sound as if needs to be urgently sent as a bug report to Eovia--please. They really like screen shots-of your shader room in this instance. No doubt in my mind of an "integrity retention" problem in the shader room-or, at the very least, a new way of working the shader room which has not been explained.

bwtr

I don't know about C5 but I have had problems with shading domians getting messed up in C4