Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Submitted byAnonymouson02-01-201702:40 AM
Status:
Implemented
Make Autosave Efficient
When you have a heavy scene the autosave function locks up max and interrupts your work flow. Also sometimes it starts to save when you are in the middle of a complex setup which may lead to a crash. It would be great if the auto save happened without affecting the current session of max.
My worries with putting in a Autoback which kicks in after X seconds of inactivity would mean that a modeler or someone working hard for an hour could easily lose their work if Max crashes after a whole hour of modelling. I've done client remote sessions lasting hours where we're constantly tweaking cameras, moving objects around.
Also, if you work for like 10 solid minutes on something, then jump over to another application to respond to a quick email or chat message, your max will lock up doing an autobackup and you'll have to wait to get it back. I'd find that more annoying. At the moment if you're working and you want to stop an autoback you can tap Escape key, however it doesn't always work.
Background auto-saving would be the best thing but as I understand it, it'd be quite tricky to implement at the moment. I always encourage people to use VRMesh/XRefs etc to keep their working file as light as possible so autoback times are quick.
Some quick fixes that could be implemented would allow better performance with Autoback.
a) Changing scene/object selection should not set dirty flag.
b) Modal dialogs should block autoback, this should stop when the Escape key doesn't work.
c) There should be a 10 second count down before an Autoback down in the status bar where it says "press escape to cancel autoback"
d) When max is idle, when it autosaves the next autoback timer shouldn't start until the scene is next dirty... this will stop the annoying thing when you have an idle max session for hours, then as soon as you touch something it wants to autback again.
e) playing animation should pause autoback timer
f) SDK/Maxscripts methods for pausing autoback timer for certain things like IPR or simulation
g) Disable File Metadata Stream writing in Autoback files, it's really not needed and can speed-up saving quite a lot.
h) Escaping X number of Autobacks in a row should flag to the users, So many times I've escape 3 in a row for max to then crash.
@alex We generally do not give timing on our upcoming releases. I can tell you that one of our teams has already been actively working on this. If you would like to see the current progress you can join our 3ds Max beta program.
Appreciate the update, and the progress with Autosave has been welcome, but the absolute main thing for us still remains "unimplemented": background saving! The current/new system is indeed an improvement, but it's been almost 7 years since this original request and AD have not managed to find a way to get Autobak to work in the Background like Photoshop does...
I don't think it should be beyond the realms of possibility for a team like AD to figure this one out over 7+ years, all things considered.
Thanks for the update and appreciate the work that has gone into improving this feature.
If and when can we expect a non-intrusive autosave? We are all paying quite alot of money for using this platform and dont seem to be getting many of the actual improvements that are regularly being requested....
