Jaz
-
Posts
312 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by Jaz
-
-
Nothing in groups, I am in the habit of keeping them cleaned up.
-
I am working over a network. Moving the file to local drive has no noticeable affect. SSD drives.
Video card is Quadro M6000, delays do not appear to be related to graphics.
In task manager nothing is being maxed, CPU runs at 5%. Running multiple sessions, Vericut and/or CATIA has no noticeable affect on this MC issue.
Actual toolpath processing is not unacceptable, but just opening and closing toolpath parameters takes several minutes and moving or deleting geometry can take 20 minutes even if it is not associated with anything. The more toolpaths in the file the worse it gets, during the creation of the 1st couple hundred toolpaths performance is acceptable. Deleting all the toolpaths in a file restores SOME of the response times, deleting all the toolpaths can take several hours.
-
More information: This does not appear to be related to the file size. I deleted all solids, including drive geometry. Reloaded file which is now 232,341 KB. Still takes minutes to open a toolpath parameter or to move a piece of geometry even if it is not associated with anything.
Any chance this has something to do with Tracking Changes? it appears I have that function turned off but I don't know how it works.
-
Not processing toolpaths, necessarily. Anything I do, like delete or move geometry or open parameters for a toolpath. And opening a file takes like 5 minutes.
-
When a part gets to about 300,000Kb file size it gets painfully slow to do anything. Are there settings I can change in MC or Windows I can change to make it run faster?
Running MC2022
-
20 minutes ago, motor-vater said:
Been there done that, worked with QC they acted shocked!!!! Started happening in 2021, way less problems with 2022 but it happens. I have deleted everything including machine group and still 200+KB.... So far the biggest one we have in the shop is 620,000 KB. Its now a competition..... So my work around is after you are done designing and model preping everything, save all of your solids as a parasolid. Then open a new file and drag it over... Will drop to like 4k or what ever it should be... Then start toolpathing and your fine.. If you allready have toolpaths you are hoping to save you are Effed!!!! That 600000KB file we have takes 25 minutes to open... lol
Edit: I have a bolt that I downloaded from Carr-Lane that is like a 160,000 KB, when u delete it and save it the file grows even bigger... An empty file. I could share it if someone wants to see how messed up it is, but I fear it might infect your system with what ever problem it is we have over here
Exactly what I am seeing.
If I copy and paste anything from the file it comes with 150,000KB of invisible baggage
Deleting everything does not delete the invisible baggage
I am looking through the file to see if I can find an evil solid, no luck so far
At this point my work around is to not use anything from the bad files, which is a bit of extra work to re-model some fixtures and stuff from scratch
-
12 minutes ago, So not a Guru said:
I think Colin was just suggesting you remove the history of each of the solids, not delete the actual solids.
But I am deleting almost everything in the file, including most solids.
-
No groups
I should remove the history before I delete a solid?
-
20 minutes ago, Colin Gilchrist said:
Delete any Groups.
Run 'Remove History' on every imported or merged Solid. (Anything copied and pasted.)
Delete all machine and toolpath groups?
-
Has something to do with copy and paste. Whenever I copy any entity from one of those files and paste it, it comes with a large amount of baggage of some sort that I can't see.
File repair does nothing
-
KB, not MB. Sorry
-
Running MC2022
I have a part file that has grown to about 190,000 MB so when I began programming fixtures for the part I saved as a new file and deleted everything except the fixture geometry. When I saved it it grew to 220,000MB. So I went back in and deleted more stuff. When I saved it had grown to 360,000MB. So I deleted everything except 2 lines. It is now 330,000MD.
What is happening and how can I fix it?
I cannot share the file.
-
Here's a sample
-
14 hours ago, nickbe10 said:
Only use clearance at start and end of toolpath.
Its up nestled under Clearance. Will go to Retract height except enter and exit (to clearance).
Mind the Absolute/ Incremental settings...
No, that's not it.
It used to work. I guess it's broken now.
-
When I drive a simple contour with several chains and try to set the cut order of the depth cuts to "By depth" the retract between cuts is very high (like 500") no matter what settings for a clearance plane I set. What am I missing?
Running MC2019
-
Still no joy.
For now I will move on to work arounds
-
I spoke too soon. Doesn't work in MC2020. I am installing 2021 to see if that makes a difference.
-
Crazy, you are a genius!
Thank you
-
Here is a file
-
That check box does other things, but doesn't affect the retract.
I am using lines to drive the toolpath. I tried using the arcs but that had other issues.
I will see about posting a file
-
It backplots just like that. Clearance is locked on incremental because this is a 5 axis toolpath.
Using safety zone gets it to retract, but since the toolpath is on the inside of a cylinder the retract zone is not ideal.
-
-
When I drive 5 axis helix bores I get no retract between holes, just rapids from the bottom of the helix to the clearance for the next hole.
What am I missing?
(MC2020)
-
Remove history might work, it will be hard to know which of the 825 solids need it.
I am in the habit of keeping the temp folder clean, reopening MasterCam has no affect.
This only occurs 1/2 the time and does not seem to affect the usability of the saved file.
Speed up processing?
in Industrial Forum
Posted
The exploding file occasionally happens to me, this does not appear to be the case. Until today, today the file is exploding.
It may just be a corrupted solid that is impossible to dispose of, that has happened before.