Quote -  Maybe I am wrong... all I know is that my computer does not seem to like all of the 

Image_Map_3

Texture "ImageMap_85" "float" "imagemap"

"string filename" ["C:UsersClayDocumentsDaz 3DStudio3ContentRuntimetexturesMorrisHiro4JMHiroLimbB.jpg"]

"float vscale" [-1.0]

"float uscale" [1.0]

"float gamma" [1]

over and over again with the only difference really being the number attached to the "ImageMap_

and when I get rid of all those and make others point to first ImageMap_85 with the file attached it works, when I leave all the others in it crashes... and now that isn't the only one that does it for, just an example of one of the images that comes up over and over again in the lxm file.

Like ADP said, Lux claims to be reusing image memory when it comes across the same image more than once. But it's possible that it stores an extra pre-processed copy for each texture that image is used in. It would then be up to the exporter to optimize what's in the lxm file.

Unfortunately, that's bagginsbill's department, and we haven't heard much from him lately. Even if he's aware of this problem, it might not be too high on his agenda, as there is still so much else to be taken care of. Maybe someone should add it to the wishlist?

-- I'm not mad at you, just Westphalian.