Render material library seems corrupted

Hello - I’m having trouble with the render material library in Rhino 8 Mac. It’s been working fine since I upgraded to Rhino 8 a month or two ago, but today, when trying to load a new material from the library, it either causes Rhino to hang, or brings in the material but it’s just a solid magenta rather than what it should be. I’ve tried several existing files and brand new empty models and get the same behaviour. And I’ve tried a load of different materials from the library with the same result - either a crash or a corrupted material is loaded.

I’ve uninstalled and reinstalled Rhino and still get the same problem. Any help would be gratefully received as I’m working on some renders for a client!

My system info report is copied below. Many thanks!

Rhino 8 SR5 2024-3-12 (Rhino 8, 8.5.24072.13002, Git hash:master @ e3530849b75f00b2b977766a567ae29b055837e9)
License type: Commercial, build 2024-03-12
License details: Cloud Zoo

Apple macOS Version 14.4.1 (Build 23E224) (Physical RAM: 32GB)
Mac Model Identifier: Mac14,13
Language: en-GB (MacOS default)
.NET 7.0.0

Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M2 Max
Studio Display (2560 x 1440 @ 60.00Hz)

USB devices
3Dconnexion: SpaceNavigator
Apple Inc.: Magic Keyboard with Touch ID and Numeric Keypad
Apple: USB3 Gen2 Hub
Apple Inc.: Studio Display

Bluetooth devices

Third party kernel extensions

Third party plugins

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
/Applications/Rhino “Renderer Development Kit” 8.5.24072.1002
/Applications/Rhino “Commands” 8.5.24072.13002
/Applications/Rhino “Snapshots” 8.5.24072.1002
/Applications/Rhino “RDK_EtoUI” 8.5.24072.13002
/Applications/Rhino “MeshCommands” 8.5.24072.13002
/Applications/Rhino “Rhino Render” 8.5.24072.13002
/Applications/Rhino “RhinoCycles” 8.5.24072.13002
/Applications/Rhino “AnimationTools” 8.5.24072.1002
/Applications/Rhino “SectionTools” 8.5.24072.1002
/Applications/Rhino “Legacy Rhino Render” 8.5.24072.1002
/Applications/Rhino “Displacement” 8.5.24072.1002
/Applications/Rhino “PanelingTools” 8.5.24072.1002
/Applications/Rhino “IronPython” 8.5.24072.13002
/Applications/Rhino “Grasshopper” 8.5.24072.13002
/Applications/Rhino “RhinoCodePlugin” 8.5.24072.13002

Hi Andy - do you have just one monitor?


The hang could be that Rhino is trying to load textures from our server. Magenta means that failed eventually.

Try running the Rhino command _DownloadLibraryTextures. It will download all textures in one go. Once that has successfully completed try the materials from our library again.

Any better?

Hi Pascal - thanks for the quick response. Just one monitor yep!

Hi Nathan - thanks for the quick response too! I’ve run that command. It finished with the command line reporting “Unpacked textures for 1306 render content files”. It seems to load materials faster but I still get the magenta textures. I’ve restarted Rhino with the same result.

You may want to run also the non-autocompleting command TestClearRDKCaches. Then in a new document try adding a material from the library. Does it work now?

Thanks Nathan - done but still the same issue!

When you create a simple box and assign such a material to the box, then switch to Rendered mode, what do you get? And when you switch to Raytraced mode?

Maybe a screenshot of what you are seeing could help here

Hi Nathan - screenshots attached!

If you drill into the plywood texture in the Rhino material UI a path should be shown. Does that path exist with that image file?

Interestingly there’s a file there with the right name but it’s zero bytes. The same is true for the other four materials I’ve tried to load since I’ve been having this issue. But all the other texture files look fine.

Can you remove all image files that are zero bytes in length, then rerun the download command?

Ah - that appears to have fixed things! Thank you! Any idea why this happened or whether it’s likely to do it again?

I don’t know why the creation of those files failed. But now that you have the correct files it should no longer happen.