Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] General Discussion => Topic started by: arqrenderz on 2019-12-16, 14:51:50

Title: Corona and Mip-map
Post by: arqrenderz on 2019-12-16, 14:51:50
Hi,  i just saw the mention about textures and the power of 2 (Optimized memory storage of textures )
Is corona bitmap using less ram with these kind of textures right now?
Title: Re: Corona and Mip-map
Post by: maru on 2019-12-16, 18:10:52
With bitmaps being non power of two, Corona 5 uses more RAM than Corona 6. :)
Title: Re: Corona and Mip-map
Post by: Njen on 2019-12-17, 03:56:39
Hi,  i just saw the mention about textures and the power of 2 (Optimized memory storage of textures )
Is corona bitmap using less ram with these kind of textures right now?

FYI, you are incorrectly associating mip-mapping with the new feature in the daily build, when in fact the feature has nothing to do with mip-mapping. All that new feature does is improve the memory footprint of texture sizes that do not resemble the following sequence of resolution:
512x512, 1024x1024, 2048x2048, 4096x4096, etc.
Title: Re: Corona and Mip-map
Post by: arqrenderz on 2019-12-18, 16:13:33
Hi Njen, i think it was miss understanded, the question is more in the way corona is Handling textures right now, I mean is corona 5 giving optimized texture storage for textures that HAVE the power of 2 size?
Its a great feature for non power of 2 textures, because i think we have a lot of them right now and its a great optimization until we take care of our textures the right way.
Hi,  i just saw the mention about textures and the power of 2 (Optimized memory storage of textures )
Is corona bitmap using less ram with these kind of textures right now?

FYI, you are incorrectly associating mip-mapping with the new feature in the daily build, when in fact the feature has nothing to do with mip-mapping. All that new feature does is improve the memory footprint of texture sizes that do not resemble the following sequence of resolution:
512x512, 1024x1024, 2048x2048, 4096x4096, etc.