nukex6.2 64bit writing tga sequences crashes

Become a member of the CGSociety

Connect, Share, and Learn with our Large Growing CG Art Community. It's Free!

Thread Tools Search this Thread Display Modes
  01 January 2011
nukex6.2 64bit writing tga sequences crashes

hit render for any sequence recently and nuke will crash with this message:

message title:
Write1: Can't rename .tmp to final, Permission denied

message content:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:/Program Files/Nuke6.2v1/plugins\nukescripts\", line 8, in render_panel
return nukescripts.showRenderDialog(_list, exceptOnError)
File "C:/Program Files/Nuke6.2v1/plugins\nukescripts\", line 623, in showRenderDialog
File "C:/Program Files/Nuke6.2v1/plugins\nukescripts\", line 231, in run
nuke.executeMultiple(self._nodeSelection, frame_ranges, views, continueOnError = self._continueOnError.value())
RuntimeError: Write1: Can't rename .tmp to final, Permission denied

this seems to be happening more and more frequently. the only fix i've found so far is to create a new write node with new location and file name.

it leaves a temp file where the sequence stops rendering, but deleting this still causes the crash in the same place. Anyone else getting this? I 'mm wondering wether its windows7 and not nuke?

  01 January 2011
Well It Seems That It Is A Bug For Version 6.2, That Did Not Exist In 6.1.

So There's The Solution, Use An Earlier Verison.
  01 January 2011
Sadly it existed in all versions of Nuke. You've only just noticed it now.

When rendering, Nuke writes temp files and then changes them to the image file upon completion. Sometimes the operating system stuffs up and won't let you change the temp to an image. Delete all the temps and hit re-render.
  01 January 2011
Yes, thanks for that, i still recon win7 is having a hand in it.
strangely enough, even deleting the tmp file- it still crashes.

what is even stranger...i can read/write nukeX 64bit.

i thought quicktimes were a nono on 64bit windows?
  01 January 2011
Do you have things like search indexing and volume shadow copy disabled?

Also, as of 6.2v1, it's possible to read and write Quicktimes on 64 bit Windows.
  02 February 2011
i just had the same problem and i solved it by turning off my windows 7 user account controls.
Adam Ferestad
Freelance Artist
3d ☼ VFX ☼ Web Design
  02 February 2011
hmmm do you mean the slider control you can set to never notify? it is already, but the problem still occurs.
  06 June 2011
Hey did you fixed this??

I have a huge project here, and I started getting this *****ng error over and over... Itīfreaking me out.

Iīve tryied it all, deleting caches, deleting the .tmp file, executin nuke as admin, the UAC is off....

yesterday the error appeared, and deleting the cache and the tmp worked, now It doesnīt.
I need to do the final render for tomorrow, donīt know what else to do
  06 June 2011
Nope, it still occurs from time to time.

the best way i found was to tick the "render in background" box and do it that way, seems to thrown significantly less errors.

also, rendering to exrs instead seems to work.

good luck
  06 June 2011
Did you use name####.tga in the write node?
Do you run any other memory consuming app at the same time?

Last edited by kyrgr : 06 June 2011 at 05:55 PM.
  06 June 2011
Hey guys!
I was having the exact same problem as joecoke69, trying to render a JPG sequence. It started to happen TODAY, yesterday was all fine.
I use the render in background, as he suggested, and also use the kyrgr suggestion of the NAME_####.jpg (i was using %04d) and now is rendering, a little bit slower, but rendering.
Donīt know what fixes the problem, though.
Is there a bugfix or something?
  06 June 2011
You guys should really report this to They can't fix it if they don't know about it.
  04 April 2012
Hey there guys...
i thought i'd chime in and ressurect this thread, as i have stumbled upon this on a rather large project, had driven me close to insane, and looking up a solution online yielded absolutely no useful information, apart from a couple of hacks that did no work.
Enabling administrator permissions, logging in as admin, changing disk permissions etc, even reformatting and reinstalling the system did not fix this. It is a windows specific nuke bug (does not happen on linux or osx).
The only thing i have discovered that fixes this problem, is to close down nuke, remove its temporary folder completely (appdata/local/temp/nuke - on windows7), then restart the app.
Using clean buffers and disk cache does not fix it.
Afterwards all behaves as expected. Mind you, once the temp folder fills up, the problem might come up again, but at least this allows you to render sequences without the annoying "can't rename" crap popping up.
As a sidenote, what i did, was to create a simple batch file that would first remove the folder and all it's subfolders, and then start nuke. That way, everytime i run the app, i get a clean run. Downside is, if i have large trees, they need to recache, but at least now they render....


Last edited by oktawu : 04 April 2012 at 04:02 PM.
  07 July 2012

Thanks oktawu!
I will spread this temp folder delete method - it is the only answer I've found that actually works.
  08 August 2012
I had problem with same issue time to time and I resolve it as save sequence in another hdd dffrent folder and carry it my proper folder after finish the render (Like D:/render/blabla.###.tga)
Thread Closed share thread

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Society of Digital Artists

Powered by vBulletin
Copyright Đ2000 - 2006,
Jelsoft Enterprises Ltd.
Minimize Ads
Forum Jump

All times are GMT. The time now is 07:07 PM.

Powered by vBulletin
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.