In 2020 I can somewhat do what you're saying, but ... when I attempt to create a line tangent to a corner rad. In prev versions I could select the rad to the closest side I wanted to create a tangent line from and then enter say 60 degree, it would create that. Now in 2020, If i want a tangent line from the top side of the rad, I have to enter the angle first, get to the closest edge of my rad, and then draw out from there otherwise the line ends up on opp edge (like in attached). Guess I never noticed this until now.

I use both depending on the project. When spinning, it ensures the form is created for the rounds of the part (allowed turn profile). A lot of times, we have models with vent flats, if i cut thru (slice) that vent and use the profile, the part would be turned under size by the depth of the vent. When using slice, i use it more to verify/get locations of say angled holes/water lines, etc. This was shown to us quite a few years ago, but i'm sure there are more advanced ways now. As of now in mcam2020, there are still issues with slice in the turn profile mode, it generates nurbs instead of the lines/arcs. See Ken's response here. http://forum.mastercam.com/Topic31976.aspx

This has been going on for a bit now. Even as PB5 starts, its still an issue. We found some issues with importing (tools/geometry/ops) that were causing some of this. http://forum.mastercam.com/Topic28516.aspx#bm31608 This is one of the bypasses Deb Rossing suggested.. "When you open the second session and load the machine, DON’T do the stock setup. Import the operations first. THEN do the stock setup and see if you get the additional planes. Our money’s on no new planes created."

Check and make sure you are doing a spin profile and not a slice. Ken replied to my issues with the slice/spin issue in the the mastercam forum here. http://forum.mastercam.com/Topic31976.aspx

When Deb and I went round and round on this issue trying to get it figured out, here was the work around they suggested. It does seem to work at eliminating the extra planes. Running mc2020 pb2/pb3 - lathe We were opening a new session with a solid, then setting all stock setups, machine, material, etc. Then importing the tool paths. (This happened when importing anything from previous ops, including tool paths, drafting, etching, etc.) hopefully this will help. "" I think we’re onto something here. I had one of the developers look into it with the video and he spotted something for you to try out. If you get the same result, we can use that as a temporary workaround and I can go ahead and finally get this logged appropriately (because we’ll know what is happening and will be able to duplicate it). When you open the second session and load the machine, DON’T do the stock setup. Import the operations first. THEN do the stock setup and see if you get the additional planes. Our money’s on no new planes created. ""

The difference may be a small post mod we did here. Due to some of our machines not liking a O0 program #, we added the following to the header sections. It auto changes 0 to 1, but leaves alone if any other. pheader_custom #Start of file "%", e$ !spaces$ spaces$ = zero IF PROGNO$=0, PROGNO$=1, E$ # RPL added to keep program number from being 0 *progno$,scomm_str, sprogname$, scomm_end, e$ scomm_str, "PROG NAME= ", sprogname$, scomm_end, e$

I've found that if I use the machine properties dialog, then i have to regen to get the program# to change, if I use the right click on operations, then i do not. Hope that helps some.

I tried and had my post output g76 correctly. G00 X2.1685 Z.2154 G76 P010060 Q0 R0. G76 X1.8833 Z-1. P426 Q165 R0. F.07874 G28 U0. V0. When i used the compute feature, it errored out when i had the 2mm in the threads/inch... New Microsoft Office Word Document.docx T.mcam

Thanks for the answers guys, all were correct. I did find where I used it, we use to use Vero software, and that's where I found that. Again... Thanks

That answers that... I hate when fog happens. Next question, is there not a sliding scale for the translucency on the main bar somewhere? It just seems like a waste of time to run to the config settings every time.

It seemed that in previous versions you could select a specific solid (in an assembly) and change both the solid color and its translucent values. For some reason I seem to think that there was some sort of slide scale to adjust this translucency. I'm in "View", "appearance". But when I drop the lower right corner all I get is a shading dialog. Am I just in brain fog or is this possible in 2017 without going through the config every time? Thanks