Haven't tried that. I'm not running the Dell install version just bare bone XP and the correct Nvidia FX4500 driver. I have no reason to believe that graphics card driver is the cause since it WAS fine in X3 until X4 gets installed. Also why would bad video driver effect just 3-D toolpath regen and block it from writing a temp file to c: drive?? Another thing worth mentioning. I noticed after pulling up the file and clicking params that a pop up "STL File Not Found" message comes up. I have like always just repathed to the correct file, but dont remember seeing this before in X3 unless I was in machine files. X4 seems to be looking for the STL at each operation now...possibly this is part of the reason I get the irritating 2-3 second pause before params open?? Also I see another possible thing in common. The files this happens in I have multiple machine groups in and the STL is pathed to group 2. I will look more into this. Try to dump a machine group and see if I still get the crash. Update:--Multiple machine groups not the cause. I deleted the group 1 and tried to regen a small file with only 5 ops and it crashed. [ 11-21-2009, 03:24 PM: Message edited by: Verndog ]

quote: Post hoc ergo propter hoc This very likely is not true (I'm at about 98% certainty with this one) as MCCore.dll is not shared amongst versions, and that is where the crash is coming from. We also have a few users reporting the crash that have never installed X4 or X4 MU1. I have a debug version of X4 MU2 that I would like to try on a few of the affected computers. If anyone is interested, please email me at [email protected]. I can send you a link to the build. Thanks again, everyone. Chris...with all due respect...I would disagree. I loaded my new system, and installed just X3 and everything including problem files and toolpath regened correctly. Then...as soon as I installed X4 (not MU1 even) the problem came back. And not only in X4 but in X3 also. This is very important I believe. I've only run this Dell Xeon 3.0ghz a couple of weeks, but have seen 1000's of 3D toolpaths generated in X3 and NEVER seen this error before. 2 of 5 of us in my department have this crash, both on Dell machines. I may take this all home with key and try on my P4 Duo and see if I can get the same file to act up. I just ran the new MU2 with mccore.dll patch with same end result. Still crashing on regens.

quote: Keep the information coming, guys. So far we know ..... 6)It is something new written into Version X4 and X4MU1 that has a trickle down effect with all version X Mastercams.

AVG version 9.0.707

Also, you can chain the tops of ribs and overcut the GEO by using minus material to get the cutter over the edge of the wall for facing ribs with an endmill.

After changing color.. when system promts you to save give the configuration a new name like FRED.config Then in system configuration -- Start / Exit--set the top dialog box to call up configuration FRED.config at startup. This should save all your choices and pull them into all files opened.

quote: Got a new puter, in the top veiw my arcs look like an ellipse. What gives? Is there any settings I can set to eliminate this?As posted, a monitor will only display correctly (especially the new widescreens) at the native resolution. To make sure I draw a full circle, fit screen and scale the screen 2 directions to check display. The issue with widescreens also messes with angles, draw a line a 45 degs. and you'll have something else... and parts just not looking correct when viewed on a widescreen not in native resolution. BTW the native is usually the highest resolution your monitor will perform.

quote: Been away from MCAM a few days. The new 2010 Esprit came Monday and I've been checking it out.A shop I worked for 12 years ago just changed over from Mastercam to Esprit. They could not get mill / turn post to work on a new Mori and said thats it. Another decent sized shop with 9 seats 5ax I was Supervisor for recently changed to UG. I hope Mastercam doesn't get complacent and pull a GM on us....if so it will be all over before they realize it cuz its already happening IMO.

quote: IT funny it started off once in a while, then intermittent, then BLAMMMMMMMM constantly at every inappropriate time. Two machines for me too I concur with that....everything except the funny part. I started a new job a month ago and this issue is causing ALOT of unecessary stress that should not be there. I did notice the same thing, happened a time or 2 then more then full slam. Today I reset the folder that temp toolpath writes to into a folder in root C:...nothing else in that folder, also turned off system restore...NOTTA. Same problem with X3 and X4 regens. Even files I posted before in X4 now I cannot change a damn feedrate and regen without crash. I'm not reloading windows again that is a huge waste of time and accomplished nothing except false hope. What I may end up doing is removing X4 from the Dell Xeon and running just X3. And I will have to bring in my laptop to run X4 and make that my corrupt computer 2 that supports the X4 files I cannot turn back time on. This way I can catapult the laptop into the Xterminators living room when X4 thankfully goes away. Ya...thats the ticket.

