repeatable save corruption

[werticus]

Save the file and hit render before the save has finished results in a corrupt save file and a crash leaving you only with the autobackup.

just cost me 2 hrs i did not have gawd knows what my 10min autoback file is 2 hrs old!

[Aldaryn]

Do something processor heavy, or hasty in the time max tries to autosave, and you'll end up with a crash, an unreadable recovery file, and also the last autoback will be corrupted.

Makes you want to do incremental saves in every minute.

Sometimes I wonder, what would be like if a scene would be constantly streamed into a file. Everything you do, would be instantly transferred to the scenefile via fast and efficient database handling solutions offering the protection for your precious, and valuable work that currently max can't really offer.
I was in the development team of an mmorpg for a while, and there we used simple and free sql services to constantly record the world of the game. Players, actions, and even world meshes modifications were stored on the fly. The engine itself was very unstable, but we had almost no data loss thanks to a streamed saving solution.

Oh, well ...

best regards,

A.

[sea2stars]

Even more annoying is hitting render not realizing that Max is autosaving; has the same effect. Probably better off increasing the number of autosaves, vs the time inbetween?

[s0real]

Even more annoying is hitting render not realizing that Max is autosaving; has the same effect. Probably better off increasing the number of autosaves, vs the time inbetween?

i just did that seems the bug is still present.

[3DMK]

SAVE, SAVE & then Save it one more time....lol Hang on...better do it one more time.

I seriously end up with over 500 iterations of my scene by the end of a big job as I have been burnt too many times already by max's daily crashing.
[Some days I dream about how stable Cinema4D was when I used it for a few years ago...I think it crashed about 3 times in a whole year....]

[simmsimaging]

Simply turning off the autoback function and doing it manually has cut down my crashes enormously. You have to discipline yourself to saving, but I set up a quick button on a toolbar so it's pretty painless. I still forgot sometimes though... wish the normal autoback would just work better.

/b

[zeronove]

Simply turning off the autoback function and doing it manually has cut down my crashes enormously. You have to discipline yourself to saving, but I set up a quick button on a toolbar so it's pretty painless. I still forgot sometimes though... wish the normal autoback would just work better.

/b

I totally agree with the exception that CTRL+S is faster than finding a toolbar button

[simmsimaging]

I totally agree with the exception that CTRL+S is faster than finding a toolbar button

You could assign a keyboard shortcut to it if you want, but the toolbar is seup up on the edge of my workspace so it's easy to find. I still preferred the autoback though: there you don't have to do anything at all