Mastercam 2025 is Available to All Customers!

[SuperHoneyBadger]

The last post enabler I have installed is 2023
All our 2024 Postability Machine Sims run without a post enabler and IIRR Chris told
2024 machine sim did not require one

Ok, I run MPMaster and IKE posts, so this whole thing shouldn't have any effect on my situation. Sounds like a 3rd party thing that I didn't know about before today, so needn't worry about. All sounded spooky, so I had to ask. Thanks!

[Jeff]

Also what does "External Post Processing Enabler" mean?

Simple explanation is that it uses the post for simulation and greys out the "post settings" tab in Mastercam sim, and greys out the "Post Settings" and "Machine Definition" tabs in Moduleworks Simulation. I'm sure someone smarter than me can give a better explanation.

If it prevents us from using an older version (once updated to 2025) as said on the forums, that's no bueno for me.
Yeah I could contact In-House and bother them for a fix but I don't think I should have to.

[Jeff]

MC2025 mill is off the table for now as well

I'm stubborn and still using 2023 because of things that are still not fixed. As much as I want to use 2025 I see no point as of now when the only thing that has changed (that I wanted changed) was the default setting for Line Endpoint "automatically determine Z depth" is now off by default in 2024 and newer.

Yippee Skippee.
If changes aren't made to 2026, then there's absolutely no point in continuing to pay for maintenance.

[neurosis]

One thing I found kinda strange -

After I installed I ran the migration utility.  First on the part files, then on my shared folder.

When I do this, I always create two folders on my desktop. One for the old files, and one for the migrated files. I then copy the machine, post, tools, etc to their correct locations making sure not to overwrite anything that isn't essential. 

Before I could copy any of the machine definitions over, it had already populated my machine drop down. There were even a couple of machines in there that shouldn't have been there.    There shouldn't have been anything in that dropdown other than the default machine. 

I promptly uninstalled and will probably try to install it again next week. I've never had that happen before.

[Dylan Gondyke]

One thing I found kinda strange -

After I installed I ran the migration utility.  First on the part files, then on my shared folder.

When I do this, I always create two folders on my desktop. One for the old files, and one for the migrated files. I then copy the machine, post, tools, etc to their correct locations making sure not to overwrite anything that isn't essential. 

Before I could copy any of the machine definitions over, it had already populated my machine drop down. There were even a couple of machines in there that shouldn't have been there.    There shouldn't have been anything in that dropdown other than the default machine. 

I promptly uninstalled and will probably try to install it again next week. I've never had that happen before.

This is an interesting one- technically you should migrate all machines/posts/etc, BUT my understanding is depending on the changes or tweaks made to the internals of the machine files year on year, there are cases where the machines might be usable directly without being migrated (but this is never advised). When the stars align, that means you might see your un-migrated machines as options in that dialog box that you can click and immediately add to your Machine dropdown.

Conversely, not seeing a machine in that dialog list despite seeing the machine file physically in the folder is a good sign that something is wrong and it needs to go through a migration.

[neurosis]

Conversely, not seeing a machine in that dialog list despite seeing the machine file physically in the folder is a good sign that something is wrong and it needs to go through a migration.

Yea.  I did some digging and it was a machine definition that I have in an installation from two versions of the software prior.  So a 2023 machine definition. It was a definition that I was using to test some post changes. I thought it was weird that it showed up in the 2025 machine drop down due to how I migrate from version to version. 

I don't know if it's the best way, but it's the way I've gotten used to over the years because of migration issues.  I always separate out the files I want migrated and then *only* migrate those files.  Everything else will be the stock files in the new install. Since I keep 3 versions of the software installed I can always go back and migrate something else if needed.

Do you guys recommend just doing a full migration at this point?  I've been afraid to try it.

[gcode]

Do you guys recommend just doing a full migration at this point?  I've been afraid to try it

We've got about 25 machine defs and posts on a network so everyone is using the same posts.
I have never been successful using migration.
The machine and control def's usually migrate correctly, but the posts never do.
I do them one machine at a time as needed.
One of the few things I like about hypermill is the posts.
The one post I bought in 2013 still works 11 versions later.
It works so well I've forgotten where I keep it.

[Thee Byte]

IN our few attempts with it...it doesn't work...

Haven't nailed it down as we're in a hard press to meet a delivery deadline but we will circle back to it to define it better

You never could make a toolpath   

[Thee Byte]

Is training an option?

💀

[neurosis]

I have never been successful using migration.

The problems I had with migration was pre X9. I don't even remember if it was called the same thing back then. 

I had some issues with config files not working properly, odd issues with machine definitions, tool libraries, operation defaults.  There were also some bugs in the software so I wanted to make sure I didn't unnecessarily introduce a potential issue.

Ever since, I redo my config every new install. Only migrate what I feel is necessary. It may be a bad habit, I'm not sure.

[Jeff]

I think I've only had a migration issue one time. I've been fortunate in that area :knock on wood:

[JParis]

When it comes to migration I still do it in a very specific way...

I create a folder on my desktop

Update

Inside of the folder I have a folder structure like that in the public shared folder, in this years case

2024

I copy that folder structure and rename to

2025

I then copy everything I want to update from my current version to my update version   2024 >> 2025

I use the advanced migration

My source folder is the 2024 folder
My destination folder is the 2025 folder

I then update and copy into the appropriate folders.

Overkill? Maybe

I am usually running in about 20 minutes though after installation.

I have not changed from this process since around 2010....

JM2C YMMV

[neurosis]

Overkill? Maybe

That is almost exactly the way I do it. It wouldn't surprise me if I picked this up from one of you guys over the years.

[Here's Johnny!]

Also what does "External Post Processing Enabler" mean?

Likely your dealer who purchased the Machsim/ Post and license from Postability?

[Thee Byte]

That is almost exactly the way I do it. It wouldn't surprise me if I picked this up from one of you guys over the years.

Probably, the group think around here is real, I mostly follow what gcode and Ron say (unless they haven't had their coffee yet)