okay so basically it took 8h+ for my render in draft quality and 72 DPI to finish to 610/1000 - essentially what I wonder - 1. what possible settings are there that I dont know about that might speed up rendering time 2. Well I already know my computers RAM capacity: 8 GB is not great but what specs (in a macbook) is it that affects up rendering time?
Apart from this Rhino has crashed a lot while Im working meaning its bit of a no brainer to just buy a new computer, because i guess that has nothing to do with anything else than my computer? Im not running any programs at the same time or even in the background so I think its just my computers pure capacity thats failing?
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: Intel Inc.
Render version: 4.1
Shading Language: 4.10
Maximum Texture size: 16384 x 16384
Z-Buffer depth: n/a
Maximum Viewport size: 16384 x 16384
Total Video Memory: 1536 MB
Graphics: Intel Iris Graphics 6100
Displays: Color LCD (256dpi 2x)
Graphics processors
Intel Iris Graphics 6100 (1536 MB)
Color LCD (1440 x 900)
USB devices
Seagate: OneTouch SSD
Broadcom Corp.: Bluetooth USB Host Controller
Bluetooth devices
None
Third party kernel extensions
None
Third party plugins
/Users/macbookpro/Library/Application Support/McNeel/Rhinoceros/packages/7.0/IntelDenoiser/0.6.0/libtbb.dylib
/Users/macbookpro/Library/Application Support/McNeel/Rhinoceros/packages/7.0/IntelDenoiser/0.6.0/libtbbmalloc.dylib
/usr/lib/log/liblog_network.dylib
/Users/macbookpro/Library/Application Support/McNeel/Rhinoceros/packages/7.0/IntelDenoiser/0.6.0/libOpenImageDenoise.1.2.3.dylib
Rhino plugins that do not ship with Rhino
/Users/macbookpro/Library/Application Support/McNeel/Rhinoceros/packages/7.0/IntelDenoiser/0.6.0/IntelDenoiser.Mac.rhp “IntelDenoiser.Mac” 1.0.0.0
It looks like your machine is at least 8-9 years old - I don’t know what is supported, but I would see if you can get a more recent version of the Mac OS - that said, I do not think it will ever be very fast. It might be worth trying the legacy renderer (Render menu > Current renderer), I don’t know.
Hi! I have a Mac Book Pro from 2019 but I find the rendering still very slow (RAM capacity of 16GB). I think a PC will do better? The program Rhino is originally made for Windows and perhaps the version for Mac is still not compatible? Just made a render → 50 samples, good quality, this took the program 3 hours and the image isn’t even of a good quality. Moddeling in Rhino 7 is great, but the rendering is taking way too much time, or is this normal? Also the draft renders make no difference still very slow.
Drawn a simple white block, turned the render on, selected good quality, size 800x600px, 50 samples → takes 2 min. (no environments, no lights etc.) See attachment.
CPU based rendering will be that fast with the default settings and your simple box set up… I have a similar Mac here and get around 2 mins with the same image size.
There are two things you can do though in Rhino 7 that will help speed things up. Use the command PackageManager and install the “Intel Denoiser” and the “ProRender” plugins. They are both free and will really help here. The denoiser removes grain as a post effect so that you don’t have to get to as high a sample count. Generally between 50 and 200 samples is good and then denoise it to remove any grain in the shadows. ProRender on the other hand is a different renderer, switch to it in the Render drop down menu > Current Renderer flyout. Then run the Render command again on your simple box set up… it’ll probably be about 2 seconds for the 50 samples. ProRender will use your AMD GPU for the raytracing instead of the CPU.
Hi everyone, thanks for your replies. It ended up that way that I bought lightly used second hand Macbook from 2017, with much better specs than my previous one.
Thanks @BrianJ for the tips. I do use Denoiser but will apply ProRender too.
@kim3 For me it was the same, although the program continued crashing constantly so I figured a new(er) computer was necessary anyway.
