What is this all about. It crops up from time to time. Regardless of if we click ‘yes’ or ‘no’, the Max session locks up and will not recover (it just sits at the Building Light Cache stage). We must crap out of Max and re-load. The problem is that more often than not, it corrupts our Max scene so we need to resort to backup files.
I’m not sure right away… it’s the first time I see this. Do you have auto backup enabled? We do have some fixes that may affect this for the next service pack though.
Happen often to me too. I suppose is a 3dsmax RAM usage problem, but it’s my idea based on the fact that when in material editor i use EXR maps (high res maps) and then I start render it gives this message.
Happen even with heavy scenes only after some test renders it appears (fortunately i save 2 files or more each work to get a security file to continue to work onto)
Would be nice to know the exact reason of this problem
I use max 2011 64bit on win 7 64 vray 2 sp1
Hmm, the material editor pointer is interesting; it turned out that the 3ds Max auto backup can kick in during a swatch render, which will corrupt the scene, so for the next update we had to disable auto backup during material editor rendering.
autoback up in max causes more problems then does good. We had to write a prompt window which would pop up in user specific time for autoback up, otherwise it would do all kinds of crazy things when you did not want.
I’m still getting this error (vray_client_scene.max is possibly corrupt) way too often too, now with Max 2013 x64 and Vray 2.30.01. Same as described by tricky and pengo: Max asks if you want to resave (which only saves a corrupt file) and crashes. Happens when hitting render, I usually have the material editor open.
It’s quite ironic that enabling automatic backup causes crashes… i’d rather do without the irony