Exciting results from an early testing image using the Cycles X integration into Rhino for Mac.
EDIT: This improvement is specifically for m1 and m2 machines.
500 samples, 46.94 seconds 1287x859 M1 Max with 32 cores.
compared to same image in v7 on the same machine
500 samples, 10 min 34.77 seconds 1287x859 M1 Max with 32 cores.
v8 is shaping up nicely folks… especially for the mac users
if you are a v7 owner, grab v8 and give it a go here-
Hi @theoutside
Is Cycle X already in the public build…? or is it in the coming release ?
I’m trying to test, and its extremely slow on my [new] MBP
I also only see CPU usage in the activity monitor [the GPU is not used at all]
thanks a lot
Akash
congratulation to the whole team!!!
this is amazing news, lets go 
keep these good developments coming!!!
Best wishes from Vienna,
Rudi
should be in the june 27th build. 8.0.23178.14306
The WIP say it’s the latest one… [and I didn’t see a post about a WIP build this week]
and the render pref doesn’t have a place for Mac GPU in this build
any suggestion?
thanks a lot
Akash
yep, you need a later build.
there was a stop ship issue this week… should be available next week
after seeing the screenshots posted by @Akash, i’m now curious which mac comes with an nvidia card to support cuda and optix?
this improvement specifically affects M1 and M2 models of the Mac.
the last macs that came with Nvidia were around 2015
that will be the default for m1 and m2 machines. You will not have to set anything.
yes, those were in macbooks back then, i think. still doens’t explain why there is optix support in the rhino-mac version. are you trying to make rhino-mac hackintosh friendly?
@andy or @nathanletwory would have to answer that for precise accuracy.
I’m assuming it’s either legacy code that hasn’t been cleaned up yet, or there to allow older hardware for the time being.
I would also assume that will likely change as we get closer to release as we tighten the system requirements, but will defer to the folks actually making this decision.
That is not the droid you’re looking for. It is old code, only supported devices will be shown whenever the next WIP goes out.
This is a game changer, thanks to everyone at McNeel.
I’ve been playing with it a bit and found an issue: a spotlight will show up in ‘Rendered’ display mode, but will not show up when running the ‘Render’ command. What am I doing wrong?
All objects are on the default layer. Seen the advice elsewhere to turn the spotlight intensity up to very high numbers (I tried 1000, 10’000, and 1’000’000, none made any difference).
Awesome!
Is there a Test Scene we could try ?
I’d love to understand what kind of performance is now possible?
it is now much faster then it was before, but how it is compare to Rhino on Windows and also to other render options…?
thanks a lot
Akash
Rendering does not seem to work on my Intel MBP16":
I am trying to render a simple cube, but it gets stuck at Updating Lights: Importance map. When I abort the rendering (with RaytracedView as well as with Rendering) Rhino freezes…
Also: Just drawing a simple cube and switchin to Shaded View is extremely slow.
@theoutside
Edit: Raytraced Viewport works now, but this is what I get from the Render output:
@rudolf.neumerkel looks like this is only an improvement for M1 and M2 Macs. I always found rendering to be very slow on my Intel Macs.
Yes, but Metal should utilize Metal supported GPUs. The dedicated AMD gpu is supported afaik
Edit: AMD gpus should run accelerated with Cycles on Mac.
It is only the Intel GPUs that will most likely need to run CPU based and even in that case they should be much faster than V7
