9 minutes ago, sharles said:

it takes me a little longer to figure it all out, but once I send it to the floor, I have a high degree of confidence in my programs and my tool-build sheets!

I always hear programmers talk about how they need to program faster...to an extent, I get it.

The reality is though, if the programmer takes a little more upfront to get everything done and can be confident in what is being sent out, to the point that the vast majority of questions are already answered, that leads to faster setup times. Frankly, I'd rather see a little longer program time and start saving on the setup times, especially in shops that do many setups per week...that will translate into real dollars very quickly.

Update your video driver...it's a different software standard for videocard drivers

and yes, a new requirement with 2020

9 minutes ago, #Rekd™ said:

I still have X6 installed on my desktop, Windows 7

V6   

Nope, you're calculating that one in...

Unless someone is going to teach this Old Bear a new trick

14 hours ago, mkd said:

ahem, Mitsubishi

True enough, you know what I was saying tho' 

Mazak

17 hours ago, Leon82 said:

Are these fanuc or just the okuma controls?

and if the parameters are wrong, what, does it show you a broken tool laying on the part?

:headscratch:

19 minutes ago, jlw™ said:

I flip back and forth with G64 and G61.1 via misc int.  The dynamic paths really love G64 but leave enough stock!

On the latest Smooth controls, holding size, machining corners ever, recently noticed an issue at the overlap of a start/stop in G64.....feeds were only in the 45IPM range

Turned on G61.1....issues all went away....seems these very latest controls are very picky

Go into the settings of the path and click the perpendicular entry box and repost....

9 hours ago, M4573RMZD said:

Just for everyone's input the Machine I'm using is a Mazak VC-500A /5X  

We have a VC300A-5X....runs fine with the dynamic paths, I do send out programs with G61.1....I have found the new Smooth controls seem s to prefer it that way.

12 minutes ago, Matthew Hajicek™ - Conventus said:

Unless there's a misc integer setting that controls how the offsets are posted?

Possible, I "assumed" they've at least talked about it, so hopefully on that, they're on the same page

It doesn't sound like you're both using the same posts...

I suggest getting a copy of his directly from him

6 minutes ago, Thad said:

Thanks for the dynamic option, Old Bear! 

Happy to be of assistance

Click on the Geometry from the operation group.

right click on the chain,Click start point...there's a dynamic option in there where you can set the start point

Caveat, if you use Solid chains, this is not available

Unless you're willing to pay for X+ into Mastercam 2020, might be time to explore other options at this point instead of fixing it

8 minutes ago, Kolson1989 said:

Like I said, was just hoping for a quick parameter change that would produce the same code that Mastercam simulated.  

 

What Mastercam simulates exists before the posted code....so it won't show things that are manipulated in the post processor

Old school, I use what I have forever

I use slice as I have no need for the lower profile...

Easiest way, use perpendicular entry....

I also built a check into my post that errors out at the position of the move so I can trace the path and change what needs changing

38 minutes ago, Leon82 said:

On a net hasp does it grab a mill licence if you are using a milling path in lathe?

Depends...

It might if switches are not set but it can be controlled using shortcuts and switches

"C:\Program Files\Mcam2019\Mastercam.exe" /L1 /M3 /noW /X5 /N /noT

The lathe/mill icon I use tells it what to/not to grab

I think they mean

https://users.mastercam.com/Default.aspx?siteId=13&ReturnUrl=%2FForum11.aspx

No Mastercam file that shows how your part is set up?

I thought it was generally accepted as good form to post a Mastercam file.

In your config, the is a setting

Toolpaths branch but there is nothing specific to stock models, toolpath crunching

In reality, for what you're doing, 64 gigs should be minimum

I have not tried an axis substitution or rolldie but that is what I would if I had to use something else

If you have access to the 5 axis paths, Swarf will work