View Full Version : proxy works but full render crashes- should I batch?
01-21-2011, 08:53 PM
My comp renders and works fine in proxy mode; however, when I go to render it in full mode it crashes. Maybe the script is too heavy for my machine?
I was just wondering - if I work in proxy mode and everything is fine, can I then switch to full mode and render a batch?
Would batch rendering be able to render where my comp couldn't?
And can anyone explain to me how to batch render in nuke or let me know if there is a good tutorial out there on how to do this. I can't seem to find one.
01-22-2011, 04:28 PM
Hi, I think you just need to relink the proxy to the full size footage..
01-23-2011, 01:59 AM
How much ram do you have? What error are you getting on the crash? You can render it in the shell by typing "Nuke -X scriptname.nk". Adjust everything to your environment(path to nuke and version number, etc..).
You can find more in the pdf manual under chapter 21 "What Is a Terminal and How Do I Use One?". Page 604 in the 6.2 docs(may be a different page depending the version your using).
01-23-2011, 08:58 PM
When I turn off proxy mode, the error says:
Memory: malloc failed and cannot free anyting, throwing std::bad_alloc. This will probably crash!
OFlow in OFlow3: Effect raised an error during render.
How ever when in proxy mode, everything is fine.
Do you think rendering in full mode in a batch is the answer though?
01-24-2011, 09:06 AM
Again, how much ram and what os, what version of nuke, 32 or 64 bit?
std::bad_alloc means you are running out of ram. Try rendering in the commandline and see if it works. If you don't have enough ram then increase the amount of swap space could help. It will render slow when it goes into swap but atleast it will finish.
01-26-2011, 03:19 AM
Here is the info you asked about regarding my system:
3gigs of RAM
Thanks again for your help!
01-26-2011, 05:00 AM
did you try it in the commandline?
01-26-2011, 05:00 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
vBulletin v3.0.5, Copyright ©2000-2013, Jelsoft Enterprises Ltd.