well I would dupe the script then using text editor delete those lines.
once those lines have been deleted your comp will look just like it did
before everything went bye bye. IF its the {} bug.
Randy S. Little
http://www.rslittle.com <http://reel.rslittle.com>
On Mon, Apr 18, 2011 at 00:58, Miodrag Colombo <[email protected]>wrote:
> Hi Jrab,
>
> thanks for the reply.
> I have been experiencing this problem for quite a while.
> The only thing that comes in my mind would be that Nuke did not save
> properly the script, although when I save the script I make sure it does it
> properly, though, also it show that has been saved.
> It might be also a network problem as for the last week we have been
> experiencing some issues.
>
> Regardless the autosave i have tried to open that too, however it does not
> work either as I face the same problem.
>
> I can only open the previous version and everything its ok apart from the
> changes made which are not in that script, unfortunately.
>
> I could also check whether there are some bad stuff checking thoroughly the
> script.
>
>
> x Randy,
>
> if I do what you are suggesting will that back up my script or it will show
> some small pieces?
> Sorry for the silly question, better to ask twice before assuming that i
> understand what you are actually suggesting/saying.
>
> best
>
> Miodrag
>
>
>
>
>
>
> On 17 April 2011 19:56, John RA Benson <[email protected]>wrote:
>
>> unfortunately, I've been seeing this a lot too. The bad news is, your
>> script didn't really save completely. Open it in a text editor and chances
>> are you'll see a script that doesn't end with "}". Could have been a network
>> problem or Nuke crashed during the save? I hope your backups are working.
>>
>> What's really a drag is you've probably already destroyed the autosave,
>> since you needed to bypass that in order to get to the point where you are
>> getting that error.
>>
>> I wish there was a way to 'proof' a script before nuke starts to read it,
>> to validate the script or clean up some bad stuff that gets into the script
>> (like bugus channels imported from another script) and is hard to clean up
>> otherwise. But I suppose that could be done in a wrapper?
>>
>> jrab
>>
>> On Apr 17, 2011, at 1:29 PM, Miodrag Colombo wrote:
>>
>> Hi there,
>>
>> recently I've been experiencing some problems with nuke.
>> when I re-open the same script that has been saved few hours before its
>> shows this error through a pop up window
>>
>> Traceback (most recent call last):
>> File "<string>", line 1, in <module>
>> RuntimeError: missing close-brace
>>
>> any helps
>>
>> Thanks
>>
>> Miodrag
>>
>>
>>
>>
>>
>> --
>>
>> __Miodrag Colombo
>> __PIXOMONDO / SHANGHAI
>> __Features Films/Commercial
>> __Lead Compositor / Salsa Teacher / Dancer
>> __SHA mobile: +8618721279510
>> __www.miodragcolombo.com
>>
>>
>> _______________________________________________
>> Nuke-users mailing list
>> [email protected]
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>>
>>
>> _______________________________________________
>> Nuke-users mailing list
>> [email protected]
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>>
>
>
> --
>
> __Miodrag Colombo
> __PIXOMONDO / SHANGHAI
> __Features Films/Commercial
> __Lead Compositor / Salsa Teacher / Dancer
> __SHA mobile: +8618721279510
> __www.miodragcolombo.com
>
>
>
> _______________________________________________
> Nuke-users mailing list
> [email protected]
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
_______________________________________________
Nuke-users mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
