Vue 5 doesn't seem to recognize poser 7 or V4 from daz. Does anyone know if they are going to have a update to correct this?

V4 imports imports just fine on my Vue 5 Infinite

Vue5 Infinite support Poser 4/5/6 Vue6 Infinite support Poser 4/5/6/7 Victoria4 load’s fine in my Infinite 5/6

 

Mazak

Google+ Bodo Nittel 

You bunch of show off...LOL...I don't have Vue 5 or 6 Infinite....:)

Another view on the same problem.

For two weeks, I had Vue 5 Infinite, Poser 6 & Poser 7 on my disk.
I could import anything done with P7 in Vue without problems. Even V4. Just had an weird extra blue color applied to her textures, but that could be removed "manually" in the material editor.

Then, I made the mistake…
After that cool transition time between P6 and P7, since everything looked OK, I erased Poser 6 to regain a few Go…

First import, Vue refused to recognize a valid Poser with P7 (well, you know that part).
So I reinstalled a minimal P6 just to be designated as a valid Poser.
But every time I tried to import a scene, it asked me where were the textures,… for each texture !  And when I tried to put P6 application file in P7 folder to re-assign it to Vue… It crashed every import attempt. I also tried to alias P7 runtime in P6 folder, same result. Can't fool V5I that way !

Next step this week-end, I'll try to copy only the texture folder from P7 to P6 and cross my fingers, because I don't intend to upgrade to V6I soon… And I'm not thrilled at the idea of reinstalling every prop/character/whatever in Poser 6 !

I'm not very optimistic on my idea, but we'll see what happens and I'll keep you posted.
Now, if someone has a solution in the meantime… He/She is more than welcome !

PS : I'm on Mac OS 10.4.8 with the most recent build of V5I and Poser 7 (and 6…).

Well at least I'm not the only one with this problem...Hmmm maybe the update for P7 will solve this problem...Don't know when that will come out, hopefully soon:(

Last attempt failed as I thought it would…
Vue apparently search everything from P6 runtime, so it doesn't ask me anymore the textures, but can't load my scene anyway.

Maybe there's more hope from e-on, since V6I already recognize P7…

**jmc95
**had before big problems whit importing  poser content to vue6
like   sometimes   whole vue crashed    sometimes only the import ended nothing imported
sometimes   only hair imported no figure   sometimes figure imported no hair.
somewhere in forums   may be here found the fix,
in poser preferences    dont use compressed files    and   no extern morphtargets.
then    open python  and run   the   degompress files skript whitch found in the python library.
.whit setting     decompress all files  and trow away the  original compressed content.
after i did this        all poser content   has exported   whgitout no problems.
hopefylly helps ...

I have run the pythonscript and decompressed the files.  But I've not thrown away the compressed files.  Can you give me an example of what the compressed files are?  What extensions are they?

I'm on a Mac, by the way.

Thank you,
Denny

as i have   trown away the compressed files cant just go looking in runtime....
but     normal obj files are named obj    so  think those named  obz       or something
i trew them away because   noted that when i opened a library  there was 2 off  everything
and   i could not   decide whitch off those 2   was the compressed whitch the uncompressed
and as the whole ide was  to    use uncompressed files so  vue not get confused    trew away the compressed ones.
skript  can  compress all ones files iff want that later so nothing lost,

Thanks!  I'll look for those.

Me too ! Thank you !

went and opened   the python window   and    looked att the   skript command
in there they   say poser will look     for     
pzz   ppz crz cmz p2z fcz ptz hrz hdz    and some more     seem  almost all files in  poser have their  compressed   equivalents         so   iff you ran the skript    and it decompressed but left the   compressed behind   as it does  iff one not   choose  the   second option too ...
then to get rid off those    probably better   to ran the skript a second time   whit
both the   uncompress geometry files   and the delete original files after
uncompressing    selected        ... or to  be sure  all be done    run the compress all files skript
and then after that run the decompress  skript whit both decompress and   trow away  originals after decompressing  selected.     

hope    the above makes  sense   and helps..