Nuke (v6.1v1 or earlier) when network processing can sometimes fail and leave its temporary “*.tmp” files behind, which theortically shouldn’t be a problem as it should overwrite them the next time that particular frame is rendered. However, computers don’t always behave, especially on Friday evenings when you want to go home and especially when the file servers in question are running Windows OS
So. here’s a general and a job script that finds and deletes any *.tmp files on a particular Nuke job or generally via declaring a certain directory to scan.
(The Foundry tell me that v6.1v2 will attempt to fix the underlying issue/s regarding writing to locked render output image files and hence the *.tmp files are fine but fails to overwrite the final output file!)
Hope this helps someone go home on time!
Mike
General Script - install to your \repository\scripts\General\ folder and run it through the Monitor’s “Script” menu. TmpFramesCleanupGeneral.zip (2.52 KB)
Nuke Job Script - which uses a job’s output folder. Extract to your \repository\scripts\Jobs\ folder and run it through the Monitor by right clicking on a job and selecting “Scripts”. TmpFramesCleanup.zip (2.49 KB)
We are having this issue with our renders. I’ve installed both scripts, after restart the monitor I can see tehm in the menus but when I execute them nothing happens and the .tmp files are not deleted.
There’s been a few API changes between Deadline 4 and 7, so these old scripts would need updating to work. It might be an idea for us to actually ship with them as they are kinda useful and the Nuke issue will always be there and the only real fix is to use Linux. I’ll create an internal ticket to review the code.
I wish we can move to Linux but is not possible at this moment.
Shipping this kind of scripts with Deadline sounds as a very good idea, indeed. I’ll give it a try so I can get familiar with the DL API, if I come with something usable I’ll share it here. An Event Plugin seems to be a better choice for this kind of job, right?
Nothing fancy and I’m sure there is a lot of room for improvement (my Python is even worse than my english ) but is working for us. I hope it helps somebody else until you guys have the time to do it properly.
Please, If you install it, be aware that I didn’t test this thoroughly. So, use it at your own risk.
I put some minimal logging that can help to pinpoint errors.
Nice! Something you might want to consider, is pushing your example to our Github site where we welcome clients/users to post their useful scripts/plugins/events for public consumption (assuming you are authorised by your company to do so):
Where possible, if we answer a client via a quick script/plugin/event, or we get asked the same question a few times, we tend to whip up a generic example for others and posted them here for events: github.com/ThinkboxSoftware/Dea … tom/events
Worth a bookmark anyway incase you need something else in the future.
) but is working for us. I hope it helps somebody else until you guys have the time to do it properly.