Rhino 6 License Validation Changes

Continuing the discussion from CDKey Lookup Changes:

In Rhino 6, license validation will be more strict in some ways, but less strict in others.

  1. A user validating a Rhino 6 Upgrade license will be required to enter a previous version license. That previous version license must have a complete upgrade chain back to Rhino 4.

  2. Once upgraded, Rhino 5 licenses are no longer valid for validation. So new installations of R50s that upgraded to R60U will not be allowed to validate. We may change this policy if we find lots of users have legitimate reasons to need R50.

  3. Future validations of R60U licenses that have already been associated with previous versions no longer require a previous version license key to be entered. For all intents and purposes, the R60U becomes a full version license assigned to the email address used to validate. The intent is to make it so our customers don’t need to keep detailed records linking their licenses together. In fact, they could just throw away their old licenses after validating.

What do you think?

I like it, but I’d be careful about implementing #2 too quickly since I predict that for a while some plugins/scripts/pascal hacks will require us to go back to V5 for certain operations.

What if you allow to validate the upgraded V5 only on same machine/s that have the new associated V6 installed? Or too confusing?


1 Like

I second about the second one (V5 expiring). With most of new versions of our core software we need at least 1 year overlap between previous and new version. Cutting off V5 would be very problematic.


Maybe the reasons are in the linked topic, but that is inaccessible to mere mortals. It would be nice if the change of such a policy is accompanied by the reason(s) for the change. Do you want to move as many people as possible to R6 as soon as possible? Is there a technical reason (I dunno, changes in Zoo or something)? Do you want to combat piracy?

This will help to get acceptance for the changes.

It looks like I pulled an Edward Snowden :slight_smile: That other topic is about internal tools we use for viewing the state of licenses, and is only tangentially related to this discussion.

More and more we run into customers that call and say “I have 5 Rhino licenses, and I’d like to upgrade”. What they have are two Rhino 2 licenses, one Rhino 3 upgrade, one Rhino 4 upgrade, and one full Rhino 4. This is really only three licenses. Some people misunderstand our licensing and think that because they have five keys that they have five licenses. We’re working to change that.

Let’s see if I understand number 1. if a user bought a new RH5 2 years ago, he won’t be eligible for an update to RH6?

Incorrect. Everyone who has a RH5 will be eligible to upgrade to RH6 once. But after they do that, the RH5 license will no longer be usable to upgrade to a future version - it is tied to the first RH6 used to validate it.

But if users have an RH5U (Rhino 5 Upgrade), that license requires a valid previous version (RH4, RH3, …) in order to upgrade to Rhino 6. This lets us capture a string of licenses into one: RH4 -> RH5U -> RH6U.

1 Like

As far as I understand: as a user of a valid RH5 I am facing a purchase of a new RH 7 (or higher) licence once it appear.
After RH6 no more upgrades for me.
What about future upgrade from RH4 to RH7?

No, that’s not the intent at all.

The intent is that you can upgrade your RH1 to RH2, then RH3, then RH4, then RH5, then RH6, 7…

What we’re trying to do is make you realize that you still have one license. If you represent a company, your company doesn’t get to use Rhino 1 on one machine, Rhino 2 on another, Rhino 3 on another… you only have the latest version of Rhino available to you.

Since we know when you validated your Rhino 6 license, we could have a window where the previous version license can be validated. We could play with the window on our end depending on customer need.

That way, if you upgraded to Rhino 6 today, your Rhino 5 could still be validated for X days before we stop allowing it.

So far this thread makes it sound like a user who wants to have both R5 and R6 (say) on one machine for whatever reasons would need two licenses even though he will only be using one at a time? I have the impression from this forum that many users have both R4 and R5 because they sometimes need to revert to R4 for some feature or capability they prefer.

No. A user is welcome to have R1 - 6 on the same machine… assuming they purchased Rhino 1.0 and then upgraded a number of times.

What they can’t do, is run the R1 and the upgrades on many different machines.

For me -

  1. That’s sounds fine, mine should go back to 1.1

  2. Not an issue for me so long as we get full capabilities to read/write previous 3dm versions (as McNeel have always done in the past).

  3. That’d be good, I could throw away this box of cd’s and keys that I’ve been previously guarding with my life!


I currently use my license one machine at work and then laptop when at home or on the road.

I’d want both R5 and R6 available (for the aforementioned plugin compatibility reasons).

Will this be possible on the proposed arrangement?

Thanks, Steve

You should keep all the old ones. They will be worth millions 100 years from now. :slight_smile:


Should that not be suffixed with "at the same time "
As with the current system?

What I take from this thread, is that upgrades on a full licence are chained and considered 1 licence.
Which is not new. What did change is the way this is going to be ‘enforced’ in the licensing system.

Please correct me if I’m wrong I just try to put out a fire getting wild.


My understanding has been that you could have a license installed on e.g. a desktop + a laptop at the same time provided that they weren’t both being used at the same time.

Ha! Bob, I hope I’ll be dead by then…

Exactly. In the past, the only enforcement of connecting licenses together was our trust that you’d read and abide by our license agreement (and, thankfully, in a majority of the cases that works great!). But, for those people who are taking advantage of that trust, we’re working on software to help them be compliant.

Also, we spend too many hours helping larger companies that have lost track of how many licenses they have and which can be upgraded.