Author Topic: Corona Autosave filename/path should be local to max file, not 3ds max  (Read 3041 times)

2017-06-30, 10:20:53

alexyork

  • Active Users
  • **
  • Posts: 699
  • Partner at Recent Spaces
    • View Profile
    • RECENT SPACES
It looks like currently when you set the corona autosave filename and folder within max it's saving that data to 3ds max itself rather than the max file. What this means is that when someone submits a network render job from their machine, say it's called machine01 and the corona autosave is set to machine01/autosaves/machine01_render_01.exr, what actually happens is that if that render ends up being rendered on machine05, it will actually pick up the corona autosave filename and path on that local machine05, NOT machine01, so it might well end up saving to machine05/autosaves/machine05_render_01.exr. This is very confusing indeed, because filenames and paths don't always (hardly ever, really) match the actual job/render name.

I've made that sound very complicated, probably. Crux of it is that corona autosave filename and path should save with the max file, not with max itself, so they will always be respected during network rendering, no matter which machine picks up the job.

Cheers,
Alex York
Partner
RECENT SPACES
recentspaces.com

2017-07-03, 15:28:40
Reply #1

Frood

  • Active Users
  • **
  • Posts: 1903
    • View Profile
    • Rakete GmbH
This reads a bit like you seem to misemploy autosave as render output :) I agree: storing the autosave definition into the max scene rather than in local config is far better for project/network based work (it has been like this in earlier Corona versions). But:

Autosave is primarily meant to be backup, and there are a bunch of reasons for keeping it as local setting (and local file). Additionally you can always override the autosave path+filename with string options in all scenes, even customised for a specific project so it gets saved persistently within your max files. You could even use a network path there if you are not scared by GBs of cEXR files testing your network performance :]


Good Luck


Never underestimate the power of a well placed level one spell.

2017-07-03, 15:55:15
Reply #2

alexyork

  • Active Users
  • **
  • Posts: 699
  • Partner at Recent Spaces
    • View Profile
    • RECENT SPACES
This reads a bit like you seem to misemploy autosave as render output :) I agree: storing the autosave definition into the max scene rather than in local config is far better for project/network based work (it has been like this in earlier Corona versions). But:

Autosave is primarily meant to be backup, and there are a bunch of reasons for keeping it as local setting (and local file). Additionally you can always override the autosave path+filename with string options in all scenes, even customised for a specific project so it gets saved persistently within your max files. You could even use a network path there if you are not scared by GBs of cEXR files testing your network performance :]


Good Luck

Hmm. Indeed backup is exactly what we're using autosave for. You send off a critical 12-hour render, but for whatever reason it doesn't finish/save, but you always have your coronaautosave backup from not long before the render crashed/stopped, so you can fall back to that if needed. We're not using it as any kind of primary (or secondary) output.

We'll try the string options. That sounds like it could be a solution. The issue is quite straightforward and I think it needs to be addressed hopefully.
Alex York
Partner
RECENT SPACES
recentspaces.com