Hello,
We're continuing our experiments in the studio, focusing almost exclusively on the caustics feature.
The first (and main) problem we've encountered since the vray_adv_70001_max2025_x64_32809 beta build (official vray_adv_70002_max2025_x64 release have the same issue) is that we can no longer render animated scenes with caustics inside.
I'm in the middle of a test set and haven't done all the cross-testing I'd like, but from what I understand at the moment, this problem doesn't exist on the vray_adv_70001_max2025_x64_32796 build.
Our computers (solo, group, local, network, via max, via a render manager etc...) are unable to render two frames with caustics in a row with the last two builds above.
Either Max simply crashes as soon as it tries to render the second frame (when the scene is rendered on a single computer) when changing frame.
Or Max takes 6 to 7 hours (I did said hours, it's not a mistake) to precalculate the caustics of the second frame for a frame that normally takes 30 to 40 seconds to precalculate the caustics pass (when the scene is rendered via a Pulze-type render manager).
To sum up: Max is very good at rendering a single frame of an image sequence with caustics. As soon as he moves on to the second frame. It either crashes, or takes an improbable amount of time to calculate the prepass.
vray_adv_70001_max2025_x64_32796 build has other issues the news builds don't have ... but at least we can render animated sequence with this one.
I might be wrong somewhere, it's difficult to be sure of my info since everything is moving fast between builds but I hope I've explained it well enough for you to find something to correct.
Best,
Nicolas
We're continuing our experiments in the studio, focusing almost exclusively on the caustics feature.
The first (and main) problem we've encountered since the vray_adv_70001_max2025_x64_32809 beta build (official vray_adv_70002_max2025_x64 release have the same issue) is that we can no longer render animated scenes with caustics inside.
I'm in the middle of a test set and haven't done all the cross-testing I'd like, but from what I understand at the moment, this problem doesn't exist on the vray_adv_70001_max2025_x64_32796 build.
Our computers (solo, group, local, network, via max, via a render manager etc...) are unable to render two frames with caustics in a row with the last two builds above.
Either Max simply crashes as soon as it tries to render the second frame (when the scene is rendered on a single computer) when changing frame.
Or Max takes 6 to 7 hours (I did said hours, it's not a mistake) to precalculate the caustics of the second frame for a frame that normally takes 30 to 40 seconds to precalculate the caustics pass (when the scene is rendered via a Pulze-type render manager).
To sum up: Max is very good at rendering a single frame of an image sequence with caustics. As soon as he moves on to the second frame. It either crashes, or takes an improbable amount of time to calculate the prepass.
vray_adv_70001_max2025_x64_32796 build has other issues the news builds don't have ... but at least we can render animated sequence with this one.
I might be wrong somewhere, it's difficult to be sure of my info since everything is moving fast between builds but I hope I've explained it well enough for you to find something to correct.
Best,
Nicolas
Comment