vrmapbak

[powerandrubber]

I've found many times that it is very easy to accidentally overwrite a precalculated imap file that took many precious hours to calculate. For example when calculating segments, not getting the frame range entered correctly or forgetting to change the save imap filename. Or when backburner is calculating an imap, crashes part way through and starts over automatically overwriting the vrmapfile. It would be extremely helpful if vray automatically created a bak file when saving vrmaps that was always one save behind the current version (similar to autocad). Or maybe an option to incrementally save a bak file everytime a vrmap is saved; filename001.bak, filename002.bak, etc.

[instinct]

i second that!

[muzzy]

three

[gilpo]

Four

Much needed! An overwrite confirmation on all possible save parameters would be nice (vrimage, irmap, lc, gbuffer, etc). I don't know how many times I've nuked an important file.

[powerandrubber]

"I don't know how many times I've nuked an important file."
3 times in the last 2 weeks for me. Also needed is frame info in the file properties.