Forum Moderators: wheatpenny, TheBryster
Vue F.A.Q (Last Updated: 2025 Jan 24 7:34 pm)
No idea what might have happened but I do know a couple of ways to correct it : - Open the material summary panel and correct the texture maps for the object that got messed up. - Better yet : since you are in Vue 4, try importing directly your poser character saved as a poser .pz3 file. It works much better (especially if you upgraded to Vue 4.0.1).
If they were the same character, with the same texture, and imported both as .obj, I can't see any particular reason why it might have happened. The one on the right sort of looks like what happens when you export from Poser as .3DS, though. Could be either Poser or Vue had a little "burp", or maybe it was Windows. Could have been a memory thing. Poser 4 starts acting funny after a couple of hours without rebooting, at least on my system. And of course, Vue 4's material editor often has some unique surprises here and there. ;) But, Agiel's right, it's easy enough to fix, and the PZ3 import seems to give better results than .obj anyway.
When exporting as OBJ from Poser, characters with hair, clothes, shoes, etc., I've found it's better to export each item individually -- the character, the hair, the shirt, the pants, etc. As has been said above, the best route would be to save as a PZ3, then import the PZ3 to Vue. Everything should come in complete. :)
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.