Batch Render not saving in VFB History

[raptorscream]

Hello,

With both Vray, and older Corona I'm doing batch renders for projects, and I saved them in VFB History to alter them (tone map) if needed after the renders are done.
Now even though I have Enabled Render History and A/B Comparison and automatic saving on render end, it wont end.
I have the progressive rendering limits so to either 3-5% or a certain time, everything rendered and saved on disk as it should, nothing saved in VFB, any ideas why?

I'm using 3ds Max 2025 and Corona 12.

[Frood]

any ideas why?

Because developers decided once again to cripple a feature instead of eliminating the cause.

https://forum.corona-renderer.com/index.php?topic=43296.msg227047#msg227047


Good Luck

[maru]

You can use the regular output autosave for this, not the render history one. You can then drag-and-drop the resulting CXR images into the VFB to edit them. In Corona 12 HF1 it is possible to only load one CXR at a time, but in V13 dailies we have the option to load multiple CXRs into the history tab. This will be a part of an upcoming release.

I understand that the current workflow is less convenient than the previous one. The support for saving history autosaves was disabled for sequences and DR nodes because in some cases it could result in filling up the disk space and firing an error message which could block rendering. Imagine a situation where you start rendering, leave the CP running overnight, and return to it only to see that 10% of your animation was rendered.

We will see if we can somehow improve this.

[Frood]

The support for saving history autosaves was disabled for sequences and DR nodes because in some cases it could result in filling up the disk space and firing an error message which could block rendering.

Just silently delete the oldest item if disk space limit is exceeded and eliminate that "error" dialogue entirely as it is standard for auto backups, log file rotation and more - no one will miss it. How many "reports" are there about this issue to justify that drastic change anyway.


Good Luck

[raptorscream]

I see, so rather than fix or find a workaround, they just deleted the feature....

You can use the regular output autosave for this, not the render history one. You can then drag-and-drop the resulting CXR images into the VFB to edit them. In Corona 12 HF1 it is possible to only load one CXR at a time, but in V13 dailies we have the option to load multiple CXRs into the history tab. This will be a part of an upcoming release.

I understand that the current workflow is less convenient than the previous one. The support for saving history autosaves was disabled for sequences and DR nodes because in some cases it could result in filling up the disk space and firing an error message which could block rendering. Imagine a situation where you start rendering, leave the CP running overnight, and return to it only to see that 10% of your animation was rendered.

We will see if we can somehow improve this.

I want to avoid using CXR because I usually batch over 10-15 renders at once, I dont want to kill my disk space with CXR that are each at least 5-10GBs

[maru]

But history autosave items are also saved in the CXR format.