It's a little time saver. Once launched, it will automatically regenrate any operation after editing the operation through the parameter dialog. Launch it again to stop the automatic regeneration. autoregen.zip Thanks to Michael Pfeil from InterCAM for this idea.

Yes. But, you can also edit an operation by clicking geometry or tool inside the operation manager...in this case autoregen will not catch it.

I started with v5 in '95. Fanboy through v9, hated X1. Stayed with V9 until at X5 it was was finally usable, now using X9. Hate 2017+ with a passion. IMO the ribbon interface was even worse a decision than adding separate machine and control definition files, which we were promised would eliminate the need for posts. Still waiting for a good version that's reliable and that has enough advances to outweigh the cumbersome ribbon, or that has enough customization options to let me make it behave the way I want it to. The hammer handle should be made to fit my hand, rather than making me reshape my hand to fit the handle.

https://www.mmsonline.com/articles/vector-programming-eases-five-axis-aerospace-machining

Yes. the String Function 'slin' stands for "String List In". It uses an "index variable" (the variable in your "ordered list of numeric and string variables created by MP), and an "offset" from that index variable, to determine "which string variable" we are editing. There are some decent examples of how to use the function in the documentation. smtap : "G84" smrigid : "G84.2" # Canned drill cycle string select sg81 : "G81" #drill - no dwell sg81d : "G82" #drill - with dwell sg83 : "G83" #peck drill - no dwell sg83d : "G83" #peck drill - with dwell sg73 : "G73" #chip break - no dwell sg73d : "G73" #chip break - with dwell sg84 : "G84" #tap - right hand sg84d : "G74" #tap - left hand sg85 : "G85" #bore #1 - no dwell sg85d : "G89" #bore #1 - with dwell sg86 : "G86" #bore #2 - no dwell sg86d : "G86" #bore #2 - with dwell sgm1 : "G76" #misc #1 - no dwell sgm1d : "G76" #misc #1 - with dwell sgm2 : "G81" #misc #2 - no dwell sgm2d : "G82" #misc #2 - with dwell sgc9 : "G81" #custom #9 - no dwell sgc9d : "G82" #custom #9 - with dwell sgdrill : "" #Target for string fstrsel sg81 drlgsel sgdrill 18 -1 # -------------------------------------------------------------------------- # Drilling # -------------------------------------------------------------------------- pdrill0$ #Pre-process before drill call sav_dgcode = gcode$ #Capture gcode for 5 axis drill #Set correct Tap Code, based on tapping mode if rigid_tap, smrigid = slin(sg81, 6) else, smtap = slin(sg81, 6) Here is a quick sample I whipped up. The "slin" function uses that "index" variable (1st parameter), as the starting string, in the Variable List. The 2nd parameter (6), is the "offset" from the 1st string. This is a "zero-based" index, so an offset of "0", means, replace the string that is listed as the "index" variable. An offset of "1", means replace the next string, 1 space below the index string. In our case, "sg84" is 6 variables below "sg81". I could have also used the following to accomplish the same thing: smrigid = slin (sg84, 0)

This has happen to me also, but only once.. Where mine differs though is I lost all my saved data up to that point, so my file went back to the first time I saved it, witch was file right after opening up model.. we are having network problem also, so wasn't sure what to think about this.. I would be interested in knowing if they ever resolve this , that for sure p.s. really don't understand the decision of the color pallet anyways, at least older version you had a check box if you wanted to always use large color pallet... to me this was a step backwards

X+ 2019 has been updated. Get it here. fixed - screenshots on high dpi displays should work now as expected

Try getting a step/stp file.

if you can get them to use Parasolids format, it's better than iges.

I guess my method could be considered lazy or working too much. I would create curve on one edge on all of the holes I wanted. Then either method would work in 2d or 3d assuming you use incremental and all of the depths are the same.

Most important thing in 4 axis is to make sue your planes are correct. Machine need to know where bottom plane is in relation to table, and distance from table to top of part. Also like Dave said you need to sync it in Mastercam, or at least you used to. I dont use it anymore. If you sync by entity i means you have the same number in top as in bottom. If not you need to create branch lines connecting them and sync by branch.

This is usually straightforward, you just need to chain top and bottom wire path. Just pay attention to synchronization as any ruled surface creation. I guess you already got it but you also need a power Mastercam tech file for your machine definition.

Yes I have used Autocursor like that since X came out. I had every possible function on the RMB when X1 came out. I realized real quick not a good move. QAT has become my new toolbar and customized the ribbons thanks to BenK giving me the idea. I reduced 9 ribbons down to 5. If it didn't lock up Mastercam I would reduce down to 4, but that is not possible to move Machine items from the Machine Ribbon it will crash Mastercam moving anything from it to another ribbon with room.

Do you have Tl manufactor selected? If so, change it to Tl Mfg code. It was change in 2018.