Sat, Nov 30, 10:27 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 30 5:12 am)



Subject: texture maps


basarav ( ) posted Thu, 22 February 2001 at 11:15 AM ยท edited Sun, 18 August 2024 at 6:01 AM

hello i am having a lot of dificulties importing OBJ files and 3DS files when i import the OBJ from poser VUE does not get the textures from the MTL file, and when i try to put it on the OBJ inside VUE the texture map never fits right why??? and when i get textures from other programs like Bodypaint and map the to a figure they never get mapped right can any one help me please the VUE tech support blames it on all the other programs exept VUE and that is no use to me please help and thanks Basarav


KateTheShrew ( ) posted Thu, 22 February 2001 at 12:21 PM

The reason VUE doesn't get the textures for the .obj from the .mtl file is that the mtl doesn't put the full path in the file. What you have to do is either correct the .mtl by opening it up and typing in the full path for each texture, OR (and this is a lot easier, believe me) put all the textures for the .obj in the same folder as the .obj file. Vue should then be able to import the fully textured model. So, you see, in this particular case, they're right - it IS the fault of the program that EXPORTS the model and makes the .mtl file. Hope this helps. Kate


basarav ( ) posted Thu, 22 February 2001 at 6:32 PM

thank you very much i have tried it and it is great it works but how how do you open the MTL to change it???


Varian ( ) posted Thu, 22 February 2001 at 10:50 PM

Just open it in a text editor, make the changes, then save it as plain text -- but don't change the .OBJ extension of the file. :)


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.