Max Has Lost It's Mind

[Jason Stewart]

This isn't a Vray issue I don't think but I don't know where else to ask. I have a deadline Friday and two days in a row my file has gone berserk.

My pointer is constantly the spinning blue circle and in the status bar it flickers between "Click or drag to make a selection" and "Press ESC to Abort Subdivide Meshing". This is after opening the file and I can't hardly move or click on anything it is super slow.

I am running max 2014, vray (obviously), Forest Pack, Railclone, Grow FX and I think that is it for plugins. I tried moving the plugins folder and making a new one and I have the same problem so I don't think it is plugin related. There is no way I can finish this project if I can't move or click on things, I am at a loss for what it could be. Anyone seen anything like this before?

[Rens]

No, but did you try merging it into a new scene? Other that that is there a key stuck?

[Jason Stewart]

I don't know what the problem was but I selected everythign that was visible and converted it to editable poly and it was fine then...I lost some of my railclone stuff so I think one of those must have been the culprit. I have rebuilt everything again for the 2nd time and hopefully it doesn't happen again.

I did try that. No key stuck, I have restarted my computer and everything else works fine. When it happened yesterday I found a file from 4 hours earlier that worked fine and after trying to figure out what the problem was for several hours I just started over from there. Today, same thing happened.

[Alex_M]

Well, that's Max for ya! It will F you up in the least desirable moment for no apparent reason. I know because I've had my own little "adventure" yesterday with Max completely breaking down. Or was it a couple of days ago? I don't even know anymore, days seem to blend with the lack of sleep it has caused me. Out of the blue it stopped loading on one of the workstations for no reason whatsoever (my colleague has not changed or installed anything on the PC) and this costed me at least a day to fix and of course at least of day of halted work. After trying everything I finally gave up and uninstalled the whole damned thing, reinstalled it and configured it from scratch to a working state. Not the most fun way to waste my day (or two) to say the least! Knock on wood, it now works fine.

[Jason Stewart]

It amazes me every time this happens that it is still this unstable. I cant imagine how people are able to work on bigger scenes, I am just trying to render single house!

Maybe I need to learn to use Xrefs more efficiently but it's always a pain to change materials or some other small detail later on.

I am finally running my final (hopefully) test render before pulling the trigger on the final. Should have had this done yesterday but all these crashes and starting over is killing me.

[jacksc02]

Do you have to use xrefs?

[Morbid Angel]

it maybe that its trying to evaluate something and getting hung up on it. Does it work fine in a clean scene? if so, perhaps isolating an object which might be causing the issue could solve your problem. I would also try switching viewports to different modes perhaps it can help isolate the issue.