If it is in this forum, then can you please consider adding a configurable “Auto File Save” feature in a (near) future update? eg: allow the user to set how often a file is automatically saved
I just experienced over 20 crashes, losing my changes each time, in the past hour using CC v726 (OSX version) on a MacBook Air running MacOS 12.4.
I now make a conscious effort to manually save the file I’m working on after each change, no matter how small the change is. I never had to worry about this in prior releases of CC.
Also, does CC create/save a log (diagnostic or otherwise) to help development debug problems?
@Gmarkos Hi George. There is a Feature Request thread for both CC and CM here in the forum…here is CC’s link.
I like the idea of an autosave function and would definitely vote for it! Although, I think something else is wrong if you’re crashing that often. I’ve not experienced a crash in CC (outside of the betas) in 3 years of use…
I like your idea. That will save me when I forget to save properly.
Problem is, I get my head stuck up my dark spot, run off to do something else, then think of another way to do what I was programing. If It auto saves will I be able to CTRL Z out of my dark spot?
The only issue is if it saves multiple versions. The reason is because you work for an hour on a design, autosave kicks in, you accidentally erase your drawing, autosave kicks in, you are screwed.
As an alternative, use a network drive system which affords backups of and access to previous versions — apparently OneDrive can be set up to allow that.
Usual approach to cope w/ crashes is to save w/ an incrementing number attached to the filename.
If you can provide us w/ a file which consistently crashes when a particular operation is performed, please send it in to support@carbide3d.com and we’ll do our best to look into it.
That’'s not an issue…saving multiple versions would auto save each separate version as you work on them. eg. “file01.abc” only gets auto saved with the changes you make to “file01.abc”. As soon as you save a different version of that file, for example, do a “save as file02.abc”, auto save writes to that new version/new file name, not to the first file, thus preventing overwriting previous versions of the file.
If you’ve ever used any MS office product (Word, Excel, Powerpoint), you’ve already experienced how auto save works.
It kept happened during the “edit nodes” operation. I ‘traced’ a file into CC, then went into edit nodes to smooth and delete some nodes. There were a lot of nodes in this traced file so I suspect CC may have exceeded one of its memory managment queues, buffers, or counters.
I’ll send support@carbide3d.com both the source file I traced traced into CC as well as the file I was doing the ‘edit nodes’ operation on.
Background autosave is something we’d like to add but I think it may have to wait until V8. We need to build a little more infrastructure so we can get a copy of the document to save in the background without it changing in the middle of a save. Otherwise we either have to pause the program for a little bit (bad) or risk a crash (really bad).
