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

Jan 25, 2017 3:05 PM UTC

Well, If Creo KNEW it was going to crash it may do that!

"I want all unplanned outages reported in a memo 3 days before they happen" - Dilbert's PHB

Jan 25, 2017 3:28 PM UTC

Microsoft Office products have solved this by creating a hidden backup file which is routinely saved. If the program crashes, it looks for the backup file when it restarts and prompts the user if they want to recover the last auto-save. PTC could implement something similar (although it is a more complicated because there are lots of files, not just one). Solidworks has a pop-up that reminds you to save if you haven't in the last X number of minutes.

Jan 26, 2017 8:37 PM UTC

CHRISTOPHER REES‌, Yes, I am voting for this idea for PTC to do something like that.  I recognize that the multiple files of asms, parts, dwgs, etc combined with dependencies create a more complicated situation that Word, however I still like thinks would be fantastic if implemented as a choice.  I wonder if they can already do it but puts too much of a strain on system performance that they don't release it.

The SW prompting idea sounds like a great work around...as long is it was not too annoying when working on something in sessions without the intention of saving.

Jan 27, 2017 1:48 PM UTC

In Solidworks it looks like this:

Capture.PNG

It fades away after a few seconds.

Jan 27, 2017 4:05 PM UTC

That looks like a nice work around that they implemented.

Jan 27, 2017 4:10 PM UTC

As long as it doesn't demand a click or break my workflow, I wouldn't be opposed to something like that.

Jan 30, 2017 4:03 PM UTC

It should be configurable by the user whether or not they see that option so that they can turn it off if they don't like it (or if it is poorly implemented and is annoying)

Jun 10, 2017 6:41 AM UTC

Also Creo should popup a warning message if designer is violating design intent instead of crash

Jun 10, 2017 12:04 PM UTC

In my opinion, if the software was smart enough to know a crash was imminent and it needed to warn a user or save the model, why wouldn't it be smart enough to just not crash.  That's why PTC (or someone) started to use the "unexpected exit" terminology.  We all expect Creo to crash occasionally, so why aren't we smart enough to save more often.

Jun 11, 2017 1:56 PM UTC

Got it on the nose.  If we know things are looking bad, we fail gracefully.  A crash means we were caught off-guard, or wrote bad code (or both).  As stated, the request is impossible, partly because we can't predict the crash, and partly because if we are crashing, the model is likely in a half-baked state (say, in the middle of regenerating a feature) or actively corrupt.  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.