AM
To: Nuke user discussion
Subject: Re: [Nuke-users] OT: machine won't render SphericalTransform node
This prompted me to dig back and see my original bug report submitted around
the time of 8.0v1 -although I haven't checked to see if this was fixed, and I
didn't get sent a bug ID
Hi guys,
I am having a problem with a brand new deca core machine (64GB RAM) that
just won't render scripts with a SphericalTransform node. Nuke loads up,
then sits there with 0 cpu load or memory consumption and nothing happens.
Even my 4 year old laptop renders some frames - slowly, but it
I may be wrong here, but I've actually seen something like this bug with
some operations that require heavy filtering, I seem to remember it getting
introduced with Nuke 8. I submitted a bug report to The Foundry with speed
comparisons with Nuke 7.
I first noticed it with STMap then
damn, that leaves me dead in the water.
oh well, I guess I will just go to bed and be grateful for any frame I
see in the morning
On 27/08/14 01:31, Michael Garrett wrote:
I may be wrong here, but I've actually seen something like this bug
with some operations that require heavy filtering, I
You're probably tried this, but maybe run multiple instances of nuke, each
running a limited number of threads? It's how we run nuke jobs on the farm
on our 8 and 16 core machines, limiting them to 4 cores from memory.
On 26/08/2014 11:51 PM, Frank Rueter|OHUfx fr...@ohufx.com wrote:
damn, that
yeah, I have tried runnign dealine jobs with only 2 and 4 threads each
with absolutely no results.
Then, when I set off a single manual command line render with all 10
cores (20 cpus) it produced a frame after several minutes.
On 27/08/14 01:55, matt estela wrote:
You're probably tried
I'm not sure if it's the same bug, but I have run into a similar problem with
LensDistortion nodes when put inline with certain other nodes.
Basically the image calculates extremely slowly, but if you break concatenation
by putting a blur or grade above the LensDistortion node, it works as
This prompted me to dig back and see my original bug report submitted
around the time of 8.0v1 -although I haven't checked to see if this was
fixed, and I didn't get sent a bug ID. The rest is a copy paste:
I seem to have found a repeatable bug that affects the LensDistortion node
under certain
more than they fix.
-Nathan
From: Michael Garrett
Sent: Tuesday, August 26, 2014 8:35 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] OT: machine won't render SphericalTransform node
This prompted me to dig back and see my original bug report submitted around
the time of 8.0v1 -although
Thanks Jed, all my exrs are zip compressed and there is no concatenation
upstream of the SphericalTransform in my script.
Just installing Nuke 7 to see if that behaves any differnt
On 27/08/14 03:00, Jed Smith wrote:
I'm not sure if it's the same bug, but I have run into a similar
problem
*To:* Nuke user discussion mailto:nuke-users@support.thefoundry.co.uk
*Subject:* Re: [Nuke-users] OT: machine won't render
SphericalTransform node
This prompted me to dig back and see my original bug report submitted
around the time of 8.0v1 -although I haven't checked to see if this
was fixed
11 matches
Mail list logo
