I found this explaination (below) but to be quite honest, can hardly make sense of it. Anyone that knows of this error or has any idea what i can do to stop maya crashing in this way please let me know!! Thank you
Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.
One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls the Windows API function DebugBreak. When using the debugger, DebugBreak will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called.
Another way to find a call to a pure virtual function is to set a breakpoint on the _purecall function that is found in PureVirt.c. Breaking on this function has the advantage of keeping the stack intact so that you can trace what is occurring.
Ermmm,.. How do you manage to do this all the time Heather? Computers just do not like you it seems.
ReplyDeleteCouldn't tell you what the hell this error is about, but does it happen every time, despite restarting?
This comment has been removed by the author.
ReplyDeleteI dont know what the message means but I get that one and the fatal error message a lot of the time. I get round by making a duplicate copy of that file under a different name, or resaveing under a different name as soon as i open it. Doesnt work every time some times needs a few trys. Good Luck.
ReplyDeletehmm i tried that too, its really strange if i re open the scene it will crash as soon as i move the time slider (which when creating an animation is not happy news) it will do this for maybe three times and then seem to work for a bit until it wil randomly crash again. ergh i just keep saving like a lunatic but if you get any more ideas let me know! thanks for the comments though
ReplyDeleteTried it on other PCs then your own? Weird crashes and bugs might sometimes be due to messy or low memory.
ReplyDeleteThe only thing I've heard causes this error is badly scripted mels. But I'm guessing this is not the case here if it happens on just on this one specific scene. Then it's could be a 'bugged' node somewhere in your scene that refers to things it shouldn't. You could do try narrowing in on the problem by deleting objects/animation/shaders in the scene and see when/if it stops crashing. Deleting history and cleaning up the scene obviously if you haven't already. Or saving the file as as ASCII (.ma) and having a look through it for any virt_func perhaps..
An interesting note here too, when you delete a shader, it will leave behind the placement nodes, the file nodes etc that were attached too it. You have to go through those tabs in the hypershade and delete them too. If you're like me and makes a lot of shaders during the modelling process, you ought to go back and clear that up. It slows render times and can speed up Maya too. Something in there could be causing a problem. Not sure it's related to this though.
ReplyDelete