Reducing texture sizes not freeing up VRAM

[Rahll]

Looking for some help. I'm maxing out my VRAM on my 2080ti in Octane for Modo. I'm on the latest release of Octane 4, and using Modo 12.1v2.

It says 5.4GB being used for textures, but after reducing all my texture file sizes significantly, it hasn't dropped from 5.4GB, even though the combined size of all my textures on disk is less than a GB. It's almost like it's reading the size every texture that's ever been loaded, but not freeing up memory when they get reduced or deleted.

Does anyone have any thoughts, suggestions, or ideas? I'm working on a big project and it's causing me a lot of headaches. Thanks!

[face_off]

Hi. Enable Out-Of-Core.

https://docs.otoy.com/ModoH/ModoPluginM ... OfCore.htm

Paul

[Rahll]

Thanks Paul, I was trying to avoid that but it seems I got some insight on FB overnight while I slept as well as to why the images take up as much VRAM as they do.

Someone mentioned, "In general (ignoring the fact for now that since Octane 4 there is possible image-compression at rendertime) your Images on your HDD are compressed. To render those images they need to be uncompressed. So for example a 4K .jpeg that is 2 MB becomes 48 MB in your V-Ram. This is because every pixel has to be accessible to provide a sample with all needed data if it hits it (not needing to uncompress first as it would slow down rendering)."

Is that generally how it works? Does it have more to do with the dimensions rather than the actual file size?

[face_off]

Does it have more to do with the dimensions rather than the actual file size?

That is correct.

Paul