Guide
Alphacam versions and add-in compatibility: what changed since 2019 R1?
Differences between Alphacam releases (2019 R1 … current) that affect add-in and macro compatibility: 64-bit and VBA 7, LICOMDIR/Startup structure, API backward compatibility, Windows 10/11 and .NET dependency, licensing. The add-in developer's version policy.
Published: 6 min read
Alphacam releases a new version every year; for the user the question is as much "will my add-ins still work" as "what is new". GMacros products state "Alphacam 2019 R1 and later"; this article explains why that threshold, what changed in between, and what to check before upgrading. It does not list features — those are in Hexagon's release notes; only differences that affect compatibility are here. Version-specific details should be verified against your installation.
Version naming
Older naming was year + half: 2019 R1, 2019 R2 (two releases a year). Later years use year + point: 2020.0 / 2020.1, 2021.0 / 2021.1 …; the first is the main release, the second an interim one. Alphacam shows the version under Help › About; in a support request the whole line (e.g. "2023.1 build …") should be given. Several versions can be installed side by side on one computer; each uses its own LICOMDIR.
Changes that affect add-ins
| Change | Effect | What to do |
|---|---|---|
| 64-bit | Recent releases are 64-bit only; VBA 7 runs. Declare lines (Windows API) written for 32-bit do not compile | Add-ins must use PtrSafe and LongPtr; GMacros is written that way |
| VBA version | VBA 6 → VBA 7; same object model, language backward compatible with minor differences | Pure Alphacam API code is unaffected |
| `LICOMDIR` / `Startup` location | Each version has its own folder; the add-in stays in the old version's folder | Run the installer again after upgrading |
| Windows version | Windows 7/8 support ended; 10/11 required. Windows 11 does not ship older .NET COM components (.NET 3.5) | An add-in must not depend on .NET — GMacros license cryptography uses Windows CNG (bcrypt) for that reason |
| Licensing / Hexagon CLS | Alphacam's own licensing changed (hardware key → software/network license) | Does not affect add-ins; if Alphacam opens, the add-in runs |
| Ribbon API | The add-in's tab/button definition may differ slightly between releases | The add-in is tested on every main release; if the tab is missing: Alphacam add-in problems: tab missing, macro failing, license errors |
Changes that do not affect add-ins
- UI and theme (dark theme, icon set): macros run the same.
- Nesting, simulation, toolpath improvements: the macro produces the drawing, Alphacam machines it; improvements apply to macro output too.
- Post-processor changes: the add-in does not touch the post (What is an Alphacam post-processor? Producing NC code for your machine).
- File format (.ard version): the add-in does not save files; it writes into the open document.
Why the 2019 R1 threshold?
2019 R1 is the oldest release GMacros can test, and from that release the API members the add-ins use (geometry creation, layers, selection, ribbon definition) are stable. Older releases bring the 32-bit and VBA 6 differences; separate builds and tests would be needed — low demand, high cost. The threshold is "and later": 2020, 2021, 2022, 2023, 2024, 2025 and beyond are supported; when a new main release appears, the add-in is tested on it and updated if necessary, and the update is downloaded from the panel.
Checklist before upgrading
- Back up the current LICOMDIR: posts, Auto Style file, tool library, Startup add-ins.
- Install the new version side by side; do not remove the old one. Two versions for a week.
- Test the post on the new version (scrap board) — posts can change with the release.
- Carry the Auto Style file to the new version and verify with the test drawing (Alphacam Auto Style setup: automatic machining by layer name).
- Install add-ins into the new version's Startup: for GMacros run the installer again; the license is on the same computer, so no key is asked.
- Run one day of production on the new version; if all is well, remove the old one.
GMacros version policy
Whenever a new Alphacam main release appears, the add-ins are tested on it; if an incompatibility shows, an update is published and downloaded free from the panel during the license period. Add-in version and Alphacam version are independent: add-in "1.0.x" is the same file on Alphacam 2019–2025. If you hit a problem on a new release, open a request in the panel with the Alphacam version line + add-in version + error text. How the add-in loads: What is an Alphacam add-in, how is it installed and how does it work?
Frequently asked
Does GMacros run on Alphacam 2018 or 2017?
Not tested and not supported. It definitely does not run on a 32-bit installation; on 64-bit 2018 it may load but is not guaranteed. Upgrading is recommended.
Do I need a new license when moving to a new Alphacam version?
No. The GMacros license is bound to the computer, not to the Alphacam version. Just run the installer again for the new version.
Can I use the add-in in two Alphacam versions at once?
Yes; it is installed into both versions' Startup folders on the same computer and one license suffices (the license is per computer).
Related products
Tools that do the work described here with one click inside Alphacam: the GMacros add-in and macro packages. Purchasing and licensing are explained on How it works.
Written by the GMacros team. Alphacam is a registered trademark of Hexagon AB; this guide is independent.