MC 2026R2

gcode · February 06, 2026, 07:33 AM

Quote from: Jeff on February 06, 2026, 02:54 AMExcept for this time it was a breeze.

Because the beta testers got beat like rented mules ironing out the problems

SuperHoneyBadger · February 10, 2026, 05:30 AM

GPU verify is fast as fuck boiii. Like a second or two for a 3 axis program, ~450 holes (spotted, drilled, tapped), 2D contours.

champshire · February 10, 2026, 07:51 AM

Funny thing, I just did back to back testing using the CPU/GPU (difference being with stop on collision turned on/off) and one way shows a collision with my holder, and the other way does not. What do you trust?

Also, when I try and import ops from another file Mastercam repeatedly crashes. Import ops has been screwy since at least x7. I really really wish they would fix a basic feature such as that. Yes I have reported it multiple times, to Dylan even. It still exists.

Here's Johnny! · February 10, 2026, 08:04 AM

I think the GPU verify does not support collision checking?

champshire · February 10, 2026, 08:05 AM

Oddly enough when I use the GPU, that's when it reports the collision.

Here's Johnny! · February 17, 2026, 05:59 AM

Lots of complaints on MC2026 R2 on their main forum.

gcode · February 17, 2026, 07:41 AM

Brutal

I've used 2026 R2 for a lot of different parts without any real trouble.
The "glow" Mike M is complaining about is a new ( and worthless IMO) option.
I turned it off immediately and never thought about it again.
I love the Planes and Level grouping and never noticed all the complaints
about the new GPU verify