Saving Elements - Can we change this?

[Charlie Nicols]

Ok scenario:

I have rendered off a final render in a scene with elements and it has saved it out.

Now later coming back into the scene for test renders for a new lighting scenario, I have turned off 'Save File' in the Common Tab however when I press Stop on Corona render VFB all the Elements save over the previous save path that was set via saving the final render.

I know this is the way Max works, to avoid it I need to turn off render elements as well as Save File.On the other hand other renders have ways to avoid this happening?

Can we get some kind of Fail safe to stop previous elements getting written over if you aren't trying to deliberately save over your previous renders.

In general for me if 'Save File' is turned off and I press a button that says stop on a render it would make sense if nothing got saved, I don't know if others agree? At the least a confirm overwrite box could pop up.

Comments welcome.I know this is not a fault of Corona, just perhaps a nice feature to stop people making this mistake.

[Frood]

Now later coming back into the scene for test renders for a new lighting scenario, I have turned off 'Save File' in the Common Tab however when I press Stop on Corona render VFB all the Elements save over the previous save path that was set via saving the final render.

Best option is to switch to "Iterative Rendering Mode" for tests. This way you even don´t need to untick "Save File" (no file outputs at all).

Additionally if you like the thrill you could use "Cancel" instead of "Stop" in cVFB (or render status window).


Good Luck

[SharpEars]

Now later coming back into the scene for test renders for a new lighting scenario, I have turned off 'Save File' in the Common Tab however when I press Stop on Corona render VFB all the Elements save over the previous save path that was set via saving the final render.

Best option is to switch to "Iterative Rendering Mode" for tests. This way you even don´t need to untick "Save File" (no file outputs at all).

Additionally if you like the thrill you could use "Cancel" instead of "Stop" in cVFB (or render status window).


Good Luck

BTW and sorry if this is a stupid question, but what's the difference between cancel and stop for the main production render?

[pokoy]

Stop will just stop rendering but save the image/passes while cancel will abort rendering and all subsequent steps.

BTW, I like the original request. We could be shown a prompt (just like with other engines in Max) asking if we want to overwrite with an option to remember the setting for the current max session.

[Charlie Nicols]

Best option is to switch to "Iterative Rendering Mode" for tests. This way you even don´t need to untick "Save File" (no file outputs at all).

Additionally if you like the thrill you could use "Cancel" instead of "Stop" in cVFB (or render status window).

[/quote]

The thing is I do use it whenever possible but sometimes and especially on the older workstations in the office it doesn't provide the preview quality we want.

This is a good idea however it is also a workaround instead of a fix for a potential problem.

[Frood]

the older workstations in the office it doesn't provide the preview quality we want.

This leaves me a bit unsure if you mixed up "Interactive" and "Iterative" rendering here.

Good Luck

[Charlie Nicols]

That may have been the the case Frood =P!

[Ondra]

this is handled by 3dsmax, other workarounds suggested, so I will close this down