All of the user interface code on the left part of the screen is now. We removed the Qt/QML system and went to native code that should be more stable and easier to work with going forward.
There is a breaking change to the file format so 500 should load files from the 400 series of releases but files from 500 may not load correctly in the 400’s
Build 500 should install to a different directory in Windows so it should not overwrite any prior 300/400 releases.
Missing Features:
“Send to Carbide Motion” not implemented yet
This is a very early build so don’t do any projects in this build that you can’t afford to lose if the file gets corrupted.
If you do choose to check it out, we’re interested in seeing if there are any regressions from prior builds. Once we confirm that everything is working, we’ll move the current build to “Released” and work on new features.
We’re trying very hard to get this back to feature parity with build 474 so we can move it to the beta download page and recommend that everyone try it.
I think we’re pretty close. There are still bugs but they don’t appear to be new bugs so we’re getting there.
(Once we get this to beta, we’ve got some fun changes to Carbide Motion to begin working on)
Love the revamp of the “Toolpath” page… especially being able to drag and drop to “Groups”, much needed update. Also, right-clicking is much better on the Mac platform. I could never reliably right-click using trackpad in previous versions and now it is flawless.
Another item that works now, may have been a bug before, is the “Align Vectors” tool. In previous versions, if you selected a vector and used the “Align” tool but did not click “done” and inadvertently clicked another vector… it would bug out and not allow you to continue without closing the file and reopening. Now it works like it should! Nice job!
I’ve noticed the pocketing operations are behaving differently in V5. When milling a pocket, after each depth pass, it does a full retract (surface+retract height) before moving to center and plunging again to next depth.
@robgrz What’s the process for reporting “bugs” in these software releases? Hardly anybody posts to your release threads, so I always wonder if there is another channel that people are taking to get the info to you?