We just started testing the first build of V7, which was going to be a major change to Carbide Motion’s user interface. But once we started on the internal changes we needed, it became clear that we should publish a version with the internal/functional changes that keeps the familiar UI for users who don’t like big changes.
We hope to share the first public V7 release in the next few weeks.
In the meantime, we moved build 667 of Motion to the main download page at Carbide Motion Downloads | Carbide 3D and marked all other releases as “retired” in BugSplat (so we won’t get notifications on those builds). If you plan to stay up to date on future Carbide Motion releases, we recommend trying 667 and submitting any crashes you see so we can incorporate fixes into V7.
For what it’s worth, we haven’t seen many crash reports for the latest Motion releases, other than a rare crash in some third-party code that’s been in Motion for many years. We’re not sure what’s causing that, because it doesn’t make any sense when we look at the crash reports. It’s likely an interaction with something on a few specific PCs. We already removed that third-party code from V7, so it won’t be an issue in the future.
