New Job Setup Interface in Mastercam 2023?

[gcode]

People are complaining on the main Mastercam forum, they don't understand how to use it..

It needs a simple/expert switch

[mega]

It needs a simple/expert switch

I will use the simple one, thanks in advance   

[Jeff]

People are complaining on the main Mastercam forum, they don't understand how to use it..

Because as with anything they release, it's just....here ya go, enjoy. And we might get a 3 minute video that shows us some of the basics.
What they need to do is more videos that go in-depth about their new changes instead of us having to rely on other sources to post a video 6 months after release once they get the thing figured out.
Sure we have resellers to help us, but if we called our reseller every time we had a question they'd stop taking our calls.

[Jeff]

This video explains some of the new features
When you first open the Machine Group page in 2023 it's a wtf moment
but it's not that bad once you figure it out.
There quite a bit of it that I like but it will throw you for a loop the first time a
machine sim machine flies in and lands in the middle of the screen.. That can be turned off BTW

I just watched it. I like how he glosses over the Material Selection portion and ignores the fact that the Material Selection is completely borked in this release. It forgets the material you select at random. The draggable box is too small, and you can only drag it open so far (Why??? No god damn clue).
The material list is NOT sortable at all, it's in no particular order, making the selection of my user created materials (I never use their default materials) a major pain in the ass and extremely time consuming. Not to mention that you will probably have to select your material more than once or twice before you even post the damn toolpath.

THEN,
if you're lucky enough to create another machine group and NOT have it freeze up on you so you have to End Task, the material you selected in the previous group vanishes, it doesn't remember what you had, unlike in 2022 where it remembered every material you have used in that entire file. AND it was easily sortable. If you wanted to select G2-Cast Iron for your material, you just hit G and it would navigate to the ones that started with a G.

Oh and if you have more than 1 machine posting to the same folder, you're S.O.L., you have to navigate to that folder again after switching machines every time.

Now, after you've gotten that clusterfuck all set up, and you want to simulate the toolpaths you've just ran guess what... you have to do it all over again in the simulator options.
I've never been this vocal about any release and I've been a steady user for almost every version since V8.
The entire machine group setup needs to be removed until everything works like it was intended. They added it half complete knowing this,just to say that there is something new in this release.
When you have to repeat tasks because the new feature doesn't handle them like they are supposed to, it shouldn't be added.

Do I like the release overall? Yes. But they really need to remove the MGS until it's ready and working.

/rant off.

[mwearne]

I'm of the mind set that this is broken, specifically stock setup on custom planes, never mind the MGS not being hooked up to the rest of the software.
If you do use custom planes, watch the few mins at 12:00 in this vid...

[neurosis]

I'm of the mind set that this is broken

This is probably the best video I've seen so far explaining the glitches in the new setup.

[Jeff]

I'm of the mind set that this is broken, specifically stock setup on custom planes, never mind the MGS not being hooked up to the rest of the software.
If you do use custom planes, watch the few mins at 12:00 in this vid...

I like the fact that he's optimistic when he says "I'm assuming this is something that will get fixed" when his machine came in upside down. That's been happening to me for years and they haven't fixed it yet. Why start now?

[gcode]

when his machine came in upside down. That's been happening to me for years and they haven't fixed it yet. Why start now?

correct me if I'm wrong, but hasn't it only been a release or two since machine sim started supporting
WCS??

[Jeff]

correct me if I'm wrong, but hasn't it only been a release or two since machine sim started supporting
WCS??

I can't really answer that since I've only really started using the Mach Sim about 5 years ago when we got our Koma 3+2 rotary.

And IMO you still have to do some finaggelin to get it to work with user created WCS. Sometimes you have to tick the "Transform into WCS" box. But that's probably my inept experience with it.

[Here's Johnny!]

I can only assume with Sandvik owning them now and with Vericut under the same ownership...they are heading towards a "complete solution" for the users...Kinematic aware post processors and possible full verification/ simulation.

[Here's Johnny!]

I'd think that is a safe assumption....Back in my Beta days, one of the stated future goals, was to have "gcode verification" (Tom would be very busy with everyone having to email him their programs for checking  )
But the whole verification "thing" has been a bit of a clusterfuk for a few years - with both verifications ("normal" and machine).
Machine far from working correct out the box - I never bothered with it at all (just vert 3 and 4axis work).
But IMHO, they should have concentrated and stuck with the one - probably nowadays machine for enhanced holder clearance etc.
But that would mean dropping the "standard" which also means resource and QA check etc to ensure it would be 100% working out the box for Joe Idiot (me).
Curve ball - but if there was going to be a port into vericut - why continue with the machsim anyway....especially as that isn't gcode....?

To get Machsim to work as well as it can you need to BUY a post processor from In-house or Postability and then BUY the full Machsim module license as well.

[JParis]

I'd think that is a safe assumption....

Is it though?

I mean Machine & Control defs, even after all these years are really mostly irrlevent..let's see..Mastercam X was release in July/Aug 2005....they were "supposed" to lead to it then...

17 years and counting......

[gcode]

Just like machine and control defs when they were introduced -

when I first saw Machine and Control defs I though OMG... this is going to be awesome !!!
15 years later, it's still mostly eye candy doing nothing
Of course in my case it's because most of my posts are old  home grown mpmaster based posts that limited
support for machine/control defs

I agree that the ultimate goal is probably launching a full gcode checking Vericut session straight out
of Mastercam.
or better yet,
a full time live associative link between VC and MC (for a not a not so nominal fee of course)

[TSmcam]

I don't know. The thought of one app, that does toolpathing, simulation/verification, post processing and then g-code verificatiion.... All sounds good. We actually have that now with TopSolid, as TS now has its own internal g-code simulation/verification using the Eureka engine. I've looked at it, and it seems pretty good.

However, I much prefer to post that code, then either export the whole setup (via the TS to Vericut module) to Vericut, and run it standalone.

[mega]

I don't know. The thought of one app, that does toolpathing, simulation/verification, post processing and then g-code verificatiion.... All sounds good. We actually have that now with TopSolid, as TS now has its own internal g-code simulation/verification using the Eureka engine. I've looked at it, and it seems pretty good.

However, I much prefer to post that code, then either export the whole setup (via the TS to Vericut module) to Vericut, and run it standalone.

I feel like using a collection of softwares is safer,that way if there is a mistake in one, it will likely be caught by the other, something about eggs and baskets,