Sorry to start a new thread on the same subject so soon, but the one below has gone completely OT. I thought that I had discovered that Vue (and I'm talking 4E here) would import pz3 files from Poser 6 as long as Poser 5 was also installed. I have now found that this is only partly the case. Vue will read the pz3 file - and superficially it seems to have imported the figure successfully. But all the morph data is gone. So your figure will always have a blank expression. In fact, if you try and open the pz3 in Poser 5 you find the same thing: all the morphs are inoperable.

A very simple reason - Poser 6 saves morphs in an extra file. That is new and not implemented in Vue so far. Will take a while i guess. Same explanation for opening the things in Poser 5. P5 does not know anything about external morph files and therefore... I personally find it weird from CL to do things like that. To have extra files without a real need for it. Makes life only more difficult for all of us. Users and developers.

There is actually a need for it, as the extra file can be compressed and save a lot of room instead of saving morph information in the CR2 file. If you go into Preferences in Poser 6, you can disable that new behavior by unchecking 'save morph as binary data'.

You call that a need agiel? I think the disadvantages of something like that are much bigger than the positive aspects. In my eyes. Especially in these times when disk memory is cheap. But the good news is that it can be switched off.

I think it all started because of all of these injectable morphs. A vicky 3 with all her morphs will take a long time to load on a good machine. I can see how they would like to improve things a bit. I am not saying having a separate file just for morphs is a need in itself. They could have just enhanced the CR2 file format, make it binary or whatnot. On another note, I keep finding CL has resolved a lot of little anoying things with Poser. I like poser 6 more and more each time I use it.

Attached Link: http://hem.passagen.se/ujederstrm/index.html

Vue Esprit 5 and Pro Studio are the same versions - Pro Studio is only a bundle of Vue 5 and additional modules. So far, Poser 6 models are working fine with Vue 5 for me (as long as morph information is not saved separately).

According to someone in the Poser forum, Poser 6's behaviour in this respect can be changed under preferences, so it's not so bad as I feared.

This will all be a moot point for the doomsayers once the SDK and first SR are released.

This will all be a moot point for the doomsayers once the SDK and first SR are released. That's the hope. We'll see.

I prefer not to be a 'doomsayer' -- but certain glaring negatives can't be ignored.

However.......one shouldn't ignore the positives, either.

So far, I've found nothing negative to report in V5I. The only issue of note is that Vue Infinite requires a fairly muscular PC in order to run at its best. But that's usually true of any new software worth its salt.

And V5I is worth a lot of salt.

On the other hand -- unfortunately, Poser 6 has one major flaw that causes serious headaches for many of us.

But one has to temper that remark by pointing out that aside from that one giant flaw, P6 is a dream application.

Fix the memory issue, and P6 will be at the pinnacle.

the knees on jessi are the worst. Has anyone noticed this?

I can live with content problems in P6. To me, figure issues aren't that big of a deal. But a memory bug that ruins some of the functionality of the program is a different matter. That's a major problem.

Both sound like major problems to me and reflect the company's work ethics. To decide which is worse is moot to me since both are problems that affect me. I want great models which includes hands, knees, and shoulders that look real or better than previous versions of the software. If they don't look good I don't want them in my vue scenes. Its really that simple.

In case you don't know already, an update to Poser 6 content is available through the Content Paradise site (registration required). Go under 'Other -> applications' and add the package to your shopping cart (it is free but you have to give them your poser6 serial number). The package included several fixes to Jessy (not her knees though... but one can hope that part of her can be updated that way some other time if they get enough complaints about it).

If they don't look good I don't want them in my vue scenes.

Sounds like a decent philosophy.

BTW -- I've got other figures that I like a lot. That's why issues with Jessi don't concern me very much.

But a lack of critical functionality affects all figures across the board -- and the program as a whole. Not just one body part on one character.

A memory bug like this one is central to the entire program.

Content issues can usually be worked around without too much difficulty.

But an inability to render a scene makes all characters -- good or bad -- equally worthless.

Xeno, I could easily continue this debate on which is worse but I bow out now. I apologize for drifting from the original post. Happy renders to all.

Sa'right. ;-)

Yep, just got my first image of the blank expressions from P6 to Vue5... are there any workarounds? What about just opening the P6 in P5 and resaving? Doug

Excuse me for passing through this old thread, but I was looking through the archives and....

"Fix the memory issue, and P6 will be at the pinnacle."

No...sorry, but Poser will never be the pinnacle of anything other than the amateur market. The "pinnacle" is Autodesk, when it comes to professional figure animation. Ask Gamebryo. Better yet, ask e-frontier if the next Poser will have a *.NIF import/export plugin...or even .fbx....

Far as the problems with any version of Vue and Poser  are concerned, you can always export your Poser file as .obj and manually apply textures in Vue. In the case of (at least) Poser 6, you can use the python script for listing materials, to have them all copied to one folder, along with all relevant .obj files, as well.