If you were wondering why VRayHDRI now allows you to load other image file formats like JPG, PNG etc, here is a part of the explanation.
Below is a scene that was rendered on a dual Intel Xeon 5660 machine (2x6 physical cores; 24 logical cores). I rendered it once with the standard 3ds Max Bitmap texture. Then I rendered it again with the textures converted to VRayHDRI (but without converting the files to tiled OpenEXR files - just using the original bitmap files).
Can you find the differences
Best regards,
Vlado
After some more tests, the slowdown for the Bitmap texture appears to be caused by the bitmap pager being enabled (which it is by default).
If you mean why the Bitmap texture is so much slower, I don’t know. I installed the service pack for 3ds Max 2011 and the new hot fix 4 before testing too. In any case, it is an issue that has been bothering me for quite some time. As we can’t really fix the standard 3ds max Bitmap texture, we extended VRayHDRI instead.
The slowdown for the Bitmap texture seems caused by the bitmap pager; when it is disabled, the scene renders much faster. Then again, VRayHDRI also supports texture loading on demand, without the slowdown.
No, unfortunately I cannot. It is from the Evermotion Archmodels’09 collection. But I guess one of our artists can probably re-create something similar…
Well, you don’t have to, but you might get faster renders if you do. The Bitmap texture still produces correct results and I don’t think the difference is that drastic on machines with fewer cores (although some tests would be good to do).
This looks like a big step forward. So Vlado are you saying VRayHDRI uses more cores compared to original bitmap texture. Where does that difference comes from, from filtering or how it’s accessed on HD? So basically if I understood it right VRayHDRI won’t be loaded to max memory, it will be called once vray starts to render? If that’s true, it means we can’t see it in viewport?
Thanks for the info Vlado. I don’t know why they enabled Bitmap pages by default it just doesn’t make sense if it’s slowing down everything. So VRayHDR is loaded in memory only when VRay needs it or does it stay in RAM all the time like Max does?
V-Ray will only load the map when it is needed (e.g. when a ray hits a material that needs the texture). There is an option whether to unload the maps at the end of the rendering, or to keep them (by default it is to keep them).
Additionally, when you use tiled OpenEXR files, V-Ray will only load the tiles that are needed for the image, rather than the entire file, which further reduces the memory usage. You can also specify the size of the cache pool for the tiles. This enables the rendering of scenes that contain very large and/or lots of textures.
The new capabilities of the vrayhdri loader sound great with regard to opening it up to other file formats. But why not just add another map called “vraybitmap”? I’m just looking at it in a clarity of naming type of way. Naming things for what they do. I think there is potential for people to overlook this important update.
