Cannot change to Service Release Candidate Channel -> RH8

Here in my mac Version I cannot Use the SR Candidate update channel. If I select it in the options menu and try to force find a update it tells my I am up to date. If I restart Rhino with these settings the selection jumped back to service release.
I Use an Intel 2016 MBP but this problem also affects an M2 pro mac mini where I just wanted to test Rhino 8 on the Silicon chips.
Actually I am on the evaluation License

same exact problem here…

Rhino 8 SR0 2023-10-31 (Rhino 8, 8.0.23304.09002, Git hash:master @ 20e15cf9bd66e6676f849f22e485cb3e82a8beac)
License type: Evaluation, build 2023-10-31
License details: Cloud Zoo
Expires on: 4674337-08-16

Apple macOS Version 14.1 (Build 23B74) (Physical RAM: 16Gb)
Mac Model Identifier: MacBookPro16,1
Language: en
.NET 7.0.0

Metal GPU Family Apple 0
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
  Intel UHD Graphics 630 (1536 MB)
  AMD Radeon Pro 5300M (4 GB)
    LG Ultra HD (2560 x 1440 @ 60.00Hz)
    LG Ultra HD (2560 x 1440 @ 60.00Hz)

USB devices
  Generic: USB2.1 Hub
  Generic: USB2.1 Hub
  Apple: composite_device
  Apple Inc.: Touch Bar Backlight
  Apple Inc.: Touch Bar Display
  Apple Inc.: Apple Internal Keyboard / Trackpad
  Apple: Headset
  Apple Inc.: Ambient Light Sensor
  Apple Inc.: FaceTime HD Camera (Built-in)
  Apple Inc.: Apple T2 Controller

Bluetooth devices

Third party kernel extensions (3.7.0) 35E739F9-BF6C-3024-A67C-750711B3FB64
  com.Cycling74.driver.Soundflower (2) 2D779840-7439-31E5-8A66-D786C3F47B75
  com.paragon-software.filesystems.ntfs (149.8.15) B3791A17-53DF-3B03-9FF5-298D092ECF8C

Third party plugins

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
  /Applications/Rhino	"Renderer Development Kit"	8.0.23304.1002
  /Applications/Rhino	"Commands"	8.0.23304.9002
  /Applications/Rhino	"Snapshots"	8.0.23304.1002
  /Applications/Rhino	"RhinoCodePlugin"	8.0.23304.9002
  /Applications/Rhino	"RDK_EtoUI"	8.0.23304.9002
  /Applications/Rhino	"MeshCommands"	8.0.23304.9002
  /Applications/Rhino	"Rhino Render"	8.0.23304.9002
  /Applications/Rhino	"RhinoCycles"	8.0.23304.9002
  /Applications/Rhino	"SectionTools"	8.0.23304.1002
  /Applications/Rhino	"Displacement"	8.0.23304.1002
  /Applications/Rhino	"PanelingTools"	8.0.23304.1002
  /Applications/Rhino	"IronPython"	8.0.23304.9002
  /Applications/Rhino	"Grasshopper"	8.0.23304.9002

As I recall, SRC’s aren’t available to Evaluation versions - but hopefully someone from McNeel can give you an authoritative answer: @John_Brock ?

This seems to be the solution. I wasn’t aware of this.
I switched from the Beta to the 8.0 and use it the way i used the beta so I doesn’t thought about this.
It looks a little bit like a very sensitive moment in the development because I a lot beta Users maybe uses the eval version for some time . . . like one or two months or so before buy (just my feeling about). In this time there is maybe a lot less feedback for the SRCs.

Here’s my understanding:
At any point in time, when an evaluation is downloaded it is the current service release. It is fully usable for 90 days. During that period there would normally be about a dozen SRC’s.

I suppose it’s not surprising that the evaluation can’t be put in SRC download mode since it makes a certain amount of sense that McNeel wouldn’t want new “evaluators” exposed to the vagaries of experimental versions.

On the other hand, since McNeel seems to enjoy releasing for sale software that is very incomplete and buggy in the opinion of reasonable users and makes the evaluation version available for an additional 90 days waiting to see if it ever gets to the point of being worth the price they are asking, it makes perfect sense to me for the evaluation to be upgradable with SRC’s, at least for the period immediately following release of a new version.

How about that “authoritative answer” @John_Brock , @brian , @bobmcneel ?

Rhino is Rhino.
The evaluation is NOT a different version of Rhino. It’s just a timed license.
Rhino will check for updates and download them when it is run.
Rhino using a valid timed (evaluation) license in a Login account will run and update.
Expired licenses are NOT supported in a login account.
Expired licenses ARE supported if locked to a single computer.

If you are using an expired timed evaluation license locked to a single computer, when it runs, it will continue to check for service releases and they can be installed.

What did I miss?

Can you subscribe to Service Release Candidates if you are running an evaluation?

Yes, but I don’t understand what problem that might solve.
Options > Updates & Statistics > Update frequency:

Mac V8:

It has been suggested that people missing the Beta should download the Eval and get another 90 days of bug fixes before shelling out for the full version. We anticipate that there will be a large number of bug fixes. SRCs come out weekly so are similar to the beta, so the best tool for continuing that regime.

Users at the start of this thread report that they cannot get the SRC setting to stick, so as you have stated they should be able to, there would appear to be a bug in the updates system in R8.


Yes, but the problem with the SRCs, is the user is being exposed to “raw” code.
A Service Release has been out for a few weeks and is in a ‘don’t touch this code’ pattern before being released.

I would never suggest a SRC unless a specific fix was added that affects them. Think of like upgrading your gpu drivers. The best strategy is to NOT upgrade unless there is a specific problem you’re trying to solve.

Is there any way to get Rhino 8.1 release candidate on macOS ? Rhino isn’t able to find the update :

here’s the link from the other thread. Rhino 8 service release candidate unavailable - #2 by flixchameroy

Akash has the link.
This is Fixed in 8.1.
You’ll need to manually download the SRC, run it, replace the existing 8.0, and you should be good to go.

1 Like