quote: Are you running Mastercam X MR1 SP2?Yes, I am using MR1.

so...how exactly does this c-hook work? I am running it but getting an error message...

I personally would like to see it made a tad bit larger. However, it might be best to make it an option so that those who want it bigger get it bigger and those that want it smaller get it smaller... but that's just my .02

Roger, I have tried the "No Front Buffer" option and can tell you that this did not have an impact on my backplotting issue. See below for a visual... I am however, pleased that these options are making into the configuration of the software. Any other ideas? Can you verify if you also have these problems? Thanks.

If, I have "Quick Verify" turned on, the tool flickers, but remains in the location it should be. If, "Quick Verify" is turned off, the tool will move back to the last position it held before the current point. I double-checked one of my mill files and it was the same... quote: I have the same problem, but if I zoom in or something like that it will usually show exactly where the too is.Yes...you are correct, zooming in closer does move the tool back to the correct position in the backplot.

I have the same issue with backplotting in X. It drives me nuts. Now, I am not 100% sure, but I wanna say this only happens in lathe, for me. I am going to be following this thread very closely. [ 03-09-2006, 08:58 AM: Message edited by: mross ]

for extending lines I have found this useful...I analyze the line and add or subtract whatever amount from either the start point or end point... give that a try...HTH

perform a search...this was covered already...you have to edit your registry...

yes...when i post files from any of our posts...i am getting a *.sub file as well that contains no data...

A quick question...maybe it's already a known bug... When in lathe backplot, if you expand the dialog box, in the info tab it is supposed to give you cycle times...however where it is reporting this info, I am getting "Invalid Feedrate" and the details tab reports my feedrate as -.004" IPR. The rapid feedrate is showing correct only the cutting feedrate is showing "Invalid Feedrate" Can someone confirm if this is happening to them or not?

any idea when we can expect SP1??? year or two...j/k

is X not looking at the predefined variable "posttype" any longer? I have a mill/turn machine that uses the variable "posttype" from V9 for controlling the output of bits of code at a specific toolchange and now it's like they aren't even there...just goes right through and outputs code at all toolchanges and it's really dependant upon seeing which posttype it is... basically what it boils down to it: in v9, posttype = 1 was for mill and posttype = 2 was for lathe and if I was going from a turning tool to a milling tool i needed to stop my spindle and the code looked like: code: ptoolend #Read from buffer 1 for prv_, current and next tool info #end tool here, current and next valid sav_rev = rev #Axis Sub does not update to rev pcan if n1_gcode <> 1000, [ toolno = t * 100 + zero sav_gcode = gcode gcode = zero coolant = zero pbld, n, pscool, e if posttype=1, "M05", e if posttype=2 & n1_ posttype=1, "M05", e now i get M05 at every toolchange

try pricewatch this website has almost everything HTH

quote: what's with these .sub files that are just empty.good question...i was wondering the same thing...but i'm sure someone is gonna come along and demand we read the manual

why is it that my stock does not update while backplotting my toolpath using X/Lathe. i have already disabled hardware acceleration in config because I had some issues with the tool backplotting. i also have updated to the latest video card drivers. i am using a 3dlabs wildcat vp880 pro.

from what i've been told...if you use the control to create the toolpath via it's conversational capabilities it will work...but we do not use that to program the machines...so therefore we don't use cutter comp on 5-axis toolpaths. what we do use is a taper-mill and then you can adjust the tool in z, to simulate cutter comp.

quote: x install does not effect your v9 what so ever..on the contrary...i did notice that when i'm in V9 my levels manager has a different look to it...no functionality lost though

quote: I spray myself down real good with Deep Woods Off. No bugs yet.too funny paul, i needed a good laugh. cheers

quote: Optic mice are cool....+1000 Murlin but i have to agree w/ the general concensus here, i was f'n livid when i learned that they removed the old selection hotkeys. much faster the old way, in my opinion. i guess i have a free hand to slap all my operators now

not exactly sure what you a refering to...enlighten me please...

i have discovered two bugs which have been logged by CNC software...and that's using X for no more than 5 total hours...so don't tell me it's not buggy... personally i think X is great and look forward to using it everyday, like V9...but there are definitely some issues that need to be worked out..

i reported this to [email protected] and they have recorded it as a bug...

i reported this to [email protected] and they have recorded it as a bug...

yeah...i thought the same thing...except it won't retain those values either

Phil, you can't use cutter comp on your DMU.