Quote from tooltip "Render History and A/B Comparison":
"If enabled, a new item will be automatically added to the render history in the Corona VFB after each render ends (both IR and Production). This feature is automatically disabled when rendering sequences, and also for nodes during distributed rendering."
This is another feature Corona team managed to turn into some broken mystery, needing a diagram to look at when trying to use it. And it feels like decisions are made to work around design flaws rather than solving the issue itself.
1. IR results have never ever been saved to history in any Corona version so far. It was even considered as a bug in some daily when it happens - I remember reporting this, and some famous developer who is unfortunately out of duty atm. confirmed it as a bug. If (this==kindof NewFeature): the result does not get saved into history by pressing "stop" if using IR which is the "stop and save the results so far" button in contrast to "cancel", so it SHOULD be saved in history when pressing "Stop". It only gets saved if IR "Max passes" is set explicitly by the user - and has been reached.
AND it only happens if having "Time Output" to "Single"?! Who on earth should be able to understand and remember all this? If I just want to IR a frame and would like to have a history item from it, I have to change my scene setup, really? Btw: IR stop condition still defaults to 0, meaning "rendering forever", so you usually do not get a history item using IR anyway (a shame to have it at 0 by default nowadays btw.).
2. Do not even try to be smarter as the user. If I render a sequence, say frame 0 to 20, every 5th frame, I want to have exactly this in the history if I have enabled "autosave" - independently of having DR activated or not. DR on/off should never ever make any difference while using any feature anyway. Of course DR slaves should not write history items locally, they should never EVER write anything to production files. I've been fighting a lot to just have slaves not to overwrite light cache files - hard to believe that it took almost a decade to get that destructive behavior removed. Slaves should just deliver data to the master and never touch any production file, no need to stress that in a tooltip.
Good Luck
