You can get some funky effects by twiddling with the framerate in Vue, if it is set for a different rate than the pz3 (open the dopesheet in Poser [that's the keyframe editor] and check the setting on the upper left; the default is 15 fps; you have to set it to 30 yourself). Vue interpolates if they are different, and that can create 'tweening glitches ('tweening refers to the computer generated frames 'between' the created keyframes. Don't you just love the buzzwords? :P ), and one of the glitches I've noticed is that you can get tweened frames where the texture simply does not finish loading before Vue shoots it to the render buffer. If that checks out, then the next thing to check is the actual pathnames for the texture files. Poser content has a long and bloody history of bad file references; the recursive search function in it makes it easy for people to be sloppy in that regard. It works on their system, so it must be all right....only it many times isn't. It doesn't matter with Poser so much, but output to a program like Vue depends of all the paths being exact (including punctuation and capitalization, which is where 95% of the screw-ups occur). However, these are based on experience with Windows; if this is a Mac related issue, I'm lost...