Corrupt autobak's (max)
So this is an issue that has been annoying me for the past year already.
For some reason, over half my autobak files are always corrupt!
I have been using max 2010 and now 2012 and I still have the problem. There are some issues with my laptop which causes it to crash now and then.
So right now I am making 60 autobak files with a 2 minute interval.
Whenever I get a crash or I made a mistake and want to revert back to an autobak, I usually have to go through at least 15 corrupt files, usually around 25!
Then I get a couple (around 3-6) files that actually work and then I get a couple corrupt ones again, then I get another 10 corrupt ones in a row, etc etc
It seems to be pretty random.
But this seems really strange to me, has anyone ever had this problem and/or knows a solution?
I use max 2012 with SP1 and SP2 installed.
Thanks
For some reason, over half my autobak files are always corrupt!
I have been using max 2010 and now 2012 and I still have the problem. There are some issues with my laptop which causes it to crash now and then.
So right now I am making 60 autobak files with a 2 minute interval.
Whenever I get a crash or I made a mistake and want to revert back to an autobak, I usually have to go through at least 15 corrupt files, usually around 25!
Then I get a couple (around 3-6) files that actually work and then I get a couple corrupt ones again, then I get another 10 corrupt ones in a row, etc etc
It seems to be pretty random.
But this seems really strange to me, has anyone ever had this problem and/or knows a solution?
I use max 2012 with SP1 and SP2 installed.
Thanks
Replies
I remember a few cases where it was much worse, one specifically was where I worked with meshes from old max files (max 9 files), I changed them from high to lowpoly versions and there was a lot of messy, sloppy geometry: double verts, random polygons that shouldn't be there. That was one of the worst cases, it tended to crash and corrupt things a lot. So perhaps it's tied to working neatly in a way?
Edit: come to think, it was always worse on my slower laptops. My desktop is much faster and never had much issues..
Now the only time I get corrupt files is if I go to close, haven't saved and it prompts to save. If I save it by clicking "yes" and then it closes it almost always corrupts. So I say no, save and close.
During those crashing often days it seemed that autoback files would always corrupt in some way even if I could open them they would lead to a crash sooner or later. So I bound "save incremental" (abc01.max -> abc02.max ect...) to ctrl-s and would rack up 20-30 files over the course of a few hours of work sometimes I would get corrupt batches if I worked for too long without restarting max, but there would normally be something I could use that was recent enough. But avoiding autoback files seemed to help stability and corruption quite a bit.
I'm not really sure what solved it, but I think it was probably the jump to 64bit, more ram and more stable versions of max.
This doesnt sound too bad but imagine this happening like 20 to 30 times in the same project...
Same at work really, nobody complains about Max crashing often, everybody has decent desktop computers.
I should actually check if I have the same problem on my desktop, havent done that yet.
Also I think having super high poly scenes might run the risk as well. But thats prob bs. ha
As I said, I had windows installed on an SSD and a harddrive now, both give me same issues which really lead me to believe its a max issue... I've tried to do some googling but didn't really find anything which really surprised and confused me, which then leads me to believe its a hardware issue...
Basically I'm lost now, heh..
EDIT: It happens to both low and high poly scenes. The harddrive looks like its in 100% perfect health as I've ran pretty much any diagnostic I could find on it (Seagate Tools aka SeaTools, Hdtune, etc)