Basically, what it boils down to is that Vue -uses- the Poser executable in the import process. By doing that, E-on avoided having to create something to deal with the file handling, which would have been a nightmare if you think about what a Poser runtime tree looks like after a few gigs. Particularly if you have to do a recursive search for a texture. Poser 5 has several features that are not recognized by Vue (shaders and dynamic anything, at the moment), and the interface in Vue was hard coded to recognize -only- the validly registerd executable for Poser 4. You -can- do things in P5 and import them, but =ONLY= if you have Poser 4 also installed, and are using the content in the P4 runtime, and are -not- using compressed files (.pzz), any of the shader node tricks, or dynamics and collision. I've been told that if you manually copy the files for Don, Judy, etc, into the P4 runtime, you can use them the figures in P4 and have a back way to import them into Vue, but I haven't tried it yet, so I can't say for certain about that.