Here are the results of my attempts to import a saved P5 file into Vue 4.1 and open the same file in Poser 4 with Pro Pack. The Poser 4 result is no surprise but how do you solve the problem without having duplicate files all over the place? The Vue result did surprise me. Only the skull cap imported and even so, Vue said it couldn't find the texture. (Note how MOST programs don't freeze just becuase they can't find a file...but that's another issue.) Can anyone provide any insight?

You might need to edit the saved file to point to the real address. Replace RuntimeGeometriesP5NudeMan.obj With something like c:Poser5RuntimeGeometriesP5NudeMan.obj If that works for the obj file it may also work for the textures. I don't have Vue or P5 yet, but that's my guess. Good luck.

...as to why (maybe) the Vue import isn't working. Again, the file was created and saved in Poser 5, I used nothing from Poser 4 in making this scene. Yet, when importing to Vue, Vue looks to the Poser **4** directory for the texture! How can that be? It didn't look there for the prop itself? The bottom pic is the result after I pointed Vue to the correct location for the texture.

Cross-post with Roy. I never tried to edit a pz3 file, didn't know you could do it. Speaking of the pz3 file, this one contains Don, the hair, shirt and shorts. It's over 19 megs in size.

Just book marking this thread. :)

Trying to import a pz3 file with dynamic hair attached is going to get you similar problems no matter what. I don't know how Vue looks for the textures, but in Bryce, if you try to import a P5 exported obj that has dynamic hair included, it turns the entire head black and still no hair, just the skull cap. Have you tried importing it without the hair? Does it make any difference at all? Does Vue have a preferences where you previously set it to look in the Poser 4 directory? (grasping at straws)

Yes, Jelisa, I tried the same file without hair. Vue acted just as if it was importing, but when it was done, there was nothing there. No, Vue has no such preference. When you select Import in Vue it always looks to its own directory for the file. You have to point it to the right location. Here's the good news: I did another P5 scene but this time with P4 characters and hair. Mike 2 with the wedge cut and Posette with P4 hair. The pics shows the result...no hiccups in Vue at all. One strange thing, tho. P5 tried to find the wedgecut texture in the same directory as the hr2 file. I had to redirect it to the textures directory.

Sorry, forgot the nudity flag on the above post.

What if you saved it back to P4 and import into Vue? Are the new P5 figures exportable to P4? Or would this just be defeating the purpose. Vue needs to update or they'll lose business with all the new P5 users.

Give them time. P5 was JUST released. I'm sure Vue has an update in the works, or perhaps even a new version entirely.

You should be able to edit the path Vue looks for Poser in. If I remember correctly, Vue prompts you to select the path to poser, I think there's a menu option to edit that path.

It's fairly easy to edit the PZ3 file with notepad. Be aware the obj file references may appear more than once.

Also Poser has two ways of referencing files. One way is putting in the full path like this
c:Poser5RuntimeGeometriesP5NudeMan.obj

The other way is like this.
Geometries:P5NudeMan.obj

Note in the second example most of the path is left off, and the separators are colons instead of backslashes. Poser assumes everything is below the Runtime directory.

Heya, Jackson.. Just out of curiosity, in the pic up there, is she now holding Mike's heart in her right hand? (Snicker!)

heyas; i think you forgot one important thing. when you first tried to use the vue pz3 importer, it asked you to find your poser.exe. and you pointed to the p4 poser.exe, right? well, it's using the poser poser.exe to read your file. unless maybe you installed over top of your poser 4. maybe.

Well, there is a =rumor= that CL and E-on are talking, and looking at P5 import ability for Vue 5. Note the word =rumor=. But oh, would that frost Corel... Of course there's no telling. One of the 3rd party programmers might just come up with a utility to do it for us...

whbos & Kate: I just read recently Vue 5 is in the works and that e-on and CL are collaborating on poser import. okcdude: Yep, Vue allows you to change the path when it can't find a file. That's what I did in post #3. Roy: Thanks, I'll try it if I ever need to use P5 characters in Vue. Right now I'm satisfied that it'll read the P5 file. I'll just just P4 characters 'til Vue 5 hits. Norbert: I didn't get the Millenium Internal Organs pack :( bloodsong: Correct and, no, I didn't install over P4. Thanks all for the input. I think the answer is use P4 stuff in P5 and Vue won't have a problem. That's a lot better than no compatibility at all.