Mastercam EverPath Webinar

[CNCAppsJames]

Ok... I'm liking it so far.

This interface looks like change for enhanced productivity unlike many changes that have been made in the past just for change's sake.

Have they fixed the File list order yet or does it still look like Kamala Harris sounds?

#AskingForAFriend

[CNCAppsJames]

From the color answer we can ascertain age range. 

#OnceYouGoBlackYouNeverGoBack

 

[Zoffen]

Ok... I'm liking it so far.

They still have plenty of time to mess it up....     

[neurosis]

I like how he lists the shortcomings of the old tool paths (wrap-around, drop-off, etc) and talks about how this  doesn't have those shortcomings. 

Does that mean they've known those were shortcomings this whole time? 

[Zoffen]

Does that mean they've known those were shortcomings this whole time? 

They have been gaslighting us for years!

[Dylan Gondyke]

A consequence of the technology behind them. 3D HST fundamentally works off of a "sheet drape" approach, which provides pretty simple 3 axis motion but has the consequences of things like the waterfall effect off surface edges as well as immense challenges with handling undercuts. This approach holds up well with a workflow where the user does something like select the entire model every path to get a full "sheet drape" with no holes, and then uses containment boundaries or other restrictions to cut the path back.

EverPath is contact-point based. It only cuts the green, and it really aggressively tries to cut all green, if you will. It will reward workflows where the user selects only what they actually want to cut.

[CNCAppsJames]

@Dylan Gondyke I'm going to bring up a promise made as to why X and subsequent generations were created; 
"this new version makes updates easier". 

This was in response to the Mastercam Executable becoming obese and inefficient. The exact quote from BITD was; "The executable now is just going to be much smaller and more efficient. All functions will become C-Hooks in a sense and all the executable will do is link to the function(s). When there is a problem with the function, we will fix the function and release the function update. 

Now, that's not exactly what Dave said, but he intimated that now we can just update the function as the function will reside in the cloud. 

#PepperidgeFarmsRemembers

Anyone care to comment? 

 

[Newbeeee™]

Does that mean they've known those were shortcomings this whole time? 

STFU and pay yer maintenance!!!!

[CNCAppsJames]

Don't get me wrong @Dylan Gondyke , I like the new stuff... and you can quote me on that, AND I fully intend to migrate to it... as soon as the SDK for 2027 is set in stone. I use CAMplete for posting and collision checking and I need the plug-in before I migrate to it. 

2027 may be what stops the hemorrhaging of MC's market share. Some of the old guy's you'll never satisfy and some of the kids know everything... they are the Heidenhain and Siemens are the only true 5-Axis control crowd. No matter what you can;t change their mind... they know everything. 

JM2CFWIW

 

[Zoffen]

2027 may be what stops the hemorrhaging of MC's market share.

Yet again... They still have plenty of time to mess it up....     

[Dylan Gondyke]

That was WAY before my time, but I can comment to some of the challenges we faced that drove development change for EverPath.

Our traditional anchor has been the requirement (from a tangled web of many reasons) that we not release UI changes in between releases. That means I can never hand the user a new feature or field or checkbox once a version is in the wild- I can only improve capability in the background. These are things that got in the way of that dream back then almost immediately.

As Dave touched upon quite a bit in that webinar, we are not beholden to those shackles. We are truly aiming for a continuous release model with this to shorten that timeframe between "user hands us idea" or "vendor hands us new tool shape" to "EverPath incorporates new thing" to a very tight cycle. Even down to the help- web-hosted so we can deploy continuous updates, add video links, etc day-to-day. (Yes there is a backup offline help)

I'm an impatient guy and I'm not interested in waiting a year to deploy new features, and neither is the team behind this tech, so I hope to put some action behind these words in the latter half of this year as we grow the product.

[Zoffen]

Where is my MP.net?

[Dylan Gondyke]

Yet again... They still have plenty of time to mess it up....     

Recreating, from scratch, every finishing toolpath pattern and linking move ever offered, in a new UI, while making them all multiaxis capable...I am under no illusions that I won't see some interesting results pictures in forum posts in the early days...

[CNCAppsJames]

That was WAY before my time.

Way before most active programmers' time.

Just call me O.A.F. Old As F***

 

[Here's Johnny!]

Yet again... They still have plenty of time to mess it up....

Spoken like a MC2026 levels fan!!!!