Sat, Oct 5, 9:27 AM CDT

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Sep 26 4:27 pm)



Subject: P5 into Vue...can anyone figure this out?


Jackson ( ) posted Tue, 10 September 2002 at 11:40 AM ยท edited Sun, 04 August 2024 at 8:54 PM

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=862620

file_23186.jpg

I'm trying to figure out why Vue isn't importing a P5 file I made. The file contains Don, the hair, shirt and shorts. Yet all that Vue brings in is the hair's skull cap. This is a screen cap of the msg I get upon import. Why in the world would Vue look to the Poser 4 directory for the texture? It didn't come from there. And Vue found the skull cap prop in the right place. I used P5 exclusively in this file. Nothing was brought over from P4. Any ideas? Please see link for a more detailed thread about this.


gebe ( ) posted Tue, 10 September 2002 at 12:01 PM

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12368&Form.ShowMessage=862066

Have a look to this started thread. BTW, nobody said that Vue can import Poser 5 files yet:-) Guitta


Jackson ( ) posted Tue, 10 September 2002 at 12:51 PM

file_23187.jpg

Of course not, Guitta. I didn't think it'd work myself but guess what? It does work (as long as you use P4 figures)! I just did this attached test to see. Everything was done in Poser 5 but everything in the scene is Poser 4. It came into Vue without a hiccup. What I was asking in the above post wasn't about the import per se, I was asking if anyone could figure out why Vue would look inside the P4 folder for the textures. It seemed strange, especially since it found the prop in the right place (the P5 folder).


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.