Forum: Vue


Subject: VueInfinite && P5

meselfr opened this issue on Mar 15, 2005 ยท 6 posts


meselfr posted Tue, 15 March 2005 at 5:40 AM

Can you now import two models in a PZZ with the same material names and have them import correctly. In VuePro4 if you imported two V3s in the same scene they both ended up with the same textures, so you were forced to import them seperately... has this been fixed?


agiel posted Tue, 15 March 2005 at 6:58 AM

I am afraid to report that bug is still there :( On the bright side, they improved other aspects of Poser imports, such as the Bump value set at -.08 (can now be set to whatever you want). There is also an option to collapse automatically all identical materials - useful when you want to apply the same settings to all these body parts with the same texture map.


meselfr posted Tue, 15 March 2005 at 5:27 PM

booo hooo.... I know they fixed the crummy white halo on transmaps.. 1 for 2 ain't bad... Maybe they will fix the other in an SR... :)


meselfr posted Tue, 15 March 2005 at 5:28 PM

BTW thanks agiel for your response...


agiel posted Tue, 15 March 2005 at 6:15 PM

On a side note, I got confirmation from the developers at e-on today that the problem with textures is actually a problem with the SDK provided by Curious Labs. Apparently, it was meant for one poser figure at a time. Something I observed though. I tried to import a poser file made of 3 vickies : one with one texture (A) and two with different morphs and the same texture (B). If I just import them with default options, all 3 vickies end up with texture B. If I use the option 'Group figures as single meshes' when importing from poser, then the textures are preserved (but the individual body parts are lost). However, now the two vickies with texture B share the same materials. So... it is not perfect but it is still a workaround - as long as your figures are not using the same textures, you have to group them as single meshes if you want to go around that bug.


meselfr posted Tue, 15 March 2005 at 6:29 PM

Thanks... That actually clarifies a lot... Maybe they will update the SDK when P6 comes out? Can only hope... :)