View Full Version : Shake Script Error
russ_c
November 11th, 2003, 05:23 PM
I have been working on a rotoscope for the past few days and in the middle of altering one of my rotoshapes Shake just quit out. This has happened before, but I had no problems opening back up my file at the last save. This time the script will not open. When Shake begins loading the script it closes and gives me a "Shake has unexpected quit" error. Changing the location, name or computer the script is on doesn't seem to make any difference. This must be a corrupted script problem.
I would greatly appreciate it if someone could give suggestions or review the script file for any problems. It kind of made me sick when I thought about losing this last three days. I am using Shake 3 on OSX 10.2.8.
Here is the script file: Cheetah Roto.shk (96k) (http://www.cpfx.com/Cheetah Roto.shk)
Thanks is advance,
Russell
Hugh
November 11th, 2003, 05:28 PM
Are you still using it on the same machine that you created it on?
I tried to load it up in Shake 2.5 (windows) and got errors on 5 of the lines near the top...
The offending lines are:
DefineProxyPath("No_Precomputed_Proxy", 1, 1, -1, "Auto", -1, 0, 0, "",1);
DefineProxyPath("No_Precomputed_Proxy", 0.5, 1, 1, "Auto", 0, 0, 1, "");
DefineProxyPath("No_Precomputed_Proxy", 0.25, 1, 1, "Auto", 0, 0, 2, "");
DefineProxyPath("No_Precomputed_Proxy", 0.1, 1, 1, "Auto", 0, 0, 3, "");
SetAudio("100W@E0000qFdsuHW962Dl9BOW0mWa06w7mCJ000000000008");
deleting these lines made it open up fine.....
Aruna
November 11th, 2003, 05:29 PM
Opens up fine for me in shake3 on linux.. I just resaved it and uploaded it, in case that does anything.. If you still can't open it, try opening up some of the autosave.shk files in your nreal directory (or maybe it's in another directory these days!)
Hmm. I would upload it, but I can't upload .shk files.. Can this be fixed admins? :)
Hugh
November 11th, 2003, 05:33 PM
indeed it can, and already has been ;)
BTW - Aruna, are you getting the RotoShapes? Cos I can load up the script here, but the RotoNodes are all empty, it seems....
Aruna
November 11th, 2003, 05:45 PM
Yes, I'm getting the rotoshapes. Shake 3 codes rotoshapes differently than Shake 2.5, so that's the reason you won't see them. It's not backwards compatible unfortunately, but the goodies in Shake 3 make up for the incompatibilities. One other thing that I noticed (don't mind me as I pry into your comp) is that your paths have spaces in them. I know that OSX is a little different than linux, but I would never put spaces between descriptions of things. Instead of cheetah run it'd be cheetah_run. It'll clean up your scripts and the chances of error will probably be lower.
Good luck!
russ_c
November 11th, 2003, 05:55 PM
Well...excellent customer service, unfortunately that didn't seem to help the problem. I still get shake quiting out with the file so I will look around to see where the autosaving is on OSX. Thank you so much for both of your help. Please feel free to pry around with the file Aruna, I think you will find a very rough layout of the roto's thus far. I will be going back and tweaking the shapes better and adding the edge blur if the script ever works again :( .
I am sure my first exploration into roto's is complete off the beaten path...we'll see if I can pull it off though.
Thanks,
Russell
Hugh
November 11th, 2003, 05:56 PM
Well, at least you know the file's working, and you haven't lost all of the work you've done.....
Aruna
November 11th, 2003, 06:10 PM
A couple fixes I would try would be to alter your filein line from:
Animal_Motion = SFileIn("//Macintosh.local./Volumes/Video/Africa Serengeti/Animal Motion.mov",
to something like :
Animal_Motion = SFileIn("//Macintosh.local./Volumes/Video/Africa_Serengeti/Animal_Motion.mov",
Open up your favorite text editor, and open up the script, adjust for spaces, save as a new revision, and rename your file structure, and see if that works.
The only other tip I could give you would be that shake doesn't like the .mov file anymore. Not sure why it wouldn't since you've been working on it for a while, but that might be a problem. Or maybe the .mov file got corrupted in the crash?
russ_c
November 11th, 2003, 06:12 PM
Aruna,
The autosave files are still in the user's home directory in nreal/autosaves path. None of my autosaves will open either...they are all the same size as my original script so I suspect that some how they are the saved from the same place. Oh, how do you know shake doesn't like the .mov file...I am sure it would show red on your comp since you don't have the file, but I can't even get the thing to open up far enough to tell if that might be the problem. How can I edit the script to remove this node? Sorry for all the nagging, I get a little to eager to learn sometimes.
I am a little worried at this point...
Russell
Aruna
November 11th, 2003, 06:15 PM
Try this.. I removed the filein and ignored nodes that weren't attached.
Aruna
November 11th, 2003, 06:18 PM
Or maybe this one...
russ_c
November 11th, 2003, 06:28 PM
Wow...your a fiend Aruna, but the files still are not opening....what about the very last move I did on the rotoshape...where would that be in the script. Perhaps this got screwed up or corrupted in the middle of working with the file. The node was Front_Leg_Roto were I have three shapes parented for each moving part of the leg. I moved the parent at the top of the hierarchy and then crash! Fixing the path file names didn't do the trick... Now I am really worried.
Thanks^2,
Russell
russ_c
November 11th, 2003, 06:36 PM
Success!
By deleting the last node I worked on, Front_Leg_Roto, the file will now open again...now it is time to see how little I can delete from the script and still get it to open. That way I will minimize the losses in rotoscoping I did on that node.
Thank you Thank you Thank you to both of you gentlemen for being so helpful. This is what makes vfxtalk forums the best experience.
Russell
Hugh
November 11th, 2003, 06:38 PM
glad we could be of some help, although, in the end, it was you who fixed it ;)
russ_c
November 13th, 2003, 05:59 PM
Alright,
The crash happen to me again today when I was working with rotoshape nodes. This time I saved each time with a new version to protect myself. Now I can't recover the file as I did two days ago and it has corrupted all of my other versions!!!???
help,
Russell
Hugh
November 13th, 2003, 06:51 PM
hmmm - sounds like it may well be something to do with your computer or your install of Shake....
You tried reinstalling Shake?
russ_c
November 13th, 2003, 08:30 PM
Reinstalling didn't do the trick or using another computer (similar config, OSX Shake 3). Do you think you could check to see if will open on your system...I might have to switch to Linux, this is disappointing and terrible frustrating.
Cheetah Roto v2.8.shk (126k) (http://www.cpfx.com/Cheetah Roto v2.8.shk)
Thanks for the patients,
Russell
Aruna
November 13th, 2003, 08:40 PM
Yeppers, opens for me in shake3 on linux. Don't know what i can tell ya. :( Actually, does it spit out an error into the shake window? What does it say, if anything?
russ_c
November 13th, 2003, 08:49 PM
It simply closes out shake and gives a message box in the OSX GUI that says Shake has quit unexpectedly. Salatar pointed out that I am using a shake beta.
I hope I am not smashed for this:hammer:. If I had a job I would take care of this immediately, but being a recent grad. and not having a job I don't know where else to go to get the experience I feel I need to be viable in the industry... mercy, please. I can start over I guess.
Anyway, I deserve this I suppose,
Russell
wood78
November 14th, 2003, 10:54 AM
In versions previous to shake 3 I would have alot of problems with rotoshapes in means that it would crash often although I never had a corrupted script. In the future try your roto with quickshapes and you will probally never have a problem again let. Although this problem may have been fixed with ver.3 but I can not afford to find out. Yes quickshapes lack multiple shapes in one node and the fact that you can feather edges but there are ways around this. Use a max node to add a couple of quickshapes together and most of the time a simple blur will do the trick. i know this is not solving your problem but it is just a suggestion for future reference ( use quickshapes!)