"As for render times. I would claim that I have noticed a differnce in speed. That is most likely not a result of the object being cleaner but rather a lessened memory usage as a result of having a smaller object loaded. Rendering is cpu and ram intensive so more ram means logically, more speed" I'm not convinced ;)... I could be wrong on this, but that just doesn't make any sense to me. Poser creates it's own normals - at some point in the rendering process. It apparently does this prior to renders in the Preview window (which makes sense). Since it completely ignores any normals that may exist in the file, there would be no reason for it to load them, and if it did, then there would also be no reason to store them 'seperately' from the ones it creates anyway (ie. it would likely overwrite the ones loaded with the ones it generated). It might actually load the entire text file into memory the first time that it loads a model, but it creates a binary .rsr representation of the model which it uses for every time after that (and I assume that it frees the text file data). The .rsr file either contains normal vertices or not, but I doubt that that depends on whether the original file had them (I guess I could do a test to find out), and even if it does, as I mentioned, there's no reason for the program to create a 'seperate' memory storage area for the file-based normals, since it never writes those back out or uses them in rendering. When you load an .obj file and make a prop (.pp2) out of it, the normal data is stripped anyway. So it's just not there anymore. Either way, having normals in the .obj file would have zero bearing on memory footprint of the loaded object.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.