Mon, Jan 6, 10:09 PM 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: Poser import


runwolf13 ( ) posted Mon, 17 February 2003 at 12:18 PM · edited Mon, 02 December 2024 at 11:36 AM

I just did a poser import, and it seems the textures I so carefully created in Poser didn't move over to Vue. Is there some trick to this? Thanks, Mike. P.S. I've yet to install Mover, would mover help with poser import? I've not gotten to the point of animations yet, so I haven't done anything that way just yet.


gebe ( ) posted Mon, 17 February 2003 at 12:21 PM

No trick. You have to import your poser 4's in Pz3 foormat into Vue. All textures, transparencies and bums will come right. Poser has to be closed while you import to Vue. Guitta guittalogo.GIF


runwolf13 ( ) posted Mon, 17 February 2003 at 1:57 PM

Hmmm... Did a poser 4 import, but poser wasn't closed. Might be the problem. I'll try it again.


runwolf13 ( ) posted Mon, 17 February 2003 at 2:23 PM

file_46488.jpg

Here's an attempt to bring in the poser file. The creepies are fine, but my priestess doesn't have her hair color or her clothes color, plus the skin texture is wrong.


gebe ( ) posted Mon, 17 February 2003 at 2:33 PM

San Francisco hair, as you know, only works in Poser when you do an anti-aliasing Render. Don't try to export this one. It will not work in any other application then Poser. Update your Vue copy to 4.12 or at least to Vue 4.11. These texture problems existed only in Vue 4.06 and earlier. Guitta


runwolf13 ( ) posted Mon, 17 February 2003 at 2:55 PM

I'm using 4.12 and no, I didn't know that the SanFran hair didn't work outside of poser. Thanks for telling me that. I suppose I could render the background I wanted in Vue and import into poser for rendering? This is very upsetting and frustrating.


runwolf13 ( ) posted Mon, 17 February 2003 at 2:58 PM

file_46489.jpg

Here's a render from poser on the default background of what I'm trying to get in Vue. Well, except for the lighting of course.


eric501 ( ) posted Mon, 17 February 2003 at 4:13 PM

Are you using poser 4 or 5?


runwolf13 ( ) posted Mon, 17 February 2003 at 5:46 PM

Poser 4 on a Mac. Now Pro Pack at this time.


Spit ( ) posted Mon, 17 February 2003 at 8:12 PM

Those are subdividing mats. I asked about those over in the Poser forum and they said they worked ok to Vue. But that might be the problem here? And why won't the hair work? It has nothing at all to do with antialiasing..that just makes it look okay, has nothing to do with substance. Does it have separate layers of transmaps? Maybe Vue can't handle those.


runwolf13 ( ) posted Mon, 17 February 2003 at 8:24 PM

Here's a thought. I've poser on my older computer, which runs natively in OS9. I then mount that hard drive on my newer computer, where I run Vue. I then pointed Vue to the copy of Poser on the other machine. I don't know why that would matter, but maybe there is some cross talk problem across the network that won't let me import poser properly into Vue?


Spit ( ) posted Mon, 17 February 2003 at 8:29 PM

I just saw some other vue pics with subdividing mats, so that's not it. Maybe it's not picking up the textures then because of a path problem it can't figure out.


Dale B ( ) posted Mon, 17 February 2003 at 9:49 PM

Odds are that it is a pathing problem. Do a search in the Poser software freebies for 'Correct Reference'. This is a little proggie that Hogwarden created in response to some problems that his PBoost program was having. Poser does a recursive search for textures throughout the Texture folder in runtime when it can't find a proper path for it. Vue doesn't have the ability to do this; it has to trust that the path in the PZ3 file is accurate. Correct Reference does a search of the entire texture tree, and locates all of the paths that do not lead to what they claim, then lets you locate the proper files and it will correct the paths where needed. And trust me, you will be apalled at the number of incorrect paths you are going to find. If you do this and have a multigig Poser runtime, plan on going away for a few hours (it's not that C.R. is slow; it's that it has so much work to do).


runwolf13 ( ) posted Tue, 18 February 2003 at 12:57 AM

With this program work on a mac?


wabe ( ) posted Tue, 18 February 2003 at 2:07 AM

Hi, Poser textures in Vue on a Mac - we had long discussions here about that. We found out, that mostly the problem comes because Vue is not able to deal properly with subfolders in the texture folder of the Poser texture folder. Or, even bader, when you have the textures somewhere else than the defaults! I haven't checked that on Vue 4.12 but it looks like that the problem is still there. What you can try out is, to copy the textures into the folder "bitmaps" inside the Vue program folder or leave all textures on one level in the Poser texture folder. TheWingedOne is someone here at Renderosity who knows surely a lot more than i do about the Poser Vue connection on a Mac. Maybe he can say a word (or two). With my very basic needs while importing Poser files into Vue, i haven't had any problems. But as i said, i only do very basic things in Poser.

One day your ship comes in - but you're at the airport.


gebe ( ) posted Tue, 18 February 2003 at 5:03 AM

"Notes on rendering in Poser: Anti-aliasing must be turned on." This is an extract from the readme file that goes with Sanfrancisco hair. It effectively doesn't work if rendered un-anti-aliased in Poser. This is the reason why it doesn't work outside Poser. Guitta


Dale B ( ) posted Tue, 18 February 2003 at 7:19 AM

Sorry runwolf, C.R. and PBooost are both Windows apps. Creating a dump folder for copies of all your textures could be the next best thing, though. I used to do that in my Bryce days, just so I would have the obj. export and all the textures in the same folder.


Spit ( ) posted Tue, 18 February 2003 at 8:52 AM

I have 4.61 gigs of textures in Poser. 13,137 files. I ain't gonna put those all one level. LOL But I've run Correct Reference on everything so that might help. Maybe there's a path length limit though. Some of the directories are nested pretty deep. Sigh. Gebe the necessity for anti-aliasing has nothing to do with whether the hair works outside Poser or not. But I just checked the template for San Francisco hair and it is in layers. So it's possible, depending on the material names, that the transparencies might not match up properly with their layers in an application outside of Poser.


wabe ( ) posted Tue, 18 February 2003 at 8:58 AM

Your decision :-)) But maybe you try it with the one you have problems with here first. And see wether this helps. Then you can decide still what to do. I dob't think it has to do with path length limits. But hopefully you find out something new! Would be great!!

One day your ship comes in - but you're at the airport.


Artalgo ( ) posted Wed, 19 February 2003 at 11:40 AM

file_46490.jpg

Just a note on the San Francisco hair in Vue, I've never had any problems importing it into Vue from Poser 4 (or 5) in a .pz3 file. This picture is cropped from one of my Vue 4 renders that used the San Fran hair and as you can see it doesn't look too bad. (I should mention that it was rendered at the Ultra setting.) I should also mention that this was done on a Windows machine and not a Mac, in case that makes a difference.


gebe ( ) posted Wed, 19 February 2003 at 11:44 AM

I did not say that you cannot import it into Vue, but it looks like wool, not like hair as in Poser:-)


TheWingedOne ( ) posted Tue, 25 February 2003 at 8:03 AM

Runwolf13, check out this thread. This should answer all you Poser-import-related questions. If you have further questions just IM me and I'll be pleased to help you out. Phil


TheWingedOne ( ) posted Tue, 25 February 2003 at 8:03 AM

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=976269

Ooops, sorry I missed the link. Here we go!


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.