Hi Group,
As promised yesterday, here comes the answer from the support.
If you have additional infos or things not mentioned here, just write
the support team with the BUG ID 23221.
(Darn, I missed the bug 2 ;) )
Hi Dennis
Unfortunately this appears to be a corruption from a third
Yes its getting to the bottom of that issue is what I'm interested in.
Nuke shouldn't add these layers when not relevant, so these things cant
propagate but is it what causes this...
Shuffle49.out: Can't select rgba.alpha; it conflicts with other selected
channels
If this is from spurious
The two interesting commands were:
add_layer {rgba rgba.UVdistort rgba.beta redguard1.glow rgba.warper}
add_layer {partial}
Also a bunch of legitimate layers from 3D renders, e.g:
add_layer {outDiffuse outDiffuse.red outDiffuse.green outDiffuse.blue}
However, adding those with
Heads up:
Just got a support mail so the BUG ID will not work anymore. It's
going to be a feature request.
Read below:
Really sorry, I found a very similar feature request that I have added
your
comments to so Feature 23221 should be ignored and the new reference
is below
:
Feature
I have a GRizmo (group being used like a gizmo), which I would like to
add a multi-line string knob to..
I can do
k = nuke.Multiline_Eval_String_Knob(info_str)
nuke.selectedNode().addKnob(k)
..which does exactly what I want, until you recreate the node in any way
(e.g copy and paste, or reopen
Hey Ben,
Sounds like it's related to Bug 21461. Multiline_Eval_String knob isn't the
only not serialising correctly; there's MultiView_Knob and some others. The
workarounds have been kind of painful, to be honest.
Cheers,
Ean
On Fri, Nov 25, 2011 at 10:34 AM, Ben Dickson
hmm, i can see that is kinda hard to solve this issue without
crippling functionality... however, corrupted scripts are no fun either.
it seems to me that it adding unnecessary channels could greatly
reduced by some confirmation/warnings boxes...like:
if you paste some code into a script
I like your ideas, Chris. Along those lines, a while ago I made a custom
nuke.Layer function here that disallows adding any channels to built-in
layers. -Ean
On Fri, Nov 25, 2011 at 12:27 PM, chris ze.m...@gmx.net wrote:
hmm, i can see that is kinda hard to solve this issue without crippling
I have my doubts about messing with this stuff. From what I see is more of a
matter of people paying more attention to what they author/share and treat as
project/pipeline independent than a actual problem.
Implementing ways to control/restrict this stuff via user interaction could in
fact end
Hi Dorian,
we actually observe this behaviour here, too - sometimes at least. i
could not find any conditions yet to reproduce it exactly.
our workstations are on windows (xp64 and 7), the file server is running
debian with samba which we use to connect the shares.
do you know of any similar
Hi Holger and thank for your feedback.
ITs told me the TCP ACK delay was dynamic and are not forced...
I'm sorry to not be able to tell you more... :(
Anyway, if you do some test, don't hesitate to tell me if you find
something interesting. :)
Regards,
Dorian
On 11/25/2011 05:30 PM,
11 matches
Mail list logo
