When I try ot import a pz3 into vue it tells me I need to have poser installed. So I move throught window till I have poser 4 and hit enter, back comes the same window. So what be goin on now.

Close Poser before you import to Vue. That's the trick. Guitta

If I know what characters I want, I do them in Poser first, save them as pz3, then close Poser. I open Vue, create or open my scene, and import the pz3. No problems.

LOL

This does not work for me! Don't know why! I even closed down the computer after Poser5 and restarted it, result: this ugly window that tells me to get a correct registration number. So I keep on importing objs and hope for the future. Bernie BTW: I updated Poser5 - does this make any difference?

Bernie, you cannot import Poser 5 files into Vue. Only Poser 4. Guitta

Sorry I was talking about pz3 saved which where build with Poser5. Bernie

You need to save them in Poser 4 to be able to import them into Vue.

Ahhhhhh - that's hopefully the hint! I will try that and tell here how it worked! Bernie

So do you mean if you have only Poser 5 (and not Poser 4) you cannot use poser figures in View??!!!

Yes marco, that's exact:-). No Poser 5 in Vue 4.

OK...I have tried every imaginable way possible to get the PZ3 into vue from my poser files. Poser is not active. The pop up windo is still telling me that I have to have Poser installed. So what IS the problem...anymore ideas?

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.

Just got through testing it; here's the results. The HiRes Judy wearing Harvey Mann's Cleopatra power hair. P4 handles them just fine. It does throw a warning that the file has a later version number than expected, and will -try- to read the file, but it seems to do just fine. All you have to do is copy the P5 character folder into the P4 one, and do likewise for the geometry and textures. So those of us who have both versions of Poser have a few new options to play with (not the least of which is that you can actually -pose- the feet of the P5 characters...which is one of the give aways of the 'poserness' of a model)

Geez..... A. I am using Vue4. B. Poser is not running. C. I am trying to import a pz3 from Poser 4 runtime folder. D. The screen pops up and says I must have Poser 4 installed and no matter what I di it does not recognize that I have POSER 4 installed. (which is NOT running.)

Ah-HA! Is this the Metacreations P4 or the CL P4? When Meta dumped their graphics to work on web content, there were several groups of valid P4 restration numbers that didn't make the move with it. Both Vue and Poser are loaded with the invalid numbers, so that they won't work with them (the vast majority of them are the warez'ed copies of P4, but those valid numbers got lumped in there by accident). Contact CL directly about this, with your registration info, and if it checks out they will send you a replacement number that will work with not only Vue, but the latest updates to P4. If the S/N was ever warezed, then you'll have to prove you purchased the copy of Poser with a sales receipt.

My Poser 4 product was PURCHASED...and is the Curious Labs version.

Hmm... You might still want to contact CL just to be sure; they never said what the key identifiers were for the groups that got mis-identified (for obvious reasons), but if you bought it just as CL took over, you may have gotten caught in that mess. If that isn't it, the only other thing I can think of to suggest is doing a re-install of Poser in a seperate dir, and seeing if Vue finds it then. If so, your old version was corrupted some way subtle, and you could just drag your old runtime over and replace the new one. If you still get the error, it might be a Vue problem that needs a re-install....

I was able to pull a pz3 into vue sometime ago but had troubles with the textures. Someone in the forum here finally cleared that up. In the mean time one of my updates from Microsoft loaded new drivers for my graphics card. So the my open GL no longer worked. I will try putting poser on one pf my other hard drives, and replacing run time with the old one. Then if that doesn't work I will reinstall vue. I bought my copy of vue and poser about one year ago, and both have run pretty clean. Couple simple problems as a result of being a dumb newbie...but since then no problems till now.

Hm One thing you might want to do is download a copy of Correct Reference. This is a freebie program written by Hogwarden, the creator of PBooost. What it does is work its way through your runtime, and find and correct the texture pathways. It will take a bit of time, depending on how big your Poser install is, but it really helps out on the exporting (he originally wrote it because PBooost was locking up do to bad references. Poser can find them usually, as it will do a recursive search if the texture path in the cr2 is inaccurate, but exporters that depend on accurate paths get choked). It is scarey how many errors in syntax and location that CR can find....even on DAZ products. When you do the 2nd Poser install, just leave it as the default, out of the box version and see if that works. It's possible that something -in- the runtime may be having an effect (don't know what, but I've seen stranger things happen in code). If that works, then start moving your old runtime to the new one (you probably were planning that anyway, but better I say it for a newbie that might be reading... :P ). Hope this fixes things....