Fri, Dec 27, 3:43 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 27 2:49 pm)



Subject: Exporting/importing poser figures as wav.obj


beonalert ( ) posted Wed, 10 March 2004 at 2:15 PM ยท edited Tue, 20 August 2024 at 8:52 PM

I can't find the original post anymore, but someone had said that you could export a figure as a wav.obj, then reimport it into a scene. This would save a lot of memory as the figure is now a simple object with no dials. You would need to do all your posing before the export, of course, as you could not make any changes once you convert it to a wav.obj. I tried this and it worked pretty well EXCEPT that the hair was converted into a big brown mass instead of retaining it's fine strands.In addition, the transparency maps for the pubic region and eyebrows seemed to be effected as well since they ended up as solid brown smudges on the wav.obj My guess is that transparency maps don't behave well in this conversion. I'm wondering if anyone else out there has tried this with better results. I could see adding the hair after the fact and adjusting it's x/y/z position to fit the object. My real concern is with the transparency maps and textures. I don't imagine I could add the texture to the wav.obj with much success. Any thoughts or experiences with this would be greatly appreciated. Thanks all!


ockham ( ) posted Wed, 10 March 2004 at 2:28 PM

You might want to rethink the basic premise that this saves memory, before you spend a lot of time perfecting the method. Consider that a typical Poser figure has about 20,000 facets; let's say it has 40 body parts, each of which has 10 dials. So you're saving 400 "things" but still leaving 20,000. More imporantly, the CPU's hardest work is in rendering all those facets, which are still there.

My python page
My ShareCG freebies


SteveJax ( ) posted Thu, 11 March 2004 at 3:53 AM

The OBJ format looses all the transparency and reflection mapping I think I read elswhere just this evening. The only reason for exporting to OBJ that I have is if I want to render the figure in some otyher program like Bryce where I'm going to end up applying better textures in anycase.


EnglishBob ( ) posted Thu, 11 March 2004 at 6:37 AM

As long as your exported OBJ still has the original material zones (and it should have) you can re-apply the transparency settings in the materials dialogue. In fact, if you parent the imported OBJ to a small figure (which can be made invisible) any MAT poses that you have will still work on it. I think this may be a problem with the MTL file that Poser produces when you export an OBJ. It's supposed to have the material settings in it, but it sounds as if transparency is not included.


RHaseltine ( ) posted Thu, 11 March 2004 at 9:05 AM

Ockham - exporting to OBJ loses the overhead of any morphs too, which even with selective injection can be quite substantial.


maclean ( ) posted Thu, 11 March 2004 at 2:37 PM

I think it was me who recommended exporting as obj to cut down on resources in large scenes. And, if I remember rightly, you were having poser crashes with a lot of figures, so I still do recommend it. English Bob is correct. The materials and maps will all still be there. All you need to do is set the transparency slider to 100% for the appropriate materials. I don't know about parenting the objs to a figure to apply the MATs. Unless the MAT address a specific prop, it's doubtful if they will work. mac


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.