Page 1 of 1

Hitting 'render' produces no files?

PostPosted: Fri Apr 03, 2015 2:36 pm
by fletcherkildren
Hi, new user here and am enjoying Fusion immensely - hoping there is a simple answer to a vexing problem I have.

When I press 'render' - nothing saves, no files, movies or images. My console only says: Render started at Fri 10:12AM (Range: 1 to 195)
Render completed successfully at Fri 10:14AM - Total Time: 0h 1m 36.15s, Average: 2.02 frames/second

no other messages in console.

Rendering other projects that worked in the past yields the same results. The only difference in my system was a dvd ripping software that I installed (and now uninstalled and used revo and ccleaner to remove all traces) I've also reinstalled Fusion and added firewall exceptions for eyeonscript, eyeonserver and eyeonQTserver - also to no effect.

Any help or insight is greatly appreciated - thanks in advance!

Re: Hitting 'render' produces no files?

PostPosted: Mon Apr 06, 2015 8:49 pm
by Stephanein Boulet
There are a few scenarios where Fusion might not produce files when rendering. Have you double checked some of the more obvious settings?

Do you have your saver turned on (not set to passthrough)?
Is the saver setup with a valid path and file type?

Is this problem related to a single comp or all comps loaded in Fusion?

Steph

Re: Hitting 'render' produces no files?

PostPosted: Tue Apr 14, 2015 5:18 pm
by Joël Gibbs
Just as a heads up for anyone else, make sure you check the saver length also.
I had a comp recently where the saver node had gotten shortened (user error I'm sure). So it rendered the entire comp, but only output frames within the duration length of the saver node.

(though it sounds like an easy fix..it actually took me a while to find out what was going on. :) )

Re: Hitting 'render' produces no files?

PostPosted: Tue Apr 14, 2015 6:03 pm
by Stefan Ihringer
The render dialog has a small "warning" message that should be extended for cases like this.

Currently, it says "not all branches end in a saver" which happens a dozen times in perfectly sane flows. So I guess everybody simply ignores this message.

Instead, the message should say something meaningful:

Rendering 3/4 savers.
1 saver does not extend to whole render range (click to inspect)
1 saver is disabled.