Modelling effiency, reducing file size
-
I think I see what you're talking about now. Running another test with 25 spheres I found that using a projection map created a file that was 1.3mb smaller than the same file with the same texture applied to the sphere with a non-projection map (not Whaat's sphere uv, but just the generic sloppy SU mapping) and both files were significantly larger in size than just adding the geometry plus the image files size.
What I'm still not seeing is SU preserving UV coordinates on an object after a texture has been removed. If I create a bunch of spheres I get a file of 2.0mb, map them with a 50kb image and I get a 4.3mb file. Apply the default material to all the spheres and the file size drops back to just over 2.0mb and running thomthom's cleaner brings it all the way back to original size.
-Brodie
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đź’—
Register Login
Advertisement