Hi Paul,
Yes, currently all Toolsets get saved in the .nuke directory and must be
manually copied to a shared location if you'd like them to be made
available to ther users. I guess it would be possible to add a
preference for Toolset save location, but this could be have a potential
for
I started experimenting with a rewrite of the toolsets feature, which
added a share command.
You created toolsets in the normal way, and they were created in ~/.nuke/
Then there was a share button which had a mirror of the toolset list
(just like delete), which presented you with a list of
two things come into my mind:
a) you can build a temp script with the read node and all the things
you want to do. and the end put in a write node
in the read node file knob write: [argv 0]
and in the write node put an expression to build the name from the write
node or put in [argv 1]
then
Some interesting stuff so far, but not yet exactly what we are after (though it
definitely is an improvement).
Is there any documentation on that python-tab in the write node? I didn't find
anything on this, but maybe I'm not searching properly, because I didn't find
the former mentioned
try something like:
in the before render field of your write2:
nuke.toNode(Switch1)[which].setValue(2)
this will work if you hit the render on each write seperate, for my
quick test it didnt work if i render all nodes
Am 21.11.2011 14:08, schrieb Thomas Volkmann:
Some interesting stuff so
Id probably set up some python to iterate through the read nodes. in the
beginning of the function it hooks up the read with the top most node,
and at the end it executes the write.
On 11/21/2011 2:35 PM, michael vorberg wrote:
try something like:
in the before render field of your write2:
i stumbled upon this a few days ago:
http://www.creatogether.com/foreach-nk
haven't tested it myself yet but looks like it's doing at least some of
the stuff you're looking for.
cheers,
Holger
Thomas Volkmann wrote:
Some interesting stuff so far, but not yet exactly what we are after
This thread is great, I haven't seen this issue going around in a while! I was
a compositor on Tron at DD, and that is exactly where this channel virus came
from. The red guards were the armies of programs that CLU used as his muscle in
the machine world of Tron. They can be seen in the
So Ned how do you think a company that didn't work on is Tron having
this problem? :-O
Randy S. Little
http://www.rslittle.com
On Mon, Nov 21, 2011 at 14:50, Ned Wilson nedwil...@gmail.com wrote:
This thread is great, I haven't seen this issue going around in a while! I
was a compositor
hey ned,
this is interesting information, but i haven't worked on TRON or somehow 'near'
the cinema world, lately
So far I deleted everything in the scripts (haven't been many in the few days i
figured out the add_layer part). But today, while showing several old comps
(6.0.1 nearly over a
Err.. actually it's the MCP …d'oh
well no job at MPC for me anymore
cheers
On 21.11.2011, at 21:49, Dennis Steinschulte wrote:
hey ned,
this is interesting information, but i haven't worked on TRON or somehow
'near' the cinema world, lately
So far I deleted everything in the scripts
Well, I've found it in several of our tools, which will then be propagated
into scene files.
I betcha Nukepedia has some gizmos that are infected too and again, if
someone is reusing a config/resource file, downloaded tools or tools
they've borrowed from other facilities and they've been
Searching through the archives, it looks like there's also a few cases of
shared snippets and copy/pasted scripts sent to this list that were
infected.
They could have propagated just by copy-pasting them back.
These layer infections are so hard to track down and completely get rid
of...
Makes me
For me the bokeh plugin (not necessarily the gizmo) is the one adding the
rgba.beta channel.
On Mon, Nov 21, 2011 at 4:21 PM, chris ze.m...@gmx.net wrote:
hmm, found two gizmos with redguard1.glow on my machine:
bokeh_blur_jb_v03_1.gizmo
Bokeh_Blur.gizmo
i probably got them of nukepedia or
Chris,
I have seen horizon.matte as well.
On Nov 21, 2011, at 4:21 PM, chris wrote:
hmm, found two gizmos with redguard1.glow on my machine:
bokeh_blur_jb_v03_1.gizmo
Bokeh_Blur.gizmo
i probably got them of nukepedia or vfxtalk
might be a good moment that everybody scans their
15 matches
Mail list logo
