I bought World Machine Professional recently. No complaints about the software or the price; this is feedback on one part of the experience, license activation management.
The two-machine activation limit caught me out after install. My setup:
- A Windows GPU workstation, where World Machine does the heavy lifting.
- A Linux development laptop, my normal working environment.
- A MacBook for when I’m mobile.
I’m the only person using all three, and I never need World Machine running on two at once. With two activations, the workstation takes one permanently and I choose between the laptop and the MacBook for the other. Now that World Machine ships on Windows, Linux and macOS, a
one-person three-platform setup follows directly from that platform support.
A Professional license should not become a site license, and I’m not asking for one several people can use at the same time. But users and installations are separate counts. Allowing 3 to 5 registered machines per Professional license, with the single-user restriction unchanged,
matches how one person works across platforms. Enforcing one concurrent session would be stricter still, at the cost of more server infrastructure and broken offline use.
The limit matters less than being able to manage it. A license portal listing:
| machine | status | action |
|---|---|---|
| Windows workstation | Activated | [Deactivate] |
| Linux laptop | Activated | [Deactivate] |
would let me release an activation and move it to another machine without involving anyone.
Another recent post here [Accidentally deleted activated install without moving license - #2 by Stephen] had someone delete a Wine installation before deactivating it. The activation was stranded and support reset it by hand. The same thing happens after an OS reinstall, a dead SSD, a lost or broken laptop, or a motherboard swap. Each one costs the
user a wait for a reply and costs you a manual ticket.
The activation service already tracks activation state server-side, otherwise it could not report both slots as occupied. Showing those slots to the license owner, with a cap of two remote deactivations per 90 days, keeps the current licensing model intact and takes the common
cases off your support queue. The cap is what stops a license being passed around a team.
I write software for a living. If self-service deactivation is something you’d take outside help on, I’ll put development time into it.
Regards