Customization?

[grafikus]

Two questions:

Is there any other way to further customize File req. in Nuke other than changing $workdir variable? For example if I would like to add some kind of Favorites Button we know from Shake.

Is there any way to alter way Nuke is handling Parameter windows. Friend of mine is perfectly happy with lots of overlaping node windows opened at once. But I would prefer ability to switch this behavior off for some situations. To make Nuke UI behave like in Shake or in XSI. I Know that unconstrained UI is stated as one of advantages in Getting started guide. But if there could be option to make it behave different way, I will apreciate.

Support for Maya .iff would be nice.

Anyway maybe I just need to get my SHAKE neurons out of my head.

NUKE THEM.

[Anonymous]

Hi Grafikus,

Improvements to the file browsers, including a means to store favorites, are on the way. In fact, they are being coded now.

We also have plans to develop some snap-to window configurations for people who prefer a more locked down UI. This is in the plans for this, but not currently in development.

MayaIFF support is in the latest version of NUKE which will be distributed in the coming weeks.

JP

[grafikus]

Thanks a lot for response.

[grafikus]

I spent more time in Nuke and I have to admit it really adictive 😀 (that SPEED). But I would like to put this question. Is it possible to configure nuke to use another sequence player than IRIDAS. Thanks.

[Anonymous]

Grafikus,

We like FrameCycler very much here, but NUKE’s integration of it is not hardwired. It’s simply a TCL script–or more accurately, a couple of them–that renders out a sequence, lauches FrameCycler, and loads the sequences. The end user has access to these scripts and could modify them to point to an alternate flipbook.

In the version of NUKE which we’re about to release, we also include the latest version of FC for all OSs.

JP

[grafikus]

Thanks. I already found that tcls that are starting Iridas and will experiment. Cant wait to put my hands on new version. Great app. Keep walking.

[grafikus]

Where I could configure Nuke to Use D:/TEMP instead of C:/TEMP Should i change system drive variable in init.tcl?

Thanks.

[Anonymous]

Grafikus,

To change the flipbook directory, edit this line in the NUKE/plugins/user/tcl-commmands/flip_me.tcl.

if {![info exists flipbooktmp]} {set flipbooktmp “c:/temp”}

Thanks,
Jason

[grafikus]

Thanks.

[grafikus]

I am facing folowing problem i have to colorcorrect very high amount of data and I would like to tell WRITE node to delete SOURCE file of actually writen result. The thing is WRITE xxx.001.tga delete xxx.001.tga and so on. I think it should be easy but I am still in kindergarden of tcl and nuke internal relations beetwen scripts. Can anybody give me advise me please. THANKS.

[wonko]

grafikus wrote:

The thing is WRITE xxx.001.tga delete xxx.001.tga and so on.

Um, out of my head, you can do three things:

– write you imaged to /dev/null , and they will never appear on the drive, but I assume that you want to do something between rendering and deleting them, so…

– you can make a tcl script part of your filename by puuting it in square brackets, for exacmple: “/in/my/directory/[exec ls]filename.jpg” . The tcl script will be run just before the image is written

– you can also execute a shell script that renders a single frame using the Nuke renderer (-x flag) and then do whatever you like with the image. You can of course do a loop in the shell script to render all frames.

Matthias

[grafikus]

Thanks a lot. I will try.

[Author]

Posts