With traditional irrmaps, there was a nifty trick where if you did say a irrmap + lightcache calculation, and saved the irrmap, then you could render the final pass with only the saved irrmap and no LC. This meant faster renders as the LC data was baked into the saved irrmap solution.
I've noticed that with the new animated irrmap sequences, this is not the case. Using the same approach will work, but the final render will be incredibly slow if you don't have a secondary bounce solution turned on. Is this because the LC is not baked into the saved irrmap?
I've noticed that with the new animated irrmap sequences, this is not the case. Using the same approach will work, but the final render will be incredibly slow if you don't have a secondary bounce solution turned on. Is this because the LC is not baked into the saved irrmap?
Comment