Mastercam crashing

[Yoga]

Please help me. 

"unhandled exception occurred mastercam execution halted"

 

it is worse when trying to save program

Mastercam x5.

 

Thanks you.

 

 

[#Rekd™]

You can try contacting your reseller. X5 is a really old version of Mastercam at this point and it possibly suggests it could be a pirated version. 

[JeremyV]

Would it be possible mcam 2022 is crashing on us due to too much solid models within a program?  we currently only have 2gb vram and i want us to get these upgraded to 8gb...

[crazy^millman]

13 hours ago, JeremyV said:

Would it be possible mcam 2022 is crashing on us due to too much solid models within a program?  we currently only have 2gb vram and i want us to get these upgraded to 8gb...

To test use un-shading and will see the wireframe of the solids and change the resolution to a crazy number like .5" or 12mm and see if it crashes. If not then shade the screen and see if the crash happens if it does then there is the proof you need.

[Colin Gilchrist]

15 hours ago, JeremyV said:

Would it be possible mcam 2022 is crashing on us due to too much solid models within a program?  we currently only have 2gb vram and i want us to get these upgraded to 8gb...

Something I see all the time is people "reusing" Tooling Component Solids in their Mastercam Files. They Import, Move, and Save those models, and then continually move/copy/rotate these models.

All Solid Models (even those without "operation history"), keep track of the transformations "behind the scenes".

After you import Solid Geometry into your Mastercam File, (Especially when using Merge), use the "No History" command, on all your solid bodies, after you've moved them into position.

I also like to run "Optimize" on all solid geometry that I've imported into Mastercam. You'd be surprised how much "overhead data" you can eliminate by using these two functions.

For Fixture Plates, Etc., I like to get rid of any extra holes/features, whenever possible. I will typically keep a "featured" model on a separate level, but then will go and "Remove Features" on models which I'm bringing into Verify or Machine Simulation. You want the "outside skin" of vises, fixtures, riser blocks, etc., but having an "internally modeled feature" just creates more computational overhead.

This is probably not related to your specific issue, but removing Solid History can really help streamline your files, and get rid of computational bloat.