Tweet
The whole archviz industry is using more and more higher resolution bitmaps for textures. Recently, I've noticed that most of the slowdowns and issues at us are related to the bitmaps and their filtering stored in the memory.
We are using more and more textures above 2K , or 4K for our surfaces, and even the lowpoly people we use now come with 3 2K textures by default.
There was a big quality increase in the textures we see, and thus grating us more quality in the output, but the bitmap handling of MAX remained quite the same trough the years, it just uploads everything into memory.
I don't know what is handled by Vray right now, but it would be great to have a more intelligent bitmap handling, sort a like the proxies we have, on demand loading. For example before a render sequence Vray could read the bitmaps and store them in a temporary block readable file format, and read bitmap information from there during render.
If this, or something like this was requested here before, than sorry for the repost.
regards,
We are using more and more textures above 2K , or 4K for our surfaces, and even the lowpoly people we use now come with 3 2K textures by default.
There was a big quality increase in the textures we see, and thus grating us more quality in the output, but the bitmap handling of MAX remained quite the same trough the years, it just uploads everything into memory.
I don't know what is handled by Vray right now, but it would be great to have a more intelligent bitmap handling, sort a like the proxies we have, on demand loading. For example before a render sequence Vray could read the bitmaps and store them in a temporary block readable file format, and read bitmap information from there during render.
If this, or something like this was requested here before, than sorry for the repost.
regards,
Comment