Sounds like the script has it's node stack messed up somehow.. I've had
similarly weird problems when importing slightly malformed files with
nuke.scriptRead..
I can't remember the exact problem, but for example if something like this:
set cut_paste_input [stack 0]
version 7.0 v5
push $cut_paste_input
Camera2 {
name Camera1
}
..is missing lines like the "push $cut_paste_input", the next created
node might be attached to an unexpected node (or potentially could end
up in a group)
On 05/11/13 10:32, Brandon Harris wrote:
> I have not run that. This works in all contexts, but this one nuke
> script. I can have the artist, in this instance, just delete the groups
> and clean the script up a bit. More attempting to head off any future
> issues that could potentially pop up.
>
> cheers,
> Brandon L. Harris
> ------------------------------------------------------------------------
> *From:* nuke-python-boun...@support.thefoundry.co.uk
> [nuke-python-boun...@support.thefoundry.co.uk] on behalf of Ean Carr
> [m...@eancarr.com]
> *Sent:* Monday, November 04, 2013 5:51 PM
> *To:* Nuke Python discussion
> *Subject:* Re: [Nuke-python] Creating nodes on the top level
>
> I can't think of any reason why that wouldn't work...
>
> with nuke.root():
> # do stuff in root context
>
> Did you try running nuke --safe just to check it's nothing about your
> setup that's causing the odd behavior?
>
> Cheers,
> Ean
>
>
> On Mon, Nov 4, 2013 at 11:45 PM, Brandon Harris
> <brandon.har...@reelfx.com <mailto:brandon.har...@reelfx.com>> wrote:
>
> Currently grasping at straws when it comes to this issue. I don't
> have the option to willy nilly delete nodes from an artists' comp.
> Is there some way to determine what about the group node makes it
> the one Nuke uses for creating its nodes?
>
> This is all probably the same thing, but I get the same issue using
> node = nuke.root().run(nuke.nodes.Camera2)
>
>
>
> cheers,
> Brandon L. Harris
> ------------------------------------------------------------------------
> *From:* nuke-python-boun...@support.thefoundry.co.uk
> <mailto:nuke-python-boun...@support.thefoundry.co.uk>
> [nuke-python-boun...@support.thefoundry.co.uk
> <mailto:nuke-python-boun...@support.thefoundry.co.uk>] on behalf of
> Brandon Harris [brandon.har...@reelfx.com
> <mailto:brandon.har...@reelfx.com>]
> *Sent:* Monday, November 04, 2013 5:29 PM
> *To:* Nuke Python discussion
> *Subject:* RE: [Nuke-python] Creating nodes on the top level
>
> If I delete all the group nodes it works, but if there are ANY group
> nodes in this script, no matter how I try to create the nodes, it
> always puts them in a group...
>
> cheers,
> Brandon L. Harris
> ------------------------------------------------------------------------
> *From:* nuke-python-boun...@support.thefoundry.co.uk
> <mailto:nuke-python-boun...@support.thefoundry.co.uk>
> [nuke-python-boun...@support.thefoundry.co.uk
> <mailto:nuke-python-boun...@support.thefoundry.co.uk>] on behalf of
> John Vanderbeck [jwvanderb...@gmail.com <mailto:jwvanderb...@gmail.com>]
> *Sent:* Monday, November 04, 2013 5:20 PM
> *To:* Nuke Python discussion
> *Subject:* Re: [Nuke-python] Creating nodes on the top level
>
> with nuke.root():
> create node
>
>
>
> - John Vanderbeck
> - http://www.johnvanderbeck.com
>
>
> On Mon, Nov 4, 2013 at 3:18 PM, Brandon Harris
> <brandon.har...@reelfx.com <mailto:brandon.har...@reelfx.com>> wrote:
>
> This is a resend because ctrl+enter gets me all the time.
>
> I'm creating cameras, but they always seem to get created inside
> of a group node that is on the top level of my script.
>
> I've tried
>
> root = nuke.root()
> with root:
> nuke.nodes.Camera()
>
> root.begin()
> nuke.nodes.Camera()
> root.end()
>
> nuke.createNode('Camera')
>
> Nothing seems to work. Is there a way to force a node to be
> created at a particular level or a way other than node.begin()
> to set what the current 'root' level is?
>
> Thanks!
>
>
>
>
> cheers,
> Brandon L. Harris
> www.freebirdsmovie.com <http://www.freebirdsmovie.com>
>
> _______________________________________________
> Nuke-python mailing list
> Nuke-python@support.thefoundry.co.uk
> <mailto:Nuke-python@support.thefoundry.co.uk>,
> http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
>
> www.freebirdsmovie.com <http://www.freebirdsmovie.com>
> www.freebirdsmovie.com <http://www.freebirdsmovie.com>
>
> _______________________________________________
> Nuke-python mailing list
> Nuke-python@support.thefoundry.co.uk
> <mailto:Nuke-python@support.thefoundry.co.uk>,
> http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
>
>
>
> --
>
> www.freebirdsmovie.com <http://www.freebirdsmovie.com>
>
>
> _______________________________________________
> Nuke-python mailing list
> Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
--
ben dickson
2D TD | ben.dick...@rsp.com.au
rising sun pictures | www.rsp.com.au
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
