Good news: The new V2 beta fixed the Z-offset issue.
Regarding the G2/3 codes, I tried to run a Mach3 style multi-tool output that I’d removed the G53 from, and it took all of the linear stuff in the first tool handily, and did the tool change correctly. Then when it got to the second tool, it started into the work just fine until it saw the first G2, and stopped there because it interpreted the lack of an F parameter as F=0, and just stopped in place, rather than keeping with the F value from the preceding G1… at least that’s my uneducated read on it…
The error Carbide shows is “GRBL Error: Invalid gcode ID:35” which it shows and then stops motion, but the spindle stays running and the project pauses.
HSMxpress and Mach3 apparently take the approach that “this is the variable until we say otherwise” when it comes to some of the variables, while from MeshCam it looks like on every switch from G0 to G1 it wants the feed-rate stated, and I see some places where it lists the feed rate before movements, like this:
Is that observation accurate, that it needs to declare F for each G1/G2/G3 block-start regardless?
I may be able to get the Post to put that in, but if Carbide is going to do more with G2/G3 in the future that should probably be part of the overall game-plan anyway, right?
note edited to include error that Carbide throws
Carbide Motion Log during attempt
further edited to include HSMxpress posted Mach3 program file, and Carbide Motion Log during operation