Are you using deeps and switch nodes, for example? Sometimes some deep
nodes allow to be connected to non-deep nodes upstream. They will become
disconnected upon reoppening the script. Example (I copied this as a
connected script, but when you paste it it will become disconnected):
set cut_paste_input [stack 0]
version 9.0 v6
CheckerBoard2 {
inputs 0
name CheckerBoard1
selected true
xpos -23417
ypos 7941
}
DeepFromImage {
name DeepFromImage1
selected true
xpos -23393
ypos 8069
}
Switch {
which {{curve x1 1 0}}
name Switch8
selected true
xpos -23429
ypos 8138
}
Blur {
channels rgba
name Blur26
selected true
xpos -23427
ypos 8202
}
On Tue, Jul 14, 2015 at 1:48 AM, Ben Woodhall <[email protected]>
wrote:
> Hello Niki,
>
> I don't know of any issue like this. Could you send a screenshot of the
> DAG before saving and the script after saving to support so that we can
> look into it here? If it happens with all Merge nodes, I'm guessing that
> you can reproduce this in a simple script. Could you also try creating the
> same script in --safe mode and see if it also affects copy and paste (which
> I expect it would).
>
> Thanks, Ben Woodhall
>
> On 14 Jul 2015, at 01:58, niki wrote:
>
> Thanks Nico
>
> our bug is different there are no cloning nodes in the scripts affect.
>
>
>
>
>
>
> [email protected]
> www.nikibern.com
>
> ------------------------------
> *From:* Nico Dufort <[email protected]>
> *To:* niki <[email protected]>; Nuke user discussion <
> [email protected]>
> *Cc:* "[email protected]" <[email protected]>
> *Sent:* Tuesday, 14 July 2015, 10:34
> *Subject:* Re: [Nuke-users] bug - inputs switching when saving
>
> We've experienced something a bit similar when decloning nodes (no
> facility code involved, just plain vanilla Nuke).
> We first noticed that back on 6.3 and it still seems to be an issue on 9.x.
>
> <image.png>
> <image(1).png>
>
>
>
>
> On Mon, Jul 13, 2015 at 4:57 PM, niki <[email protected]> wrote:
>
> Hello
>
>
> long time since I used this list so please excuse me if I am repeating a
> bug that may be already known.
>
> I'm currently working at Cutting Edge in Sydney and we have noticed a
> pretty bad bug in both v08 and v9.0v5.
> At some point after working on a shot for some time our scripts become
> corrupted and on Save the merge inputs swap randomly between the matte and
> a side or jump to different nodes all together.
>
> So far we have noted that it seems to be only the A stream and the Matte
> that is affected. The B stream seems to remain correct.
>
> The only solve we have found is to remove all merge nodes.
> Save file
> Replace all merge nodes.
>
> Has anyone else seems this ?
>
> Many Thanks
>
> Niki
>
>
>
>
> [email protected]
> www.nikibern.com
>
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
>
>
> --
> "Attention, attention. Here and now, boys," the mynah repeated. "Here and
> now, boys."
>
>
> <image(1).png><image.png>_______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
> --
> Ben Woodhall
> Software Engineer
> The Foundry Visionmongers Ltd
> 5 Golden Square
> London, W1F 9HT
> Tel: +44(0)20 7473 4350
> Web: www.thefoundry.co.uk
> Email: [email protected]
>
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>
>
>
>
>
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
--
Jose Fernandez de Castro
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users