[Animation] Exporter first creates blank frames

[fused]

I have changed the output path back to it's original purpose of specifying the render output path and fixed the issue where blendigo "forgets" the output path if it contains # characters.

The scene file will be saved into the render ouput path, but the name cannot be set anymore (if anyone needs that functionality back, I'd introduce a scene file name property).

[Doug Armand]

That's great - has the creation of blank frames also been fixed?

[fused]

Well, yes, sort of:

The output path is used correctly now, that means Indigo will save the images with the same name as blender does. The blank frames are still written by Blender but Indigo will overwrite them as the animation renders.

[Doug Armand]

Well, yes, sort of:

The output path is used correctly now, that means Indigo will save the images with the same name as blender does. The blank frames are still written by Blender but Indigo will overwrite them as the animation renders.

So there isn't a way to prevent Blender from producing those empty frames?.
Shame as they add time to a render session - a 30 sec animation @30FPS needs 900 frames and generating those empties just adds to an already long process .

[fused]

So there isn't a way to prevent Blender from producing those empty frames?.
Shame as they add time to a render session - a 30 sec animation @30FPS needs 900 frames and generating those empties just adds to an already long process .

I doubt they actually take any meaningful amount of time to create. What is taking up time is the export process, i.e. the scene processing, mesh and scene file writing to produce an Indigo scene file.