Wed, Jan 15, 9:04 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 30 8:14 pm)



Subject: Vue doesn't import whole poser file


mariajudyta ( ) posted Tue, 09 December 2008 at 6:29 AM · edited Wed, 15 January 2025 at 8:57 AM

Hello!

I made an interior with vue, then a woman in Poser.

I wanted to import the woman, but the ARMS ARE MISSING. Can someone explain to me, what I have done wrong?

Mariajudyta


Peggy_Walters ( ) posted Tue, 09 December 2008 at 7:55 AM

What figure?  Did it maybe have a transparency map applied to the arms? 

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html


mariajudyta ( ) posted Tue, 09 December 2008 at 8:14 AM

It is called JESSIE and she's in the gun-fight pose.

But when I render the poser file, the arms are stil there, they are only missing in vue

It seems like the whole body is missing in vue, but due to the fact that the woman is dressed, it looks like only the arms are missing - only the head and neck is visible.

Where can I see whether a "transparency map" is applied?

Mariajudyta


Rutra ( ) posted Tue, 09 December 2008 at 8:47 AM

As you know, in Poser you can have two independent levels of invisibility: on the preview and on the render. It may be invisible in the preview but visible in render. If you set it invisible in preview, then these parts are not imported to Vue.

If this is not your case, then I can only imagine that your Vue is running out of memory and it's becoming unstable...


mariajudyta ( ) posted Tue, 09 December 2008 at 9:07 AM

hello!

well, I also thought, maybe its because vue is running out of memory, So now I restarted vue, and loaded only the poser-woman, without any other things (landsape/interior).

But the body is still missing.

I checked the properties panel in poser and everythings checked on >>visible<<

I'm really hopeless - what can I do now? I'll try to import another poser file and look whether vue will import everythin or not.


mariajudyta ( ) posted Tue, 09 December 2008 at 9:47 AM

hello again!

it has definitely something to do with poser!

because - I've made two other figures and saved them as a normal poser file.

Then imported them to vue - in the first one only the head and hair are visible, in the second one - only the hair (???)

Then I tried to reopen them in poser - and indeed - poser also only opened the head and hair - no body is visible.

Why?


Rutra ( ) posted Tue, 09 December 2008 at 9:48 AM

So, you used Jessie, a native Poser character, right? If I remember correctly, a lot of native poser content is compressed and Vue doesn't handle that very well. Maybe that's your problem. I never use Poser native content, so I don't even know how to decompress but I know there's some utility for it and this has been referenced many times in this forum, so a little search should get you to one of these threads easily.


Rutra ( ) posted Tue, 09 December 2008 at 9:49 AM

Wow, if even Poser only opens part of the character... then it's not the compress thing. Sorry, I haven't got a clue...


Rutra ( ) posted Tue, 09 December 2008 at 9:50 AM

Maybe you could post in the Poser forum, since you seem to have narrowed it down to Poser specific.


ArtPearl ( ) posted Tue, 09 December 2008 at 9:57 AM

If the character in poser uses an obz file(compressed) rather than an obj file for the geometry, it will not import to vue.
Not likely to be your problem since the head is visible, but worth checking (there is a python script in poser to uncompress). A work around if all else fails - export the character from poser as an '.obj'    and import to vue.

"I paint that which comes from the imagination or from dreams, or from an unconscious drive. I photograph the things that I do not wish to paint, the things which already have an existence."
Man Ray, modernist painter
http://artpearl.redbubble.com/


mariajudyta ( ) posted Tue, 09 December 2008 at 10:43 AM

I guess something's really wrong with poser.

The first time, I saved the poser file als OBJ-file and imported it into vue, I could see the bodySHAPE, but from the head downwards everything was BLACK. - the textures were missing.
Only the pants were perfectly visible.

The second time, I imported the file into vue, the hands were gone, I could see this on the black shape....

OMG


mariajudyta ( ) posted Tue, 09 December 2008 at 11:27 AM

It looks like poser doesn't work right any more.

Because now, when importing to vue - it isn't able to find certain textures.

I will uninstall it and try by new installing and tell you if the problem still exists.

I hope not! Or otherwise I'll get mad :o)


Peggy_Walters ( ) posted Tue, 09 December 2008 at 11:51 AM

All of the Poser figures that come with the program are compressed (obz).  They WILL NOT import into Vue in that format.  In Poser, there is a phthon script to uncompress all the files. 

In Poser, click the Windows menu, click Python Scripts. 
Click the Utility Funcs button.
Click the UnCompress Files button.
Check the Uncompress geometry files and Delete original files after uncompressing boxes. 
Click OK. 
Now save the pz3 file and try the import again.

 

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html


thefixer ( ) posted Tue, 09 December 2008 at 11:55 AM

You're going way over the top here I think! [Artpearl has already stated the most likely cause]

It is a common problem in Vue for it to not import correctly from Poser if the poser file is compressed, it just doesn't like it!! This has been said many times in this forum and you could have saved yourself a lot of grief if you'd searched for it, anyway follow the steps below and it should work!

You need to run the "uncompress" python utility inside Poser, making sure to tick both boxes as well, then re-save your poser scene, character or whatever and then try it in Vue, it should work!

Injustice will be avenged.
Cofiwch Dryweryn.


2ni ( ) posted Tue, 09 December 2008 at 12:48 PM

Not sure it's a compress problem, currently I have a similar problem : a Poser scene with a V4, some figures (hair, cloths), and a prop : Vue imports only the prop !
Maybe it's because of the Magnets applied on the V4 ?

