animation prepass

[Robert]

When rendering an IC/Light Cache animation with prepass saving. I can't set the save folder for IC, only for Light Cache. Its a bit difficult to translate the Documents to the Modo dialog (which in general I find much better). So the only way I can save out a precalc animation is by saving the light cache (for which I can't set a frame step individual) and render IC as multi frame incremental. Not sure if that get saved some how.

[Robert]

So in 3dsmax you got a save IC and load IC.. same for light cache... In Modo there is only a same LC save option.. how can I test animation rendering without that?

[vladimir.nedev]

You need to check the "Auto save" option in the "Irradiance map" options. Then the "Auto save file" option will appear.
"Auto save" defaults to checked for the light cache, but it is unchecked by default for the irradiance map.
I will modify the code so they are both checked by default.

Note that when you choose "Animation (rendering)" for the mode, there is a separate path which is used to specify the file name for loading.
You will have to manually remove the frame number from that name, this is something that is done automatically in V-Ray for Maya,
but I haven't done in MODO yet.

Greetings,
Vladimir Nedev

[Robert]

Ok, thanks. Thats clever hidden.
I don't really know why the IC and LC cache has to be saved separate, but I will test that.
I also will use the 'use camera path' and check how well it works.

What really bugs me while testing is that you don't use the Modo animation pre-dialog. Its very confusing to set that in the output for a Modo user. And it really confuse.

The VFB is now at a permanent state of refusing saving and zooming.. guess that most be somehow related to config saving.

[vladimir.nedev]

If you have a .lxo scene in which the VFB always refuses to save/zoom, please send it to me.

As for the 'use camera path' option, I haven't tested it and it is a bit special compared to all the other options, so it may very well not work.

Greetings,
Vladimir Nedev

[Robert]

good to know. So after the process I got one map for LC and few (per frame) for the IC. Shouldn't it result in one IC map that you load.. without need of the LC when rendering?

[vladimir.nedev]

I think the "Animation(prepass)" and "Animation(rendering)" modes are supposed to be used for non-fly-through animations, i.e. you have something other than the camera position/orientation animated in the scene.
So that's why there is one irradiance map generated for each frame.

For fly-though animations I think you need to use the "Multiframe incremental" and then "From file" modes.

And yes, I don't think the "Light cache" will be used when you switch the irradiance map mode to "From file".
Unless you have checked "Use for glossy rays" in the "Light cache" options. There might be other cases though, I am not sure.

Greetings,
Vladimir Nedev

[Robert]

Ah ok, I thought thats new in Vray that the Incremental add to current map is replaced with the Animation Precalc method.. but thats for animation not flight through.
I basically just testing how to send scenes to render farm and fly through is the first simplest thing..

About the scene that block the VFB zooming.. I don't think the reason is the scene. It starts with the fact that VFB doesn't open first time in render size but always 640x480.. There must be bug there, that this size is stored on the computer and then general blocks the VFB..

[vladimir.nedev]

Then maybe if you can give me the steps that result in this, or record a short video ?

Greetings,
Vladimir Nedev

[Robert]

The render process make my testing a bit lame.. but I keep trying..

One thing so, I had now a few crash when rendering.. how do you handle that? Normally I send the crash report with a note to TF.

[vladimir.nedev]

You can create a thread here (actually in the bugs sub-forum) with the report attached or you can send it to me : vladimir.nedev@chaosgroup.com

Greetings,
Vladimir Nedev

[Robert]

Ok thats sticky, when rendering an increment to current map, Modo crash after the last frame rendered.