mrucereto

My office is currently running Max 9 on both 32 and 64 bit stations. Since our move to Max 9, a lot of our files are being corrupted. The majority of the corrupted files are being worked on and saved from one particular workstation running Max 9 x64. There are 3 other machines in our office that are identical to this workstation. The only difference that I can ascertain, the person at this workstation likes to have multiple max sessions open (sometimes 4 scenes). My thoughts are that this has something to do with the corrupted files.

I just wanted to get people’s thoughts of having multiple instances of Max running. My personal max practice is to only have one instance running, and if for some reason I need to jump in another model I will save and close that session, then open the other file.

We are still trying to narrow it down, any thoughts would be appreciated.

crazy homeless guy

interesting. i am on a 64 bit machine, and often run 2 or 3 instances of max at any given time. i do experience corruption quite frequently, but i never thought it to be from that...

i like to work with xref'd scenes. typically around 4 or 5 xref'd scenes to a project. my corruption problem typically happen in the master file where the other scenes are xref'd to. the file will start crashing while trying to load the xref'd scenes on opening. i have a work around, so it is more of a neusance than anything.

i never considered the fact that i was running multiple instances to be causing the corruption though.

___

edit: i am on a 64 machine, but running max 32.

__________________
travis schmiesing

DavidR

I haven't made the move to 64-bit yet, but I typically have 2 or 3 Max sessions open -1 doing render tests, one modeling, and maybe one rework, etc, and I almost never have an issue, and I've worked this way since Max2. I get corruption maybe 3 times a year -usually due to a crash- but I always use iterative save, and I always keep the last 2 iterations because we all know how flaky Max is.