Even if I doesn't use poser shaders. If I make an OBJ with Poser and imports in Vue, textures are really ugly (black eyes, wrong bump...).
So I'm really tired of the couple Poser-Vue which is supposed to work hand in hand...

I have Poser 6 and Vue 6 (last releases).

It gives me the pretext to ask : Does Poser 7 work better with Vue 6 ?


thefixer ( ) posted Tue, 09 December 2008 at 12:58 PM

I use Poser 6 and 7 with both Vue 6 and 7 Infinite, the only time I have this issue is if I have put new stuff in Poser and forget to run the uncompress script!
I always also use the shaders from poser with no problems!

I don't know why you would get bad texture problems, I haven't experienced this so can't help on that score!

For sure though, the "usual" reason for missing props, bits, whatever is a compressed file somewhere in the import!

Agree it may not be in this case, but before I went down the road of a full uninstall/re-install, I would run a 5 minute script first!

Injustice will be avenged.
Cofiwch Dryweryn.


Peggy_Walters ( ) posted Tue, 09 December 2008 at 1:16 PM

I used Poser 6 and 7 with Vue 6 - no problem with V4.  But, I  use only one runtime folder.  Now I have a newer computer, so only installed Poser 7.  Still no problem with any of the DAZ figures.  V4 and M4 import fine.   Vue 6 supports Poser 4 to 7, Vue 7 supports all of the Poser programs including Poser 7 Pro.  

Things to try:  

If V4 is installed in a different runtime, try to install in the main runtime folder and try importing again.    

Open the pz3 file with a text editor like NotePad and check the paths to the obj files.   

Bumps and materials will always have to be adjusted - there is no magic setting to get everything perfect. 

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html


FrankT ( ) posted Tue, 09 December 2008 at 1:24 PM

Also make sure you have "Use External Binary Morphs" Turned OFF
That does horrible things to imports in Vue - I use Windows XP, P7, multiple runtimes and Vue 6i and I never have that problem

My Freebies
Buy stuff on RedBubble


2ni ( ) posted Tue, 09 December 2008 at 1:40 PM

@Peggy

What do you mean by the main runtime  ?
I put all my content in the Download/runtime folder because I use any of Poser content, only Daz or Rendo content.
Is the download content can make a problem with Vue import ?

Ii's really frustrated because I have many issues with Poser import. Currently if I use Poser shaders, the OpenGL preview is fine but the render is totally wrong, textures are "melted". I post a bug report for that but no solution.


Peggy_Walters ( ) posted Tue, 09 December 2008 at 2:51 PM

When I install content - it only goes to Poser 7runtime.  It's one really big folder, but seems to work OK.

I never use Poser shaders.  Please show a render of a figure you are having problems with and the bump and highlights tab.  That's where most of the problems are...

Also, think about DAZ Studio.  I don't like the interface that much, but you can customize it and it has the advantage of when you export, you can set it up to have your obj and all the needed maps in one folder.  For things like buildings that do not have any poses, but lots of too big texture maps, I find using DAZ studio better than Poser. 

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html


mariajudyta ( ) posted Tue, 09 December 2008 at 5:51 PM

hello, well....

I reinstalled poser and then made the same figure and imported it again to vue: body was still missing.

Then I've tried it a second time as object file - vue couldn't find any texture - so I had to locate all the 29 textures manually and apply them to the figure.

Complicated, but it worked. I hope, I can present my new picture and solve the problem with poser soon.


ArtPearl ( ) posted Tue, 09 December 2008 at 6:04 PM

No guarantee but there is a possibility that if you import back the object to poser save as pz3 and import that to vue, it will know where all the texture files are without you locating them one by one.

Did you try running the uncompress script? interesting to know even if it didnt work for you.

"I paint that which comes from the imagination or from dreams, or from an unconscious drive. I photograph the things that I do not wish to paint, the things which already have an existence."
Man Ray, modernist painter
http://artpearl.redbubble.com/


thefixer ( ) posted Wed, 10 December 2008 at 1:22 AM

Make sure you have Vue pointing at your Poser installation.
Run the uncompress script inside Poser and re-save [as Artpearl ha ssaid!]
Make sure your Poser import isn't using EBM's [like Frank said!]

These are the 3 most common reasons for your problem, an uninstall was prolly unnecessary!

Injustice will be avenged.
Cofiwch Dryweryn.


mariajudyta ( ) posted Wed, 10 December 2008 at 2:07 AM

hello,

but where can I find this UNCOMPRESS SCRIPT?

(what are EBM's?)

Mariajudyta


FrankT ( ) posted Wed, 10 December 2008 at 4:05 AM

EBM = External Binary Morph

My Freebies
Buy stuff on RedBubble


Peggy_Walters ( ) posted Wed, 10 December 2008 at 7:54 AM

In Poser, click the Windows menu, click Python Scripts. 
Click the Utility Funcs button.
Click the UnCompress Files button.
Check the Uncompress geometry files and Delete original files after uncompressing boxes. 
Click OK. 
Now save the pz3 file and try the import again.

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html


thefixer ( ) posted Wed, 10 December 2008 at 11:48 AM

Uncompress script Poser 7 = Scripts/Utility/uncompress poser files.
                                    Poser 6 = Window/Python scripts/Utility funcs/uncompress files.

You'll find both in your top menu bar!

Injustice will be avenged.
Cofiwch Dryweryn.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.