I've found this happening when not enough memory is available to Poser. I've only encountered this under Mac OS 9x-, where RAM must be specifically allocated to a program by the user. As I understand it, Poser fills up the available RAM with uncompressed versions of all the textures, then renders into that same space, also uncompressed, the first render. Due to it's ludicrous memory-management if it runs shy at that stage it can't recover; it deletes random texures from program memory but leaves the pointers intact (and large fragments of RAM are left permanently inaccesible). The only answer at that point is to reboot Poser (and on less-robust OS's, reboot the computer!) The answer is, as always with computer graphics, more RAM. I've found 260 megs barely enough for a fully-dressed and textured mil figure.