Hello,
I have tried to solve this problem for the last day, but was not able to find the source of the issue. Usually all scenes render quite flawlessly with Arnold for me, but this one I just can't get to work.
The render process starts without problems, but always crashes on the second frame, no matter what frame is the first one. A day ago for some reason it managed to render about 50 frames without crashing, but I could not reproduce this effect.
I have attached the bugreport. I would be really glad if someone from the team could look into it quickly, I am at the end of my wisdom here, but I feel like I might be missing something obvious.
Hard to tell from this. Would it be possible to send us the scene (you can contact support(at)arnoldrenderer(dot)com)? Do you have motion blur enabled? Anything special in the scene?
thank you very much for looking into it.
Unfortunately I am not able to send off the scene..
Yes, I did have motion blur enabled- I just did a run without motion blur and it crashed again...
I also disabled DOF. After that the render rendered for about 4 frames and crashed then.
Otherwise I use almost the exact same setup as in a scene before that rendered just fine. I am using motion clips in this one, a focus object and constraints, that's basically the only difference
Would be great if you could narrow it down to something specific in the scene. Btw, is there anything (errors or warnings) in the Arnold log? You can find instructions of how to generate full verbosity log files on the right.
Otherwise please contact support and I can send you a build with more detailed debug logs, which can hopefully give me a clue what's going on.
I have converted the arnold logs to .txt because it would't let me upload the original files
I have attached the first frame (which rendered fine) and the second frame (which crashed). I hope this is more insightful
So to clarify. If you now run the render from frame229 (which crashed above), then it will render fine and frame230 will crash? Can you send the log of frame229 when it rendered successfully?
No, frame 0228 (which is also attached above) renders fine and 0229 crashes. But no matter which one is the first, the second one always crashes, also if it's 0100 and 0101
So here are the 0229 frame rendered fine and the 0230 frame crashed:
Can you try increasing the texture cache size and/or max open files in the render settings to see if it makes any difference?
https://docs.arnoldrenderer.com/display/A5AFCUG/Textures+-+settings
Try for instance 4096 MB for the cache.
I just tried it and it does not help unfortunately, I increased the texture cache to 20000 and the open files to 100 but it still crashes -
Not sure what's going on. When the plugin renders a sequence, each frame is independent, each frame starts and closes an Arnold session. So in theory it should be the same as rendering them one-by-one.
I wonder if you have the same crash when you start the render via the Render Queue or Commandline.
Here's a small script which you can also check. It renders each frame as a separate job. Downside of the script is that it blocks the UI and you see only the final images in the Picture Viewer, not the progress.
Thank you very much for the script, the first frame hasn't even crashed once, I think theoretically that should solve the problem, I will try it out.
Yes that also strikes me as very odd, I have already troubleshot a lot of different problems, but in most cases the render didn't even start or the log showed (more or less) a clear identification of the problem source. I have not the slightest idea what may cause this one, especially since both sets that were merged here worked perfectly fine on their own before.
I have spent the last hours deleting objects that are not directly visible to the camera in that shot, at the moment it is rendering frame 7 in a row, so chances are the culprit is one of the deleted objects, but they were so many that I couldn't nail it down exactly. Doing this for every new camera angle would not be very efficient though, so I think for now I will hope that the script will be of help.
Thank you very much for your help Peter, it is greatly appreciated!
Unfortunately the script is still giving me crashes..
I had set up my preview range to the frames I wanted to render and set my render settings to preview range. Then I ran the script. Is that set up correctly?
Here's an updated script which can read the range from the render settings, so this should work with your setup.
So I think I MAY have found the problem:
I had two scenes merged together and both where rooms that shared the same wall. So upon importing one into the other I had the same wall in place exactly on top of each other twice. I think that was what was causing the issue, I am not entirely sure though - do you think this could have been the reason for the weird behaviour or should this not be a problem?
Both had displacement and an arnold tag applied to them and both were Boolean operations. (For the cut out door)
And I know that Arnold has a bit of an issue with booleans within C4D right? For example, often a boolean just disappears in the render, especially if nested.
Ok nevermind, it's still crashing...
What is so strange about this is that there doesn't seem to be any pattern to it, sometimes after I delete something it runs for 5 frames, then crashes and the next time I start the same scene it already crashes after one frame again. I cannot get my head around this
Yeah, I don't think having both meshes should be a problem.
Honestly, at the moment I have no idea what could be wrong and it's really difficult to troubleshoot. You can try to disable elements (like ignore textures, etc.) in the Feature Overrides of the render settings, maybe it can narrow it down.