Feb 2011
1 / 8
Feb 2011
Sep 2012
diamondx
Feb '11

So has anyone out there heard of this one?  A simple copy paste function locks up Nuke completely.  I can't seem to find anything like this online and it really sucks.

I'm using NukeX 64 bit version 6.2v1 on windows 7 64bit OS with 6GB RAM

I suspect this might have something to do with filesharing and/or timed backup because the program will occasionally not allow me to save over an existing file.

What's more, everytime the program crashes, it leaves a process nukequicktimehelper-32 in its wake.  Perhaps I can blame quicktime for all this.

Any help would be greatly appreciated guys!

Bob

  • created

    Feb '11

  • last reply

    Sep '12
  • 7

    replies

  • 7.2k

    views

  • 1

    user

fxnurbs
Feb '11

I never came across something similar.
try to update quicktime or an older version maybe

I suggest you to contact the foundry support, it seems more to me a specific problem that can come from your side (conflict or ...)

1 month later
sierrus
Mar '11

Up!
I have the same problem than rchapin and I don't know how to solve it.

Any solutions?

Thanks

23 days later
bfm
Apr '11

Did anybody ever solve this problem? I am having the same trouble.
I'm running NukeX 6.2v2 (64-bit) on Windows 7 64-bit OS, 4gb RAM, similar to the first guy who posted.
I too discovered the nukequicktimehelper-32 process after each crash. Took a long shot and tried updating QT but it didn't help, so I'm stuck.

However, I found an easy workaround. If you hit copy (presumably Nuke freezes up at this point), open the task manager and find the nukequicktimehelper-32 process and end it. Now when you return to Nuke you should hopefully be able to continue as normal and copy/paste all you like. Obviously this is by no means ideal and it would need to be done each time you run Nuke, so if anybody has an actual solution then please let us know.

Thanks.

18 days later
doomer
May '11

Same here. Nuke 6.2v1 (64-bit) on Windows 7 64-bit crashes with either copy or duplicate command.

5 months later
wetterschneider
Nov '11

I had this problem as well. 
I solved it by exporting chunks of my script and importing them one at a time into a fresh script, each time copying and pasting to see if it was still ok.  Eventually I had it all in and my nuke was working fine.

10 months later
nendo
Sep '12

I had this problem as well. I dont know if the cause is the same though. For me it was a keyboard language problem, I found out by chance when switching language (in this case from spanish to english).
Try it out, hope it helps!