quote: I seem to have missed this one ... where is "tool plane" in verify dialog box? Under the Files tab in machine properties use the Stock Setup then Stock View tab. You can pick a saved construction plane there to take the part from 1 orientation to another if the part moves from 1 machine to the next. Using this keeps from using Transform STL that can corrupt the STL and tend to waterfall surfaces that should be contoured. 1 easy way to pick and save tool planes. On original operation save 2 lines, a long X+ and a shorter Y+ from X0Y0. Save that GEO where you can find it later. After running operation xxx then part moves to new machine, pick the old X+ and Y+ lines and save the toolplane in a named view...say "OP1-STOCK". Then simply pick OP1-STOCK on next operation Stock View Tab and it will re-orient the part STL to your new coodinate sys.

Sometimes you just have to open up tolerances to get thru large parts and get on to something else. Mastercam verify hates faceting and bull nose 3-D roughing with small rads. A couple things to try without having Vericut. Filter toolpath to reduce faceting. Increase tool and STL tolerance in verify. This does not mean your STL will be off that far, just that more allowance is possible. Do not use transform STL to move part to new position, use tool plane in verify to move part op to op. In early operations use drop down speed / quality toggle toward speed before saving. (Run on quality to check, then drop down 2 notches toward speed to save and cut in the next operation)...this helps alot! Finally USE BACKPLOT!! Save GEO (make sure you are on endpoint backplot before saving) to new level and look for any discrepancies in toolpath GEO. Should be smooth and not be backing up on itself. Many gouges are the result of Mastercam losing which side to comp the tool on complex merging surfaces. Turn on a few surfaces (on their own layer) that could be problematic and gage toolpath GEO to those. In tight stitching often you can spot problem areas from weird or irratic moves (GEO)....and they DO happen. This will eliminate 99% of issues without Vericut or other expensive "work around" softwares.

I've been using Mastercam since 1986, and am seeing a sharp increase in area shops going away from Mastercam....there is a reason for it. I've used other systems over the years and always come back to Mastercam one way or another. Mastercam needs to cut the fluff and get their software WORKING reliably. Since Version X the users have become the guini pigs and the literally millions of man hour $$$ are on their shoulders for buggy releases. X4 is a major disappointment and offers me little to nothing over X3. CNC Dont bother releasing a new version MU2 until you get all the toolpath parameter pages the same for all toolpaths 2-D, 3-D, and 5ax. Hunting for coolant or stock to leave ect. on various different menues depending on the toolpath your in is a joke. Freezes opening parameter and operation manager from machine to machine are a joke. Lost files from toolpath crashes on 3-D toolpath regens are shameful and costly to the customer in tough times...especially on a maintanence release it's STILL THERE! Not feeling the love with X4.

I can confirm the issue is with Version X4. I haven't loaded X4 MU1 yet and as soon as I installed X4 and regened the file in question (using version X3 that worked previously) I got the error again. This is with a brand new 2 day install of XP with latest SP3 updates. My guess is both X4 and X4MU1 are Fubar. I see nothing in X4 that would make me miss it. Slower toolpath param open (machine does a 2 sec. stall), mixed new and old parameter methods with 3-D toolpath being left behind in V X3 style ect. Looks like another rush release IMO.

I just re-installed all of Windows XP and Mastercam thinking I had a currupt system because of the TP regen memory access error. I now have X3 MU1 installed and system working well... and am about to load X4. Has this been pinpointed to X4 MU1? If so I will avoid loading it and put up with the "other" issues of X4. I get this temp file access error often on large 3-D toolpath calulations. Most often during regen, but sometimes on initial toolpth as well. Very frigen irritating with TONS of lost production. GRRRR!