Quote - > Quote - Poser also behaves very stupidly in this ... if it encounters multiple instances of the same texture file (like in this case "KateShoes" and "KateShirt" etc, it just writes the file again ... and again... and again.

Are those files dated in the future by any chance?

For managing the texture cache, Poser checks the file dates of the source textures and compares them to the files dates mip maps in the cache. This way it can react appropriately when files get changed in Photoshop between renders.

That's very interesting.

The original files (Kate resource files) referenced by the pz3 are dated 13 of Nov. 2006 on my system so I can't see why that would be happening. Cause for further investigation as it really slows down this benchmark for me (clicking open some of my own pz3 files doesn't make this happen so it's an anomaly and not a norm).