2023 Update 2

[crazy^millman]

It is out and I cannot think of any version having 2 updates this fast. Does it mean things are heading in a different direction with addressing issues and defects?

Thoughts?

[JParis]

If only Ron.
I think this is more about all the low hanging fruit that were left thru the Beta cycle...

Long been one of my issues....too much stuff gets left behind becasue of the "created" deadline to get a product released.

[gcode]

I think the userbase's participation in the beta cycle is way less than it used to be
I know I have not been able to bug hunt like I used to.
A lot of the stuff that was fixed in Update 1 and now 2 should have been addressed in beta but didn't
get reported
Once X23 went RTM the reports started coming in.

I had a hard time installing Update 2
My system was X23 with the Update 1 patch applied and it would not run Update2
I had to uninstall then reinstall with the full X23 UPdate1 exe file to get Update 2 to run

[crazy^millman]

Yeah don't have time to do the non paying testing anymore like I use to. Running a business, dealing with older family and just life in General has changed my focus on giving my time to beta testing like I use to. Still have to find time in get my programming responsibilities done also. Even though some days I put 12 hours in I am home so it makes it more bearable.  

[gcode]

In my case it's the level of work I've been doing
Explaining that I've hammered a quarter million $$ submarine part cause I found a bug
in X23 would be an awkward conversation 

[Jeff]

Does it mean things are heading in a different direction with addressing issues and defects?

Unfortunately, no.
There's still a major crash issue preventing me from using 2023 and they are unable to replicate it which tells me that I won't be using 2023 at all, so there's that money wasted.
Along with a whole slew of other issues related to the new Machine Group Setup fiasco.

[gcode]

There's still a major crash issue preventing me from using 2023

what are the details of this crash.

[CNCAppsJames]

I stopped Beta Testing because I saw no value in it.

I mean one can only make so many reports and requests over TWO decades with only a few fixes before it becomes an exercise in futility. I'm involved with other more fruitful endeavors now. And the other things is I need CAMplete to get code because I only have a few Mastercam posts (VMC's and HMC's) and the bulk of my work these days is in the 5-Axis realm so it REALLY is of no benefit to me now.

I have started sending in the crash reports again if I get a repeatable one. I figure if I don't at the very least submit those, then I have absolutely no right to complain about the issues.

[CNCAppsJames]

... the new Machine Group Setup fiasco.

Yeah... NOT a fan of that at all. COMPLETELY unnecessary IMHO. AT LEAST give me the option to tirn it off/disregard it. They must be wanting to #MeToo this "Digital Twin" stuff.

How about we make a healthy CAM software package that routinely hits the low hanging fruit before it chases the eye candy bullshit? Is that too much to ask?

[TSmcam]

Is that too much to ask?

Yes 

[Jeff]

what are the details of this crash.

Creating a new machine group completely locks up Mastercam, forcing me to End Task. So it's not really a crash, but a freeze.

[gcode]

Creating a new machine group completely locks up Mastercam, forcing me to End Task. So it's not really a crash, but a freeze.

I think this is windows and x23 not playing well together
Have you tried right clicking the x23 icon and choosing "run as Admin"
also make your default machine
"C:\Users\Public\Documents\Shared Mastercam 2023\CNC_MACHINES\MILL DEFAULT.MCAM-MMD"

What does the Mastercam log say when this happens?

[Jeff]

Ok did that,
It says
App=Mastercam Entry=EditGroupPropertiesDlg    28996
Entering Inline function"App=Mastercam Entry=OnViewIsometric   8376
Exiting Inline function"App=MastercamEntry=OnViewIsometric     8376
Execution Time = 234 ms


This is what I did in order,
Started in Run as Admin
Changed the default machine
Selected New
Cleared Log
Right clicked in toolpath manager to create new machine group.

It waited a few seconds before the execution time popped up




Now comes the interesting part,
If I create a new machine group from the ribbon dropdown, it works regardless of which machine is default, and/or running as admin.
The event log is completely different:

App=MastercamEntry-MTCommand    31060
Exiting App=MastercamEntry=MTCommand    31060
Execution Time = 1922 ms    31060

[Dylan Gondyke]

Jeff, did you get an R# for your issue and did you submit video/files/log file for this? I want to check on where this is at.

[gcode]

This is what I got in the Event log when I added a new Machine Group
which executed with no problems

Information   9/9/2022   8:28:52      Mastercam Event log cleared.      23808
Information   9/9/2022   8:28:58   T   App= Mastercam Entry= EditGroupPropertiesDlg      27408
Information   9/9/2022   8:28:58   T   Entering Inline function: App= Mastercam Entry= OnViewIsometric      27408
Information   9/9/2022   8:28:59   T   Exiting Inline function: App= Mastercam Entry= OnViewIsometric      27408
Information   9/9/2022   8:28:59   T   Execution Time = 375 ms      27408
Information   9/9/2022   8:29:50   T   UBVS started https://svn.moduleworks.com/ModuleWorks/branches/X23_IOF/dev@1592395      date:2022/8/11 Count: 2      27408
Information   9/9/2022   8:30:01   T   Exiting App= Mastercam Entry= EditGroupPropertiesDlg      27408
Information   9/9/2022   8:30:01   T   Execution Time = 63156 ms      27408

It looks like my machine is going out into the net for the machine sim file or permission to run machine sim ?
I loaded this line into a web browser and got a Moduleworks website which asked me for a
Username and password

I've been trying to figure out how to assign my machine sim files to my machine def and posts but haven't got there yet