out of memory

[fredjr]

when i calculate it said "out of memory " what does that mean???

[Adrian]

Your toolpath is too complex for the amount of RAM your computer has available.

I've only ever seen that with massive v-carve toolpaths (which aren't in Cut2D) so not sure what would be causing it.

What are you trying to do job and toolpath wise? Can you attach a copy of the file?

[fredjr]

its just a simple file with a 1/8" bit cutting a pocket out around a name

[Adrian]

Check your vectors for errors in that case and make sure you haven't got something else running on the computer that is eating up all the memory.

Attaching a copy of the file is the best way to get a definitive answer.

[fredjr]

i think this is it

[gkas]

I don't see any problem with the project, but it gets a Out Of Memory on any toolpath, and I have LOTS of memory. Does this happen to all projects? Try recreating this from scratch. This may be one for Vectric.

[SteveNelson46]

I cannot create any toolpaths in the original file so I created a new instance of Aspire ( I don't have Cut2d) and copied everything from the original. Everything seems to work okay with a V-carve and a profile toolpath. I don't have the font you used so I changed it to Arial.

[fredjr]

is there a limit on the cut 2D program

[fredjr]

thanks i will try a new one

[gkas]

is there a limit on the cut 2D program

It failed in Aspire with lots of real memory.

[Rcnewcomb]

There is something odd with the file. I converted the text to vectors, and then exported the vectors as an EPS. I created a new project and imported the vectors. Everything worked fine, but I could not get the original file to calculate.

My updated version is attached.

[Adrian]

The only time I've heard of something like this was when the vectors had been stored off the z plane so, although they look normal, internally they aren't at the zero level. I guess they were imported from another program?

[gregk]

i think this is it

The file has a corrupted toolpath list. We have fixed the issue that caused this to happen in V10.507, but the file was created using V10.504. Please consider updating to the latest version.

The easiest way to recover your file is to start new job and import vectors directly from your corrupted .crv file.

Greg K

[fredjr]

thanks i restarted the program and it work fine and also added 16 ram of memory too lol