Upgrading from 3.1.175 to 3.2

These pages are the long form of the 3.1.175 → 3.2 line — the 3.2.7 entry and the 3.2.24 incremental drop. They exist because 3.2 is not an increment on the last release most callers hold — it is the accumulation of everything that landed after the 3.1.175 package set, delivered in one step.

Read them in order the first time. The two sections that decide whether an upgrade is a recompile or an afternoon are Breaking changes and Results that change on upgrade; everything after them is new capability you can adopt when you need it.

Important

Read the Adoption status note on the release-note page before planning around this. The short version: 3.2 is published for review, verification is still in progress across most areas, NC optimization is not finished on this line, and SoftNc canned-cycle indexing with rotary A/B/C words is not finished — work that depends on either should stay on 3.1, serviced as 3.1.175.<patch>, or run with SoftNc off for the rotary-cycle case.

Pages

Ordered the way to read them: what the package numbers mean, then the two sections that decide whether the upgrade is a recompile or an afternoon, then the new capability, adopted when needed.

• The package line — Why a 3.2 build number starts low, which ten packages moved together, and what that means for a mixed reference set
• Breaking changes — The eight groups that stop a build, in the order they bite — registration, messages, the session surface, the play verbs, renames with no shim, removals, signature changes, changed defaults
• Results that change on upgrade — What a simulation produces differently afterwards — usually because 3.1.175 was wrong — and why a byte-for-byte comparison will differ
• Brand NC language coverage — Where most of the release went: Siemens, Heidenhain, Fanuc and ISO common, and the cross-brand work behind them
• NC optimization and writeback — The optimization leg as it stands on this line — published for review, not for production
• Milling physics, training and measured data — Physics in the native kernel, and what changed in training and in the handling of measured signals
• Cutter-location (CL) playback and CL-to-NC — Replaying an NX CLSF / APT-source toolpath directly, and writing one out as NC
• Session, project and command model — Runner suits, the three the project holds, and the command model a script and the app share
• Geometry, rendering and native stability — Disposal crashes that no longer take the process down, and the geometry and rendering changes behind them
• Performance and footprint — Every figure with its conditions stated, including the places the release spent time on purpose to buy correctness
• Packaging, resources and hosting — The .default ownership marker, resource seeding, and what a host has to change
• New diagnostics you may now see — The searchable ids for failure modes that used to be silent