Mastercam 2026 is Available to All Customers!

[neurosis]

Mastercam 2026 is Available to All Customers!

[JParis]

Yup, downloaded it this morning, going through and getting everything updated...

I'll roll it out to the rest of the user base, middle of next week

[megatronprime]

I have had it installed, I guess there is the new official version?

Usually the customers only upgrade 6 months in, once the bugs are sorted out, if there are any.

[Jeff]

I have had it installed, I guess there is the new official version?

Note: This is the same build as Mastercam 2026 PC1. You do not need to uninstall the PC build. It is the same as the RTM version. 

[gcode]

I don't know if they are the same or not, but they have different build numbers

Mastercam 2026 Production Candidate 1
Version information
Mastercam version number 28.0.7534.0.

Mastercam 2026

You must have a maintenance expiration date of June 30, 2025 or later to run this product. The version number of Mastercam.exe is 27.0.6723.0.

[megatronprime]

I don't know but I'm using the PC1 sdk anyway

[gcode]

once the bugs are sorted out, if there are any.

megatonprime make a funny!!! 

[Jeff]

once the bugs are sorted out, if there are any

You must be new here.

[gcode]

During the 2024 and 2025 beta cycles I was super busy and didn't do much beta testing
2025 was and remains a train wreck... I've got 3 programmers on my staff now and all three have stayed at 2024

I felt bad about not participating in 2025 beta and resolved to do better during the 2026 cycle.
I was still super busy but made the time to use 2026 betas when I could and file reports when I found a problem.

I made numerous reports and got 3 R numbers which I guess means they are considered a regression?

I found a serious issue in the ModuleWorks interface that will cause all kinds of trouble for me but didn't
get a number for that once because the developers said it was "too late"

So.. 2026 is released and not one of my reports got fixed... and I'm wondering why I even bothered.

 

[JParis]

So.. 2026 is released and not one of my reports got fixed... and I'm wondering why I even bothered.

I have come to realize that unless something is important to them and it's caught early OR if it's a show stopper caught late...they will just roll with what they have....

Look at what, 7 updates to 2025....I am still on Update 3....if I was a one man show, maybe I'd keep up but with over 15 workstations to keep up with, it is too much.

Not all users can simply install updates for themselves, I am guessing these days, many need an IT department to do so...

The other thing they NEED to do consistently is make the updates all encompassing....if you install update 4, you also get 1,2 & 3. All these updates have become a nightmare to manage.

Beta testing for me has been difficult...when I was doing my own work for the floor, I could do it fairly easily. Now that my time is between managing, meetings, 3D printing, I pass off nearly everything I begin..just happened this week, job I was working I got 6 OP's programmed, still needed to do the fixtures. I passed it off and they were looking for it the next day. One of my guys was working on getting the fixtures done.

[Dylan Gondyke]

I made numerous repots and got 3 R numbers which I guess means they are considered a regression?

I found a serious issue in the ModuleWorks interface that will cause all kinds of trouble for me but didn't
get a number for that once because the developers said it was "too late"

R numbers are "Request" numbers and everything that comes in gets a Request. It may spawn a defect or enhancement after investigation, which is where development activity occurs. The R# is usually what we hand out for reference.

What was the moduleworks issue? It should have received an R# no matter where we are in the release cycle. You've got my email...

[Dylan Gondyke]

Look at what, 7 updates to 2025....I am still on Update 3....if I was a one man show, maybe I'd keep up but with over 15 workstations to keep up with, it is too much.

The number of updates has been purposely ticking up as a firm response to, how can we deploy fixes and enhancements faster to someone whose workflow depends on small items? How can we get CAD translators out closer to the release cadence of other packages so there isn't a big lag between Solidworks/Catia/etc launch, and the compatibility with their new files?

The other thing they NEED to do consistently is make the updates all encompassing....if you install update 4, you also get 1,2 & 3. All these updates have become a nightmare to manage.

Definitely on our radar and much more important now that we have the goal of doubling/tripling the release cadence within a year.

[gcode]

Dylan

It's pretty well documented on this thread on the Mastercam fourm

https://my.mastercam.com/forums/topic/2026-pb3-5x-linking/#post-89197

This is R41359
https://my.mastercam.com/forums/topic/mc2026-machine-output-folder/

and R-41589

https://my.mastercam.com/forums/topic/absolute-vrs-incremental/

[Jeff]

I'm wondering why I even bothered.

I feel your frustration.
I wonder if sometimes their hands are tied because of the higher ups.

[megatronprime]

During the 2024 and 2025 beta cycles I was super busy and didn't do much beta testing
2025 was and remains a train wreck... I've got 3 programmers on my staff now and all three have stayed at 2024

I felt bad about not participating in 2025 beta and resolved to do better during the 2026 cycle.
I was still super busy but made the time to use 2026 betas when I could and file reports when I found a problem.

I made numerous reports and got 3 R numbers which I guess means they are considered a regression?

I found a serious issue in the ModuleWorks interface that will cause all kinds of trouble for me but didn't
get a number for that once because the developers said it was "too late"

So.. 2026 is released and not one of my reports got fixed... and I'm wondering why I even bothered.

 

No R is request all issues are categorized under R, at some point they may be classified as D for defect but that happens internally.