Repair File feature

[beej]

How often do you guys use this?  It seems like since MC2020 I have to use it on every file and sometimes multiple times a day.  Using 2022 now. not sure what's going on but it gets frustrating.

[neurosis]

I had to use it some time back but I was using version 2021 at the time.  It borked my file up so bad that I had to use a backup and restore it. The file was several versions old so I assumed that may have had something to do with it wrecking the file. I haven't used File Repair once since 2022 knock on wood.

[JParis]

Almost never

[beej]

Almost never

bummer!  I got to figure this out.

[JParis]

Almost never

bummer!  I got to figure this out.

What's your system spec's"
How big are your files on average?

What is happening that makes you have to use the Repair function?

[beej]

Almost never

bummer!  I got to figure this out.

What's your system spec's"
How big are your files on average?

What is happening that makes you have to use the Repair function?

my system is a Solidbox precision 5820 purchased in Feb,21.

my files range anywhere from 2 mg to 250 mg.  But size doesn't seem to make the difference.

I always notice it when creating 3d Highspeed toolpaths. When I tell it to detect the limits on Zdepth it will give me numbers that don't make sense. That's when I will have to stop and repair the file.  If I don't repair the file at that point all of my 3d HS paths will turn dirty at the next autosave. which is when I also realize that I need to repair the file.  I might repair the file on the first part that I start to program. and it will be fine.  But then if I turn on another level and start to program a different solid, using surfaces to cover holes, or what not, I will probably need to repair the file again.

[gcode]

When I tell it to detect the limits on Zdepth it will give me numbers that don't make sense.

are you using WCS on your files?? the numbers you are seeing may be in Mastercam workspace, not your WCS Workspace

[crazy^millman]

I quit using it in 2021 since it was combining arcs in your files. I would have toolpaths and solids created with arcs that would go dirty when I ran the repair file because it was moving the arcs to different views. They were not physically moved, but because their view changed everything done with them would git dirty and sometimes make the work unrepairable and I would have to go back to an older saved file to get back what was destroyed.I have a number for it somewhere. I just restart my Mastercam every few hours and good to go.

[Jeff]

I haven't used it since 2020 when the memory leak was insane. I just resorted to restarting Mastercam every 2-3 hours to prevent a crash and loss of work.
I can't recall it messing up one of my files though. Damn.

[byte]

I quit using it in 2021 since it was combining arcs in your files. I would have toolpaths and solids created with arcs that would go dirty when I ran the repair file because it was moving the arcs to different views. They were not physically moved, but because their view changed everything done with them would git dirty and sometimes make the work unrepairable and I would have to go back to an older saved file to get back what was destroyed.I have a number for it somewhere. I just restart my Mastercam every few hours and good to go.

Yes, that's correct, Cnc added a call to combine views to repair file, if you call combine views PRIOR to generating geometry it should work.
The issues is with arcs and combine views.

[byte]

bummer!  I got to figure this out.

What's your system spec's"
How big are your files on average?

What is happening that makes you have to use the Repair function?

my system is a Solidbox precision 5820 purchased in Feb,21.

my files range anywhere from 2 mg to 250 mg.  But size doesn't seem to make the difference.

I always notice it when creating 3d Highspeed toolpaths. When I tell it to detect the limits on Zdepth it will give me numbers that don't make sense. That's when I will have to stop and repair the file.  If I don't repair the file at that point all of my 3d HS paths will turn dirty at the next autosave. which is when I also realize that I need to repair the file.  I might repair the file on the first part that I start to program. and it will be fine.  But then if I turn on another level and start to program a different solid, using surfaces to cover holes, or what not, I will probably need to repair the file again.

Repairing the file purges some of the memory used in undelete/undo, you can also save and reload the file.
Limiting the number of undo events can help you reserve more memory

[beej]

When I tell it to detect the limits on Zdepth it will give me numbers that don't make sense.

are you using WCS on your files?? the numbers you are seeing may be in Mastercam workspace, not your WCS Workspace

yes, I do use WCS.  the problem isn't so much that the numbers are wrong, but that those numbers are an indication that there is corruption in the file, which causes all 3d HSM paths to go dirty.

[byte]

When I tell it to detect the limits on Zdepth it will give me numbers that don't make sense.

are you using WCS on your files?? the numbers you are seeing may be in Mastercam workspace, not your WCS Workspace

yes, I do use WCS.  the problem isn't so much that the numbers are wrong, but that those numbers are an indication that there is corruption in the file, which causes all 3d HSM paths to go dirty.

In file -> configuration -> Undo -> Select -> Limit the Number of Undo Events, set a reasonable number of undo's and size in megabytes

[byte]

Toolpaths, memory buffering should be set to 90% or so

[beej]

[quote="Thee Byte™" post_id=13159 time=1625840719 user_id=50]
Toolpaths, memory buffering should be set to 90% or so
[/quote]

mine was set to 50%.  I just bumped it up. I don't know how it got set so low.