Carbide Create closing during editing

[DustyWoodChips (Dusty)]

I am using Carbide Create Pro build 815. I am a hobbyist…retired old fart!

Until recently I have have zero issues importing images and editing them to get an optimal image for cutting. This mean erasing unnecessary lines etc. which also improves the clarity of the final cut and minimizes the run time in carbide motion. I have not change my desktop computer, ram or anything else.

What happens is that I will be editing/erasing lines, the software pauses, the hour glass shows up and then Carbide Create just shuts down. All or any of the work changed since last save is gone. Quite frustrating.

Has anyone else experienced a similar problem and if so what is the solution?

Appreciate any feedback.

Cheers!!

[jtclose (Jim Close)]

Email support with your file. If you can repeat the issue, state the steps.
Did you notice if you computer ran out of memory ?

[WillAdams (William Adams (Carbide 3D))]

This part of the code was just re-worked in a new beta:

CC - Node Editing Changes

We just posted 817 to beta with the new node editing command. Top-line changes include: Node editing is now modal Snapping can be toggled with F4 When node editing, you can disable snapping by holding Alt/Option when dragging While node editing and hovering on a curve, you can press I to insert a node, or C to cut the vector at that point. You can nudge selected nodes with the cursor keys And of course, our code signing token disconnected itself from our remote build machine, so this beta is…

Please try that.

If it still happens, be sure to send in the Bugsplat and upload the file to that thread and let us know step-by-step what you are doing and we will try to look into it with you.

[DustyWoodChips (Dusty)]

It appears that the software crashes when there are a lot of small details that are being erased. I save the work frequently, however, occasionally I get the message that it cannot save as toolpaths have not been calculated. It seems or is possible that it crashes because of so many changes and the software cant keep up with the details. I can always restart the software and the project i was working on and continue make changes…until it get overwhelmed again. Does this make sense?

[robgrz (Rob Grzesek (Carbide 3D))]

@DustyWoodChips

Does this make sense?

Yes and no. If you’re on Windows, we’d need to get the Bugsplat report that should popup when you get a crash.

There are a few crashes that we see deep in the user interface library we use(of those, many seem to be in the video driver on their PC), and one that appears to be in our code that we cannot duplicate (yet).

The vast majority of people who report a crash do not give any contact information that we can use to follow up.

There’s no reason that CC cannot keep up with a detailed design- we torture test it with a few of the most pathologically bad files that we have received from customers. Even those really bad files just don’t include that much data for a modern PC.

So, if you get a BugSplat popup, submit the crash and be sure to include your contact information. Feel free to shoot an email to support right after so we can check out the report quickly.

But, if it always happens on node editing, be sure to try the latest beta that Will linked to. There have been massive changes to that code over the past week or two.