Fri, Nov 22, 6:38 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)



Subject: A quick Millie MT question


SnowSultan ( ) posted Mon, 27 March 2000 at 7:57 PM · edited Fri, 22 November 2024 at 6:13 PM

Can anyone tell me why the tongue morphs by rtamesis are well over a meg each when unzipped? I hope all Victoria facial morphs aren't going to be this big... Thanks. :) SnowS

my DeviantArt page: http://snowsultan.deviantart.com/

 

I do not speak as a representative of DAZ, I speak only as a long-time member here. Be nice (and quit lying about DAZ) and I'll be nice too.


rtamesis ( ) posted Mon, 27 March 2000 at 8:37 PM

The head is pretty high resolution, with lots of vertices, much more so that P4NW. I exported each of them as Wavefront obj morph targets.


Ikyoto ( ) posted Mon, 27 March 2000 at 9:27 PM

You can open the object files in a text editor. Strip out all the lines that don't start witha "v".


Traveler ( ) posted Mon, 27 March 2000 at 9:34 PM

yep drops them to like 25% of the original size. Even more if they were exported from poser. -Trav


rtamesis ( ) posted Mon, 27 March 2000 at 10:01 PM

Thanks for the tip.


rtamesis ( ) posted Tue, 28 March 2000 at 12:15 AM

Taking your advice, I stripped all those unnecessary lines from the tongue and butt morph obj files, reduced their file size by at least 30% and reposted them. Thanks, Ikyoto and Traveller!


Jaager ( ) posted Tue, 28 March 2000 at 5:09 AM

rtamesis: Is *.bin some kind of Mac thing? If changed to *.obj they show up. And work. Morph Masher will take your 835K obj down to 300K and they still work. Do you need some collaboration? Jaager


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.