Sat, Nov 23, 6:05 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 21 4:12 am)



Subject: Question about multiple Poser figure import...


argoforg ( ) posted Fri, 02 July 2004 at 12:03 AM · edited Sat, 23 November 2024 at 6:00 AM

Has anyone had this problem in Vue and know a workaround? I'm currently using Vue (not Pro) 4.2 upgrade in conjunction with Poser 5. I'm not sure if this has been happening since before I upgraded, but I know it's happened since the last upgrade.

I compose a scene in Poser 5 with a pair of Vicky (or Mike) models-- with full textures-- interacting. I save the scene as a PZ3 (or PZZ.. file format doesn't seem to matter) and then import it into Vue.

For some reason, I get both figures importing with the same texture. In the material list, I get one skinbody, one skinhead, one texture for lips, eyebrows, etc. And if I select by material, the same areas on both models highlight. Both hair models have their own individual textures, as do any clothes they're wearing, even if the clothing is the same. Just the people models have combined textures.

Natch, any touchups or texture work I do to one figure in Vue now affect both (I've done a few statuary pictures by using Vue's better stone materials, so this is particularly irritating if I don't want both characters to be made of inanimate material!)

For the time being, I've had to make do by exporting the individual figures as PZ3's, and then importing multiple scenes (and resizing, moving, etc, as needed) but that's a stopgap measure, at best. Does anyone know of a workaround for this? Should I open the PZ3 in a text editor and change the second characters' material zones to skinbody2 and the like?

Message edited on: 07/02/2004 00:05


Brewvet ( ) posted Mon, 05 July 2004 at 5:50 PM

If both figures have the same texture in Poser then, yes, they will import identically. To have two instances of the same texture on different models will require you to import one as an individual PZ3, alter the tex as you see fit and THEN bring in the second figure. Any textures from the first that you don't alter will be, again, identical and shared. This prevents Vue from having to import fifty billion texture files when you have several characters that share texture maps. If you changed the texture settings in Poser before saving as a PZ3 then the changes will be reflected when you import them into Vue. That isthe easiest way of making certain that your characters have different textures. (Or use a different tex map in Poser, or, alternately, rename a copy 'Vickie Tex 2' for instance and apply THAT texture to Vickie number 2. As far as Poser and Vue are then concerned the texture maps are different, even if they are not.) You can also NOT import as single mesh, click on each individual body part (Once you have the figures placed to your satisfaction) and edit the body part. This SHOULD (not always- don't ask me why...) enable you to select each portion that has a different texture map and if you open it in the material preview (not material summary) you can edit it to your heart's content. Hope this helps a little bit. MN


argoforg ( ) posted Tue, 06 July 2004 at 9:43 AM · edited Tue, 06 July 2004 at 9:48 AM

Thanks for the response, Brewvet! I won't say that didn't help, but I think I might not have explained myself very clearly on this, myself. It's not so much a case of having the same texture with different tones, or bumps... then I could understand why Vue wouldn't have the same texture twice. The models I've imported already have distinctly different textures applied in Poser before I import, and then when they import into Vue, one texture gets 'pushed aside' in favor of the other.

I don't have a visual in front of me, but I'll work on one tonight if I have a chance to try to clear everything up. Let's say I use a texture MAT pose map for one Vicky named 'Lucy', which applies Lucyhead.jpg for the skinhead and Lucybody.jpg for the skinbody (as well as everywhere else on the poser figure). For my second Vicky I use a texture MAT pose named 'Julie' that applies Juliehead.jpg for the 2nd model's skinhead, and Juliebody.jpg for the skinbody (et al). I render a test in Poser, and all is well... both models have individual and distinctly different texture maps. I save this file as a PZ3.

When I open that PZ3 in Vue recently, both models have the Lucy textures applied to them, and if I open the material list dialogue, only the Lucybody and Lucyhead Jpegs appear to have imported... and these are applied to both Vicky models in the scene.

This doesn't happen if, for instance, I use a Michael and a Vicky figure, or a Stephanie and a Vicky figure. Only when I use two of the same base model... two Vickys, two Michaels, etc. For the time being, I've worked around it by using a different PZ3 for each model, but that seems a bit iffy when the scene has them interacting. If this has happened to anyone who can explain it a bit better than me, or who has a better way around that bug, I'd appreciate the help.

Message edited on: 07/06/2004 09:48


kristinf ( ) posted Fri, 03 September 2004 at 5:56 AM

I get the same problem, any new thoughts on how to fix this?

"I am extraordinarily patient, provided I get my own way in the end" - Margaret Thatcher 1989


argoforg ( ) posted Fri, 03 September 2004 at 8:36 AM

I've talked to support at e-on and thus far they've suggested that the development team will be informed about it. I'd imagine that Vue 5 won't have this problem, although that doesn't help us right now. For the time being, the only workaround I've seen is importing two (or more) PZ3's. But if anyone finds a different workaround, I'd be interested in hearing it, as well.


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.