Auto save?

[Anonymous]

due to the inherent unstable nature of the program, it would be really useful for the auto save function to work automatically as a default setting, and save an emergency file that is overwritten every 15 mins or so. This will limit the amount of work that is lost. Msave does not work reliably enough and although it is a lifeline the amount of times the program has crashed out mid operation without successfully msaving has cost me many hours of work. I am aware that there is a current auto save feature, however it needs to be more usable. The problem is that it interrupts workflow whilst it preforms the operation and also the way it is currently configured means that it erases the auto save when the program exits which defeats the point if the program has crashed out! this is something that i have been frustrated about for some time now and as i am paying to use the software i would like it not to lose work. I know people will say you should save regularly, yes we should, however i know i am not alone in getting caught up in actually making the model and not thinking about saving until you have finished making the current changes, which (sods law) is usually when it crashes, just as you are about done! 

Please could you consider revisiting the autosave tool and see if it can be improved upon. Thank you 

[bob55]

Alias has that feature.  Under the File menu look for Checkpoint.  This will save a dated file out at a specified time or number of commands executed.  Take a look.

[Anonymous]

Thanks Bob55, This was the feature i was referring to as auto save, My
problem with it is that it interrupts the work flow, in my opinion it could
do with a bit of revising so that it preforms the save in the background
without stalling the workflow. Also it creates lots of checkpoint saves
that take up loads of memory, all it needs to do is save 1 file per
session/ stage of alias that it keeps overwriting so that when the program
does fall over unexpectedly and Msave fails there is always a last file
available that is say a maximum of 15-30 mins old, rather than there being
a long list of checkpoints or it running out of memory. It doesn't even
have to be a new one every day (thats down to the user to save) The feature
i am proposing is more of an automatic background fail safe that is an
updated and revised version of the checkpoint save (which i don't think has
been revised since Alias went to annual releases?) a kind of perpetual
msave if you like. I am not suggesting getting rid of Msave, its a very
good life line its just not full proof, this is more of an additional belt
and braces approach. I don't know if you have noticed (it could be just me)
but it seems that the more urgent the deadline and the less time you have,
is when (it seems) something goes wrong and thats when a failed Msave
really stings. I am simply sharing my opinion.

[bob55]

We appreciate all feedback and suggestions from our users.

Saving data in another thread while your modifying the data is a challenge. 

I understand is a disruption but you can control when it happens and how many checkpoints are saved before overwriting.  Instead of automatic checkpointing some people put checkpoint on a hotkey and do it manually.

[Anonymous]

That's an idea. I already have save set to a hot key, Its just a case of
remembering to hit it often enough. I think it also contributes to the
frustration of the failed MSave's, in that if it has been some time since
saving then its more frustrating than had the regular save been more
recent, So maybe an alternative feature suggestion might be for some sort
of configurable setting that provides a visual prompt to remind the user
that it has been X-amount of time since the last save?

[bob55]

That's a good suggestion.  I'll enter an improvement on that and we'll evaluate.

The advantage of checkpoints over save is that if you've screwed up your work some how you can go back to one of the previous checkpoints. It's ment as a in session tool as they (the checkpoints) get cleared on exit of the application, but of course you can turn that off.