Skip to main content
Jan 25, 2017 6:20 AM UTC
Archived

Creo Model should be saved automatically before traceback/crash to avoid data/work loss.

Related products:Creo Parametric

Hi,

As we know, Many times creo get crash and designer lose his all works. Creo not gives a chance to save model at the time of traceback.

So the idea is, creo should save model automatically before get crash or should be able to get one step undo after selecting cancel so designer can at least save there work and avoid suffer for work loss.

Thanks,

Prashant Pandarkar

21 replies

Jun 12, 2017 12:00 PM UTC

In my opinion, this idea should be closed down, and a new one made for built-in functionality for a timer-based notification that you might want to save because your part was modified N minutes ago and has not yet been saved.

There already is one of these ideas.  It just passed its 4th birthday.  Automatic Save for Creo Parametric

Jun 12, 2017 2:30 PM UTC

The problem with the current auto save feature is that many times we do a hypothetical change see how it looks and then erase from memory without saving.  So an auto save across the board doesn't make sense unless it was done under a different name...

Can someone explain to me why it is (apparently) so difficult to implement an auto save in the background with a dummy name that the program can find if it crashes for CAD work?  This was MS's solution to the problem and it really was a good one.  I understand that some companies may not be able to implement this if they are always working with HUGE models that are too resource demanding to do this, but there is a very large base of customers who don't work with HUGE models that would appreciate this.  Many core processors are now the norm so to "designate" (I don't mean this word too literally) one for Creo and one for an auto save feature seems like a very good and natural idea.  Since no one has mentioned any system doing this, and the idea is very intuitive I imagine this is some great obstacle to doing it this way.  Does anyone know why that is?

Creo, since time memorable, has been saving log files which are kind of like a near useless save history.  If that was switched to a useful one, or made more useable and robust, we would have the feature we are all voting for. 🙂

Jun 12, 2017 2:50 PM UTC
Jun 12, 2017 2:50 PM UTC

Its because PTC has to think about all the cases not just a few. If PTC tried to implement something that only worked in some cases but not others there would be a lot of user frustration. Parent Child relationships would be harder to maintain if you were making copies all over the place when things get modified. They would need to be some sort of reserved name so that references didn't get screwed up when working in a PDM environment in which a user may have created something with the same name as the backup name.

There is also performance issues to think about. When MS office files become very large the autosave function can prevent the user from working on the file for a little bit. Now multiply that wait by the number of files that Creo may have opened / modified. It could get frustrating quickly. That is why Solidworks opted to just prompt the user as a reminder to save instead of actually performing the save.

I agree this idea as written can't be implemented and the one that Tom referenced is worded better for the desired outcome.

Jun 12, 2017 3:12 PM UTC

See the comments over here: Re: autosave option available in Creo????

Autosave in itself is not practical for various reasons.

Same with temporary file naming like MS uses, since the relationships would become messed up.

A timer to remind the user to save and have the rule of FFF drilled into their heads is the best practical solution.

Jun 12, 2017 4:21 PM UTC

This would better be in the discussion for Automatic Save for Creo Parametric.

Jun 12, 2017 4:22 PM UTC

The parent child relationships is a good point.  On the other hand, you are only AutoSaving that which is in session, and in session all those relationships get modified in real time and have to be synchronized.  If there is no conflict in memory that I don't see why there would be a conflict saving that which is in memory.  Once you start erasing things and reopening, there would have to be a rule to know how long to hold those before auto-deleting them.  This doesn't seem like a show stopper.

Yes, I have seen performance issues to AutoSaving very large files in MS Word.  One of the highest ranking ideas has been to get Creo to use multiple-core processors simultaneously.  This would be an excellent use of that once they get that working right (if they haven't already).

Ben Loosli, have you had the temp file names in MS become problematic?  I always have this feature running in the background of MS Office, and use it whenever Office crashes, and have never had a naming conflict come up.  Their naming scheme is purposefully very screwy.  I am not sure what FFF means...?

Jun 12, 2017 4:42 PM UTC

In MS products there is no problem with temp file names. In Creo, if you rename a part file and its parent assembly for a temp save, how do you resolve them back to the real names after a recovery?

FFF = File Fairly Frequently.....or other choice words!

Jun 12, 2017 5:07 PM UTC

Ahh, thanks.

That is a good concern.  2 thoughts on how it could handle this:

  1. Creo would definitely know when a save as or a rename occurred because that happens in session so that could be programmatically accounted for.
  2. However, if all someone had to do was rename something after Creo recovered a file from being lost after a crash, that would be a pretty minor loss, that I think almost all would be too busy being thankful for everything else being recovered to care much about having to rename a file.

CHRISTOPHER REES, There are many features that Creo has that work in only some situations and then it works well.  I don't see this as a negative.  People could decide if it is good to use in their environment and then either turn on or off the feature accordingly.  I am never bitter at MS that the save as takes too long on HUGE MS Word files.  It is to be expected.  If I don't want it to slow down with HUGE files, I know that I have to fork over more money for a better computer.  I'm glad that MS gives me that choice! 🙂

Jun 14, 2018 7:54 PM UTC
Status changed to: Acknowledged