Wish: WIP key also for Rhino 6 customers

Hi @dan,

it would be nice, if Rhino 6 customers could also get a Rhino 6 for Mac WIP test key from here:
https://www.rhino3d.com/download/rhino-for-mac/6/wip

Thanks

Michael
www.flexiCAD.com

Right now I cannot download the WIP with my Rhino 6 commercial key.

I see you have an open issue here: https://mcneel.myjetbrains.com/youtrack/issue/RH-44039
But I also see the last comment saying that maybe it won’t be supported…

Can anyone confirm this?

The Mac V6 WIP cycle is only open for owners of Rhino V5 for MAC.
When MAc V6 is released, then a V6 license key will work for either Mac or Windows, but not until it’s finalized and released.
That will be a while.

2 Likes

Another option is slightly circuitous, but will work:

  1. Visit https://www.rhino3d.com/access-rhino-5/mac
  2. Enter your Rhino 6 license key (upgrade keys not eligible)
  3. Get a Rhino 5 for Mac license key
  4. Download the Rhino for Mac WIP using the key from the previous step

So basically I can you can use my RH6 for Windows license also for Mac?

Not now, but eventually.

Rhino 5 for Mac and Rhino 5 for Windows use different license keys.

Rhino 6 license keys are not platform specific for the released product.
Right now, there is only a released V6 for Windows.

When V6 for Mac is completed and released, then a Rhino 6 key will work for either one.

2 Likes

YEAH!!!
That’s awesome, thanks!

@pablo2
If your V6 key is not an upgrade, you can get a “Legacy Mac V5 key” using the link on the Support page.
Once you have that, you can use it to get the beta key.

Thank you John, but unfortunately it is an upgrade. I am one of those long time Mac users stuck on parallels…

This is great news!
I can finally stop using parallels on my mac and switch from using V6 on windows to V6 on mac.
You guys are the best!!

I hope this means that with similar coding the differences in the two would not be as big as they are now. Its understood though that platform specific differences will be there.

V6 Rhino and Mac share a bulk of the same core code, so generally, your statement is correct.
However, the U/I will remain very different and with respect to plug-ins, that’s an entirely different situation.