Check this odd occurance out

[Thee Rickster ™]

X4 MU3

 

I open a file to do some Ec'c and find 2 paths necessary flow line ghosted. I show path and only one has toolpath lines. so I reprocess both and they go dirty.

 

So I show all level and check both path and hit only show associated Geometry to find there are none. but there are 16 check surfs.

 

So I close mc and reopen with out saving.

 

I verify and the path that was still good showed material removed. I click geometry and it shows NO DIVE surfaces, yet I have a tool path???

 

So I try to mirror the path to get the other one back that is missing and it MIRRORED!!!

 

So I saved it and did my EC and all is good.

 

Weird??

 

Any body else seeing this behavior?

2nd time for me.

 

.

.

 

I tried regen display list and the surface does not show up. same with unblank entity

[bhyde]

Yep...Had this happen yesterday..I ended up nuking the toolpath and recreating it.

[Thee Rickster ™]

I thought about that too...but I did it in X3 and

cant remember exactly how I created the original surface. Part is proven an I cant take the chance of reproducing it wrong.

[bhyde]

I understand..I couldn't take the chance there there wasn't something that would give me bogus numbers in the post had I chosen that route. My part was a relatively simple surfacing path and it was no big deal to re-create it. When it happened to me, the graphics seemed to be hosed up as well..this was shortly after a verification.

[mayday]

next time that happens run ram saver and or close mc and re-open. There seems to be a huge amount of crap clogging up memory to the point things go stupid. I have to do this numerous times a day. rebuilding the display list has never solved the problems for me, only ram saver

[Rob Dusenbury CAD/CAM CONSULTING]

Just a thought.

 

Try using update folder. Choose "Update specific file types" and choose "Part files".

 

Also select "update specfic versions" and choose the version the file was created in. By design this should work.......but you never know.

 

Another option is to regen all cutter paths and re-save it in x4.

[Thee Rickster ™]

I haven't use Ram Saver since X2 MR2 Sp1 when it

dirtied all my mold component files and made associative geometry disappear. (fortunatly I just

closed with out saving and reopened it)

 

Has ram saver ever fail for you Wes?

[peon]

Rickster, I use the ram saver utility just as often as I save my part. No problems here and have been using that practice during the last 4 years.

[Thee Rickster ™]

Cool, thanks!

[mayday]

We had only file go bad from ram saver, but it was huge around 500,000kb, just locked up the system. but other than that one time,working good

[Colin Gilchrist]

I always, always do a normal "Save" before I run Ram-saver. Never had a problem once I implemented that practice.

[MotorCityMinion]

59 surfaces in one toolpath. Add a check surface to a toolpath. Regen. Verify, then say to my self, well that sux, try sumthin' else. Open up parameters to delete the check surface and bam, I have 60 check surfaces and ZERO drive surfaces. Absolute BS. Empty all my options and start again.

 

Maybe I'm off base here or just being mean but...

LOL, friggen Ramsaver at this stage of the process in any recent version of MC is a JOKE. Especially with a 64bit OS and butt loads of ram.

 

Is this what you pay buku bucks for up front, and then repeated maintenance.?

[jhjr]

Damn that would suck. What all did you break when that happened? I know I would've had a hard time not breaking something or get away from it for a few minutes to cool off. 

[MotorCityMinion]

I don't mind the glitch so much, it's the dam calc time with the tight tolerance that gets me. Usually, a small change in some parameter doesn't take that long to regen, but re slecting surfaces, checks or boundaries will take a while.

[Thee Rickster ™]

I tried the ram saver on a big 318 meg file @home on the

weekend. I will be opening it and coding tool paths later, :crossing fingers:

 

Maybe instead of designing a work around to save

ram as a utility and making MC even more cumbesome, program the architecture to

utilize ram efficiently....like, ****cam