what is the reason for not having AutoSave in any versions of NX

[NXsupport]

Hi All,

Just curious to know why did UGS not implement AutoSave in NX,when AutoCAD has it... I think its a good thing to have it..

 

[ewh]

Because it @#%&'s!
Actually. it used to be a feature of UG, but nearly everyone I know complained about it and turned it off, so there probably really wasn't much point in continuing to offer it.
If I'm working on a large part or assembly, and trying to accomplish a complicated task, the last thing I want is for the file to save itself automatically. If it is an assembly, does it save only the work part or the whole assembly tree? What if I had edited some components of the assembly but wasn't sure if I had found the right solution? I realize that you could be able to go back to previous save levels, but it still seems to be too interuptive to me to be worth much. Self discipline (save early and often) is a much better solution in my opinion.
For what it's worth, you can use the save reminder if you want. A better, less aggressive solution. I turn that off though, too.

Believe it if you need it or leave it if you dare. - [small]Robert Hunter[/small]

 

[JohnRBaker]

While we don't have an 'AutoSave' option (the rational behind that has already been more than adequately described by ewh even without the @#%&'s!) you could, as mentioned, turn on the 'Save Changes Reminder' in Customer Defaults -> Gateway -> General -> Part (it's at the bottom of the page).

Between Virtual Memory and PDM systems, some of the older 'recovery/protection' schemes, such as 'Warm-Starts' or 'AutoSaves', are either largely impractical or would involve such complex self-checking and logistical rules that any benefits gained would soon be lost in additional system overhead and/or platform resource requirements.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[hudson888]

There are a few areas where working in assemblies will make that kind of auto-save rather intrusive as compared with systems where you aren't likely to be using either the master model concept or drawing upon files that you may not have ownership or write access to. In NX were such a feature implemented then you might consider the case where it attempts to save your work and either affects others or frequently spawns a series of perfectly valid and normal warnings but which would be nonetheless intrusive.

I think that earlier versions of UG dabbled in this kind of thing from time to time, but in latter years the developers have deemed it inappropriate for their product. On the other hand the save reminder is a less insistent solution which may be well worth considering. As it does not force anything upon the user it does little harm.

Many a time I have chosen to work for hours on end without saving accepting the risk that I may lose the work should something go wrong, but unwilling to save until I'm happy that I have something worth going further with. I would not under those circumstances appreciate an auto-save function.

Best regards

Hudson