Re: [Nuke-users] Simple Custom Environment Variable setup

Thanks Frank. You’re always so helpful. This was a huge help in my baby steps to start customizing the workflow a little more. It just takes some of us a while to get a “feel” for the syntax with tcl and Python. Michael > On May 1, 2016, at 7:16 PM, Frank Rueter|OHUfx

[Nuke-users] Nuke Studio 10.0v1 on OsX 10.10/11

Is anyone successfully running Nuke Studio on OsX 10.10/11? Getting GPU hangs and machine hard-restarts whilst testing it with simply H.264, DPX and Exr clips, on a Gtx 980. Thanks! ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk,

Re: [Nuke-users] Simple Custom Environment Variable setup

Yes, that's how it can work (just make sure you use correct single quotes, one of yours is a back tick which will cause a syntax error). And of course in your example you are setting and env variable called "JOB", but then reading one that is called "NUKE_JOB" which won't get you the respective

[Nuke-users] Simple Custom Environment Variable setup

I know it’s kind of a basic question ( I already asked on the forum and the silence was deafening) but I’m struggling with properly setting up a custom environment variable in Nuke. I’ve read the documentation but it seems to gloss over the fundamental set up a little. So I've got two

Re: [Nuke-users] Nuke Studio 10.0v1 on OsX 10.10/11

I’m using it fine. I get the normal Nuke crashes but it crashes a lot less then 9.0v8. They fixed most of the El Cap crash bugs during the beta. Did you update your cuda drivers? On Sun, May 1, 2016 at 4:50 PM, Marten Blumen wrote: > Is anyone successfully running Nuke

Re: [Nuke-users] Simple Custom Environment Variable setup

No problem. Generally python is more flexible and powerful than tcl, but in some cases the syntax for tcl is shorter which lends itself more to using it in text nodes or node labels. tcl is also generally more light weight than python but that can depend on what you are doing. I'd recommend

Re: [Nuke-users] Nuke Studio 10.0v1 on OsX 10.10/11

Yep - Cuda is up to date. NukeX is running fine. I'll see how the support tickets go. Cheers! On 2 May 2016 at 13:37, Deke Kincaid wrote: > I’m using it fine. I get the normal Nuke crashes but it crashes a lot > less then 9.0v8. They fixed most of the El Cap crash

Re: [Nuke-users] Nuke Studio 10.0v1 on OsX 10.10/11

Cool - yep it's a MacPro 5,1. Cuda 7.5.26, Driver 10.5.2, OsX 10.10.5, and whatever the current latest is for 10.11.5 beta. Easily happens with iPhone H.264 footage, in the timeline trim the clip, click drag on the left clip edge, as the preview window appears NS will freeze within a few seconds.

Re: [Nuke-users] Nuke Studio 10.0v1 on OsX 10.10/11

Interesting. Reported similar issues in beta but thought it was my machine and stopped them from chasing it down. MacPro5,1? What cuda and driver version? Do you have a case that's easily replicable that I can try here? I never found a way to consistently provoke it to do this. MacPro 5,1,