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.
Absolutely! I've brought up this issue a number of times.
'more aware' is a good term to use i think.
You wouldn't do full server backups every night. You would do incremental backups. As far as I've seen a 3ds max file is just a package containing different types of data... mode, material, lighting, settings... Definitely some room for improvement here. The time savings would be mind blowing.
@SuperDrifter I know you can but I want to keep it turned on - it's saved my from crashes more times than I can count, I just fail to see why 3ds Max should completely lock up whilst doing so when other programs manage it just fine...
@SuperDrifter Ha! Yes, I know that. Thanks for the tip though. The suggestion is more about making the autosave feature (which is quite useful) a little more situationally aware so it doesn't autosave at inopportune moments, or as a background process instead of locking down the application while the save processes.
Also, just to add to my earlier comment, I think anything that creates an uninterrupted workflow is well worth investing time/money in... this includes opening files, closing files, saving files, loading resources, folder navigation, starting 3ds max...
the recently used auto save feature allow us to cancel auto save during the save process wich will lead to max freeze, i would like to suggest a 5 seconds autosave countdown to cancel during the countdown which will prevent max from freezing, then if the countdown finish without hiting esc button the autosave eventually save the project.
I don't know if this is feasable, but an autosave that saves the current state of the scene without locking up the entire program would have been amazing and probably the nr. 1 feature I would have wished for. Photoshop did the same thing a few years back, so whenever you save a photoshop file or autosave kicks in you can keep on working, except the saved state is from whenever it starts saving - which is super useful. When working with huge scenes in 3ds max it really slows down production, though you still need autobackups, so I hope this is something the 3ds max team can consider looking into.
A while ago I came across a script that did just that, here. After some experimentation, I found out that after 5-10 autosaves (it was a bit random), max would suddenly crash (sometimes without errors, sometimes with - again random)
So while it works in both theory and practice, there is probably some kind of memory leak or garbage data lying around causing it to crash. But it proves that it can be done, AD just has to implement it properly.
THanks, that is very good to know. Then I really don't understand why that's not been made yet. I don't know how many hours I wasted waiting for the scene to save every 10 mins. For huge scenes it can be minutes every time.
I really hope this will be one of the main things Autodesk can improve in the future.
I could have sworn I commented on this exact topic a while back. Might be worth doing a search for similar Ideas already posted, so there isn't any vote-splitting. Anyways...
I'd say the crashing indicates it cannot be done, not easily at least, and it may well not be down to a classic memory leak (which are very rare these days) or "garbage data". You get into logical problems with "working while saving", including time required to clone everything (assuming a duplicate isn't being maintained, or a much more complex delta-record) i.e. what happens if you need to save again before the first one has completed?
Kind of curious what's being done on very large projects, that could not be done on smaller (and faster) chunks. Faster isn't always about better hardware or software, good data and work organization have a big impact on larger work.
One of the more frustrating things is getting interrupted in whatever you are doing and the autosave feature is really good at interrupting.
I would love if we got a countdown timer when we get closer to the Backup interval time. That way you can prepare and possibly cancel the autosave if you don't want it to happen.
As an additional feature, it would be lovely if it got a bit more intelligent. You can have the Save As window open and be in the process of naming your file when the autosave feature kicks in and starts saving in the background. Make the autosave unable to save when doing certain things, such as having selection windows open.
So how are things going on now? We have versions 2019.1.1 and then autosave crashes 3ds max, and it takes many minutes on a very fast computer at the scene with only 2 million polys. This is not right. Someone wrote above that this is because it is an old program. But after that Autodesk created an initiative called 3ds max Excalibur (XBR) a few years ago to rewrite the 3ds max code according to the latest generation of programming techniques.
Id like it if there were an autosave feature that used the number of actions you've completed rather than a time limit; maybe based on the same ticker the "undo's" go by. When the ticker hits a specific amount (like 500) then autosave would happen rather than every set time limit.
Give users a visual count down (like a 10 second timer or something) before max will autosave so that users can cancel an autosave before it starts. A lot of people probably work with large files and whilst increasing the interval is one time to cut down on save times, sometimes it's not always feasible to keep it high.
