Hi all,The way source and destination curves work will change for the next major version of Nuke, but in 6.3 the source and destination are essentially the same curve, similar to Roto and it's feather curve. (Hence the awkward naming..)Regards, Wouter-- Sent from my HP Pre3On 15 Dec 2011 01:28,
Hi all,
nice effect with the merge node :)
(v6.3v5 on Linux)
[Image: http://img809.imageshack.us/img809/9854/disover.jpg ]
(http://imageshack.us/photo/my-images/809/disover.jpg/)
set cut_paste_input [stack 0]
version 6.3 v5
Constant {
inputs 0
channels rgb
color 0.115
name Constant1
Strange. I wonder if this can be explained rather than just shrugged as a
bug.
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/
On 15 December 2011 15:10, makis nuke-users-re...@thefoundry.co.uk wrote:
**
intresting how the patterns changes when modifying the Transform filter...
On 15 December 2011 14:49, Ron Ganbar ron...@gmail.com wrote:
Strange. I wonder if this can be explained rather than just shrugged as a
bug.
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
so now that we finally have our house in order with a central
plug-in/gizmo/whatever install and the NUKE_PATH set, I'm wondering if it
makes sense to do a central install of the binaries? It would be nice if
all the workstations and render nodes are all on the same version, all the
time. How do
Our systems guys use a combination of remote execution tools (Puppet,
MCollective) and custom RPMs to enforce software installations (including
things like PyQt builds and other pre-rolled libraries/modules) and other
scripts that we need to have maintained locally (shell setup scripts, etc.).
Sounds like I need your systems guys
On Thu, Dec 15, 2011 at 9:38 AM, Nathan Rusch nathan_ru...@hotmail.comwrote:
Our systems guys use a combination of remote execution tools (Puppet,
MCollective) and custom RPMs to enforce software installations (including
things like PyQt builds and other
Got it, thanks for the info Nathan. I'll take a look at MCollective.
Sort of related to this (and equally noob-ish), is there any kind of nuke
startup file, where we can set it so nuke always starts with a certain
resolution and fps, for instance. Couldn't find it in the docs
Thanks!
On Thu,
You can set those attributes in the init.py file in your .nuke or user
directory.
C:\Program Files\NukeX.XvX\plugins
R
On Thu, Dec 15, 2011 at 2:26 PM, Gary Jaeger g...@corestudio.com wrote:
Got it, thanks for the info Nathan. I'll take a look at MCollective.
Sort of related to this (and
I've been going back and forth with cameras between Nuke and Cinema 4D for a
while but recently our Matte Painting changed size and offset. In order to get
all my projections to line up I created a camera in Nuke with a
window_translate or film back offset. However, when I export this to C4D it
If you're running OSX, have a look at Apple Remote Desktop 3 -- you can install
.pkg files on all the machines on your network with a nice UI:
http://www.apple.com/remotedesktop/
It makes it super easy to push out Nuke point releases to everyone. Time to
install 6.3v6!
--alex
On Dec 15, 2011,
I'm not familiar with C4D but you could try to look if the problem you're
facing isn't related to the unit system used by C4D. Perhaps C4D uses a
different unit system that needs to be converted to correctly work with Nuke.
On 15/12/2011, at 18:35, Joshua LaCross
Hi According page 607 of the Nuke manual (6.3v5):
U - Update Viewer display. Used when Pause is active (press P).
Can any one get this to work? What I would like to do is selectively update
the viewer while keeping it paused so that I can make several
changes...update...make several more
13 matches
Mail list logo
