dampeoples opened this issue on Mar 10, 2003 ยท 8 posts
dampeoples posted Mon, 10 March 2003 at 11:00 PM
I'm too incredibly new to this to lose the work I just did, I wonder if I hit the OK or Cancel button enough, will I get my work back?
dampeoples posted Mon, 10 March 2003 at 11:01 PM
Oh, All I did was try to apply some directional force, then CMD-X it away, using OS X 10.2.4, Carrara 2.1, and the last update that I saw, so I assume I am current. I'm gonna go sit in a corner by myself and cry.
dampeoples posted Mon, 10 March 2003 at 11:34 PM
Someone is smiling on me. After trying like a little monkey, click, click, click. to get this thing to recover, I gave up and right clicked the quit option on th icon in the dock. It gave me the option to save :)
willf posted Mon, 10 March 2003 at 11:37 PM
A first lesson hard-earned: save, save & save again. I'm have the same set-up but just installed Cararra V2 last week so haven't really spent too much time in it yet.
dampeoples posted Mon, 10 March 2003 at 11:47 PM
Yeah, I'm normally good about saving. It was only gonna take 5 minutes to fix this before I saved, honest :)
pixelicious posted Tue, 11 March 2003 at 4:22 PM
Be careful saving files after getting "unknown error has occurred" I usually "save as" if i get the option, just to make sure the error doesn't get written into my file. I'd rather lose the last hour, than all week.
save as frequently, as carrara tends to still do strange things from time to time. at the end of a project, i usually have 15 or so copies of the file. you can never be too safe.
-pix
bluetone posted Tue, 11 March 2003 at 6:49 PM
I would say the culprit is the directional force, which takes a deal of calculation in the backgfround. Even though you CUT it out, it still was in the UNDO buffer. This means your memory was still being used, even though you thought you'd removed it! As your memory probably reached it's end, your computer, hiccuped with the dreaded "unknown error has occured." (This is also sometimes called a "memory leak.") I agree with pixelicious, that you should do a 'save as.' It clears the buffer, and should keep your file clear of excess baggage. Also, do a re-boot after your save. That way the computer as a whole is starting out fresh, without an error in its memory. Hope this helps! :>
dampeoples posted Tue, 11 March 2003 at 6:55 PM
Thanks for the tips. i ended up rebooting due to other strange things, they could have been related. Work.Save.Work.Save. :)