Indeed! or some viable alternative if a 30% consumption is a possibility. I take it this is some sort of failure in the coding of the ColourCorrect map or is a significant time loss going to be inevitable when performing all of those adjustments on the fly?
I’d imagined that it would perform all of the adjustments at the beginning of the render and hold those in memory but I suppose that negates the memory-saving aspect of having fewer source images.
I thought about the VrayHDRI loader but there is no control over Hue/Saturation. It would be great to have an image adjusment map with more generous controls (a bit like what we now have in the VFB in Vray 3) - as long as there were no big negative impact on render times associated.
4k wide would be ideally 6-8 hours on a single i7, up to 12-15 for some particularly elaborate ones
Similar renders are honestly about 5 times longer than this for me. I must be cursed!