Wed, Jan 29, 11:39 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2025 Jan 24 7:34 pm)



Subject: Poser Objects in Vue3


tryten ( ) posted Mon, 03 July 2000 at 2:31 PM ยท edited Wed, 13 November 2024 at 8:46 AM

My problem, I can't open a Poser obj. File in Vue3 with original textures. Is it possible? Thanks for your messages.


arcady ( ) posted Mon, 03 July 2000 at 5:03 PM

Do you have the 3.1 patch? If so you can import an obj file directly with all but the transparency channel of the textures intact. You have to add transmaps back in by hand. With a y-scale of -1 AND the filter flipped (high to low instead of the normal low to high, this inverts the colors to a negative image). If you don't have the 3.1 patch you have to do it all by hand and resave your texture images to jpg format first. I'd get the patch; it's free to registered owners of Vue 3.

Truth has no value without backing by unfounded belief.
Renderosity Gallery


bloodsong ( ) posted Mon, 03 July 2000 at 7:43 PM

heyas; also note that the obj you saved from poser has to be in the same directory as the texture maps you are trying to use. alternately, before you import it into vue, you can edit the mtl file and put full directory paths into the slots where the image files are listed. arcady: y-scale of -1 for trans? havent heard of that technique. does that go in place of the 'mirror y' and offset by the y image size?


smallspace ( ) posted Mon, 03 July 2000 at 11:56 PM

You know, even with all the support the 3.1 patch has added for importing obj format, I still find it does a better job importing 3DS. I find I have better results exporting 3DS from Poser then importing into Vue.

I'd rather stay in my lane than lay in my stain!


bloodsong ( ) posted Tue, 04 July 2000 at 1:08 PM

heyas; that's funny, small, because i've found the opposite is true. i tried 3ds for a while (because pre-patch vue imported it with textures etc), but i get better results with obj. weird. :)


arcady ( ) posted Wed, 05 July 2000 at 11:14 AM

for me 3ds works on some poser objects and not others. I've had some come in with seams still. I always try to get it in as a 3ds though because it comes in as only one object so Vue works with it faster. And yeah, the -1 thing is the same as mirror and offset. If you look at an obj file import under the patch E-On uses the -1 technique. Which was were I got the idea. The full directory paths thing sounds like a great idea. I'm sick of having to have multiple copies of all my textures. I've always had this long proceedure of copying all the textures to one directory. Putting the obj file there. Then opening it so I don't get errors on opening, Then editing the materials to point to the proper directories and saving out a .vob. Finally deleting all my duplicate textures. As you can imagine that's a pain to do...

Truth has no value without backing by unfounded belief.
Renderosity Gallery


smallspace ( ) posted Wed, 05 July 2000 at 11:48 AM

bloodsong: Do you "un-parent" all your props (including hair) before exporting from Poser? I've found that makes a world of difference. I will say that most of my Poser exports wind up going into Truespace for further tweeking before I put then into Vue. It may be that Truespace does a better job of exporting 3DS than Poser.

I'd rather stay in my lane than lay in my stain!


bloodsong ( ) posted Wed, 05 July 2000 at 7:18 PM

um.... haven't really done anthing in vue with props, small. :) probably wouldn't think to un-parent anything; why? arcady: cool, i'll try the -1 thing! yeah, i keep my textures in my poser geometry folders, and would save the exported obj's there to get vue to read the textures. since my poser drive is full enough already, this isn't such a hot idea! :)


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.