Thu, Nov 28, 1:10 PM CST

Renderosity Forums / Bryce



Welcome to the Bryce Forum

Forum Moderators: TheBryster

Bryce F.A.Q (Last Updated: 2024 Nov 26 4:28 pm)

[Gallery]     [Tutorials]


THE PLACE FOR ALL THINGS BRYCE - GOT A PROBLEM? YOU'VE COME TO THE RIGHT PLACE


Subject: Reduceing file sise for exported models, how?


DreamlandModels ( ) posted Sun, 07 December 2008 at 6:02 PM · edited Sun, 24 November 2024 at 9:03 PM

Hi all,
I am starting to sell Bryce products now and need to know how to reduce the file sise on my exported objects. I have a suspision that the very large texture I used from export out of 3D Studio Max as .obj format has a lot to do with it. One little 9,000 polygon building has several very large .jpg's assigned to it. Do I have to reduce the .jpg files from say 4000 x 4000 to say 1000x 1000 before bringing the .obj into Bryce?  Hope this question is clear enough.
Kind regards, Tom



pakled ( ) posted Sun, 07 December 2008 at 7:56 PM

what file sizes are you getting? I've seen textures that come in at the megabyte range, so that's a possibility.

I wish I'd said that.. The Staircase Wit

anahl nathrak uth vas betude doth yel dyenvey..;)


DreamlandModels ( ) posted Sun, 07 December 2008 at 8:08 PM

I just exported one little building that was only 9,000 polygons and the file sise ended up at 99 megs. Way too large to manage. The .obj and the texture maps that I used to create this product only can to a total of about 25 megs.
Regards, Tom



dan whiteside ( ) posted Mon, 08 December 2008 at 7:32 AM

 It's the textures - a 12K poly cube, with UV coords and normals is only a 1.5 Mb .OBJ file.
A 4000x4000 RGB is 45.7Mb.
A 1000x1000 RGB is 2.8Mb.
With the .JPG compression set at max you should see another 5% to 10% reduction.


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.