DownloadLibraryTextures warnings on model open causing slowdowns

Priority: High

One user at our company unable to open a shared Rhino 8 model without triggering repeated warning messages on startup. The warnings cause Rhino to hang (“Not Responding”), produce extreme UI slowdowns in the layers/materials panel, and prevent Enscape from launching. No other user who opens the same model experiences this behavior. The issue persists across machines, indicating it is tied to the user’s profile or local configuration rather than the workstation hardware.

Error observed

The following warning repeats multiple times in the command line on model open:

Library materials that use texture maps require an Internet connection the first time they are imported. Use the command DownloadLibraryTextures before disconnecting from the Internet to access textures while offline.

The title bar shows (Not Responding) during and shortly after these warnings appear. The model contains multiple layers with Rhino library materials assigned (Concrete, Glass, Metal, Paint ramps). The warnings appear to correlate with those material assignments attempting to resolve textures on open.

Symptoms

  • Repeated DownloadLibraryTextures warnings loop on model open
  • Rhino enters “Not Responding” state during or after warnings
  • Extreme slowdowns navigating the Layers panel (materials column)
  • Enscape fails to launch due to unresolved Rhino warnings blocking the session

Troubleshooting steps already taken

  • Verified the same .3dm file opens without issue for all other users on the same file server
  • Tested on a second workstation with the affected user’s credentials - issue persisted, ruling out hardware or OS-level cause
  • Uninstalled and Reinstalled Rhino
  • Disabling Material Rendering in the Materials + Layers panel through Advanced
  • Confirmed the file has not been modified between test sessions
  • Confirmed materials are stored in a shared location in which this user has access to

Hi Maya,

One thing to try is to go offline and then open the file, if there are networked materials missing this will identify them quickly.

Lets try these as well :

  1. Clear the texture cache — delete or rename %APPDATA%\McNeel\Rhinoceros\8.0\Localization\en-US\Library\ and let Rhino rebuild it
  2. Check Rhino account — sign out and back in via Rhino’s account panel to refresh auth tokens
  3. Check proxy/firewall — verify the user’s machine can reach McNeel’s texture CDN (outbound HTTPS), particularly if on a corporate network with per-user firewall rules
  4. Reset material library paths in Rhino Options → Files → check that the library path resolves correctly for this user
  5. If none of the above work — back up and delete settings-Scheme__Default.xml to fully reset Rhino preferences for that user profile
  6. Run SystemInfo on the users machine and post the results.