Rhino Render Won't Start

Rendering
1

I’ve been trying everything I can to get my render to start but I simply can’t. For a rundown of what I’ve tried I have up to date drivers, I have modified my settings like the sample size and bounce limit to significantly lower, I have disabled my plug ins, the render window DOES pop up in other simpler rhino files. The one thing I believe might be really the problem is the file size itself which I brought down from 5000MB to 3000MB (which I don’t really understand what is taking up so much space since I have everything in blocks. I understand 3000MB is still large, but the render window not popping up at all is strange. I have already tried being patient and simply waiting for the render window as far as one hour long, but nothing has worked. I’ve attached the file below.

https://drive.google.com/drive/folders/1iBlSwzfM5qe3DoF0CfGRQHgKWaMMlpSq?usp=sharing

File

Rhino 8 SR22 2025-8-5 (Rhino 8, 8.22.25217.12451, Git hash:master @ 96429e6361004c775cd83973f2148f3943b5e512)
License type: Educational, build 2025-08-05
License details: Cloud Zoo

Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 32GB)
.NET 8.0.17

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics (Intel) Memory: 2GB, Driver date: 8-19-2025 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA GeForce RTX 4070 Laptop GPU (NVidia) Memory: 8GB, Driver date: 8-7-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 580.97
> Integrated accelerated graphics device with 4 adapter port(s)
- Video pass-through to primary display device

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 8-7-2025
Driver Version: 32.0.15.8097
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8188 MB

Rhino plugins that do not ship with Rhino
C:\Users\lawre\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.22.25217.12451
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.22.25217.12451
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.22.25217.12451
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.22.25217.12451
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.22.25217.12451
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.22.25217.12451
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

2

it appears this file is over 3 gb?

is you machine even up to handling a file that large?

for instance on my most powerful machine, this took 9 min to switch into rendered mode.

it also seems like there is a large displacement happening, but I cannot figure out where.

displacement is very expensive, make sure you need it and can’t use bump instead.

you also have some bad objects in the scene… run selbadobjects to identify them.

in the end, this just may be a massive file, and you may need to throw a much bigger machine or render farm at it.

3

I let my work machine trying to switch to raytraced overnight, but was still chugging along. Removing the bad objects did not improve that much. Disabling the displacement in materials did maybe improve things a bit, but hard to say, since it still takes ages (presumably).

I logged RH-89013 Rhino appears stuck when trying to use Cycles

4

This came into tech support as well and I wanted to share my findings on the forum too in the event they help @Lawrence_Lo or other users with similar issues.

Your file has a number of inefficiencies which will make rendering it hard or simply impossible on some systems. I’ll explain what I found in investigating and offer you my best suggestions on working with this file further.

The Scrubs layer has a bunch of blocks and meshes using object properties displacement. Some of these are not calculating completely due to the number of polygons in the base meshes. This is preventing the rendering from starting. If you edit each block on this layer > select the mesh in it > disable displacement in Properties and also do the same for the meshes not in blocks on this layer, you’ll solve that issue. I don’t think you need displacement on meshes of this density if not zoomed in close on those objects and maybe not even then. You can also hide this layer to test rendering without those objects.

The Fencing layer is a ton of polysurfaces in blocks and then in groups. This is the wrong way to do this and adds a ton of memory overhead and object processing up front. Instead, use transparency maps in a material like how you are doing the grass. The fence panels should just be planes.

Lastly, even if you were to hide both of those layers and render, you’ll be using around half of your system RAM (16GB) and if raytracing with the GPU, you won’t have enough video memory on your card. I was using 24GB of VRAM as well as the 16GB of system RAM in my test. For this reason, you’ll probably want to go through each layer and clean things up. Blocks will not make things faster here for rendering, they only make it easier to edit lots of the same object in unison. So for rendering purposes, I would suggest instead using the ExtractRenderMesh command on any displacements you need and then delete the original object. SaveAs the file with a different name as you work so you have the original to come back to if necessary. After extracting the render mesh, the displacement will no longer need to be calculated. You can further reduce the memory overhead with ReduceMesh too on those meshes. Remember not to displace meshes that already have a ton of faces, you should be able to just use bump mapping in those cases if you need more detail.

I hope that helps.