Michael J. Brown Posted June 18, 2009 Share Posted June 18, 2009 I don't know if it is a V-Ray issue or a 3dsMax issue. So please forgive the double threads (on both the V-Ray & Max boards). I get this error every now and then. I can't determine what exactly causes it, but it seems to basically currupt my scene and I end up having to drop back to a previously saved scene. The moment I start a render the progress line will read "Preparing tone operator". Then 15 seconds later Max crashes. Has anyone else ever gotten this error? What specifically causes it? Link to comment Share on other sites More sharing options...
mattclinch Posted June 18, 2009 Share Posted June 18, 2009 http://www.evermotion.org/vbulletin/showthread.php?t=60525 Link to comment Share on other sites More sharing options...
Michael J. Brown Posted June 18, 2009 Author Share Posted June 18, 2009 http://www.evermotion.org/vbulletin/showthread.php?t=60525 Thanks Matt, but that didn't do it. I'm not using a single RPC (moving or static). Link to comment Share on other sites More sharing options...
BrianKitts Posted June 18, 2009 Share Posted June 18, 2009 32bit or 64bit OS and how much RAM? I think that's the last step before it allocates the RAM for your frame buffer, so most likely you are maxing out your RAM at render time and you crash before you even get going. Pop open the task manager and watch to see if the crash coincides with your available RAM running out. I didn't read the RPC thread but, I know they are a huge memory hog as well which is why they could cause the same problem. Link to comment Share on other sites More sharing options...
Michael J. Brown Posted June 18, 2009 Author Share Posted June 18, 2009 32bit or 64bit OS and how much RAM? I think that's the last step before it allocates the RAM for your frame buffer, so most likely you are maxing out your RAM at render time and you crash before you even get going. Pop open the task manager and watch to see if the crash coincides with your available RAM running out. I didn't read the RPC thread but, I know they are a huge memory hog as well which is way it could cause the same problem. Boy, that would be strange, as this is hardly a RAM-heavy scene. I did discover a work-around though. I just merged everything into a new scene and BINGO! Problem (whatever it was) solved! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now