me across that issue a few times too. Didn't know about the cut
> and paste. I usually just restarted Nuke but I would love to get a better
> solution.
>
> On Wed, Feb 8, 2017 at 2:01 PM, Josh Imbruglia <
> the.factory.sm...@gmail.com> wrote:
>
>> I'm wondering if anyone els
I'm wondering if anyone else is experiencing an issue in Nuke 9/10 where
double clicking on a node doesn't always open the properties tab. If you
cut and paste it back into the node graph it then opens the property tab
again.
It's driving myself and many other artists crazy and just wanted to see
I know this post is quite old but we're seeing this on Nuke 8.0v5 and it's
quite annoying. Is there anyway of ignoring these errors other then editing
the layout.xml by hand?
Thanks,
Josh
On Tue, Dec 10, 2013 at 4:46 PM, Neil Rognvaldr Scholes n...@uvfilms.co.uk
wrote:
Anyone getting this in
Definitely repeatable, this is the same issue that we're seeing, weird key
frames get added and all the keys at the end get flattened.
A fix would this would be greatly appreciated as we've started to run into
this problem more and more in production.
thanks.
Josh
On Wed, Feb 13, 2013 at 10:10
i don't believe Nuke currently handles this, you'd have to write your
own dtex reader in order to access this functionality
-josh
On Wed, Jun 13, 2012 at 1:14 PM, Brany
nuke-users-re...@thefoundry.co.uk wrote:
Hi all,
I'm creating some .dtex files with multiple images inside. When I open them
the only way i found to do this was by launching a subprocess for
exrinfo and then parsing through the piped output.
if anyone knows of a simpler way i'd love to hear it.
-josh
On Mon, May 21, 2012 at 7:14 PM, Rich Bobo
rich.b...@armstrong-white.com wrote:
Hi,
Anyone know a quick way to
from what i've tested this seems to be now fixed, or at least our
problem has all but dissapeared.
josh
On Tue, May 1, 2012 at 11:10 AM, Moritz Eiche m...@moritz-eiche.de wrote:
hi,
any news on this? also just ran into that. we're using nuke 6.3v6 on linux.
couldn't find anything in the
Hi Christoffer,
we ran into this exact same problem just last week, contacted the
foundry and was told this is a known issue and has been logged as bug
#22989.
The work around we found was to set expressions to your frame numbers
or seed in order to get the result that you're looking for.
