C4D - frames say "complete", but are not created.

[rtaege]

I submit a job from within C4D and all the frames turn blue and say complete with a render time of about 5sec. They aren't really rendering and there are no files created in the output directory. In the Error tab, there are no errors. In the Out tab, I see a line "Project not found". But above that it has the correct path to the project file...

Has anyone experienced this before?

I'm running C4D R14.025, win 7 x64.

[rtaege]

I just noticed while it's rendering, there are temp files that appear and dissappear real quick in the folder. I took a screenshot of it. It looks like there's some information at the end of the .exr extension. Could this be keeping it from writing out the file?



[attachment deleted by admin]

[jburk]

I see that CinemaConcept has a valid software subscription, which entitles you to support through our helpdesk.

Would you like to send an email to support@pipelinefx.com with a brief description of your problem, and if you could also include the contents of the log directory for the job in question that would be great.  If you can't find the job log directory, we'll reply in the helpdesk ticket with instructions on where the logs are.

[rtaege]

Thanks for the reply. I managed to get the issue sorted out last night.

[teows]

Hi, our users are on Mac OS platform QUBE6.4 and they are also experiencing the same missing frame. how did you get it solved?

[BrianK]

For the googlers, there are 2 issues at play here:

1. C4D (on Windows), does not return a useable exit status @ exit.  Because of this, Qube cannot determine success or failure based on the traditional method of looking at the exit status of the application (which it does for every other application we support).  To work around this behavior, Qube looks for key words in the output logs.  If it sees one of those words or phrases (they are defined in the "regex_errors" section of the submission dialog), it marks the frame as failed.  In this instance, a matching error message was not seen, therefore the frame was not marked as failed.

To note: As of Qube 6.5, Cinema4D submissions include "Path not found" as a key phrase to determine pass or failure. 

2. Path not found errors are very likely due to one of two issues:
 i. Qube is running in service mode and the user under which the service runs does not have access to the file share.
 ii. Jobs are being submitted from a Mac, using forward slashes ('/') as path separators, but rendering on Windows.  While other Windows applications work with both forward and backward slashes as path separators, Cinema4D on Windows does not accept '/'.

To solve 2.i. - Either give the proxy user permissions to the file share or change the proxy user to one that does have access to the file share

To solve 2.ii - Set up path translation either in the GUI or through the use of appFinder jobs.

Related:
proxy user:
http://docs.pipelinefx.com/x/NYAc
http://docs.pipelinefx.com/x/k4Ur

path translation:
client-side http://docs.pipelinefx.com/x/4IAO
worker-side http://docs.pipelinefx.com/x/kogr
appFinder http://docs.pipelinefx.com/x/mIgr

Of course if your support contract is up to date, you can mail us: support@pipelinefx.com for more detailed help.