Artistic Rendering is absurdly slow on mac WIP

(Tom) #1

Hi Rhino team,
it seems that the new WIP (2019 April 9th) is stalling for several minutes when one tries to use the artistis rendering. Once it’s started, it works alright.
Thought I’d signal it.

Keep up with the good work,
Thank you


(Wim Dekeyser) #2

Hi Tom - was this working differently in a previous WIP release?
Also, could you run the Rhino SystemInfo command and post the result here?


(Tom) #3

Wim, this is my first WIP for Rhino 6.I did most of the WIP of v5 back in the day.
can’t tell you more on the previous version of the WIP v6 but here is my SystemInfo (redacted for privacy):

Rhino 6 SR15 2019-4-9 (Public Build, 6.15.19099.12046, Git hash:master @ 00878fbc356e8a3ae40dbaf4d502416407a02c6e)
License type: Beta, build 2019-04-09
License details: Cloud Zoo. In use by: XXXXXXXXX
Expires on: 2019-05-24

Apple Intel 64-bit macOS Version 10.13.6 (Build 17G5019) (Physical RAM: 4Gb)
Mac Model Identifier: MacBookAir4,2
Machine name: XXXXXXXXX
Language: en-US (MacOS default)

Intel HD Graphics 3000 OpenGL Engine (OpenGL ver:3.3 INTEL-10.4.14)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: None
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height

Vendor Name: Intel Inc.
Render version: 3.3
Shading Language: 3.30
Maximum Texture size: 8192 x 8192
Z-Buffer depth: 24 bits
Maximum Viewport size: 8192 x 8192
Total Video Memory: 384 MB
Graphics: Intel HD Graphics 3000
Displays: ASUS PB258 (118dpi 1x), Color LCD (128dpi 1x)

Graphics processors
Intel HD Graphics 3000 (384 MB)
Color LCD (1440 x 900)
ASUS PB258 (2560 x 1440 @ 60 Hz)

USB devices
Apple Inc.: FaceTime Camera (Built-in)
Apple Inc. : Apple USB Ethernet Adapter
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple Inc.: Bluetooth USB Host Controller
Apple Inc.: iPhone
Microsoft: Microsoft® 2.4GHz Transceiver V1.0
Apple: Internal Memory Card Reader

Bluetooth devices

Third party kernel extensions
com.usboverdrive.driver.hid (3.1) B3A2DDFC-9EF0-32D6-8076-33A40FF7FCC7

Third party plugins

Rhino plugins
/Applications/ “RhinoCycles” 6.15.19099.12046
/Applications/ “STL Export” 6.15.19099.1002
/Applications/ “Displacement” 6.15.19099.1002
/Applications/ “Snapshots” 6.15.19099.1002
/Applications/ “Grasshopper” 6.15.19099.12046
/Applications/ “Rhino Bonus Tools” 6.15.19099.1002
/Applications/ “Named Position” 6.15.19099.1002
/Applications/ “RDK_EtoUI” 6.15.19099.12046
/Applications/ “PanelingTools” 6.15.19099.1002
/Applications/ “AnimationTools” 6.15.19099.1002
/Applications/ “Commands” 6.15.19099.12046
/Applications/ “SolidTools” 6.15.19099.1002
/Applications/ “Renderer Development Kit” 6.15.19099.1002
/Applications/ “Rhino Render” 6.15.19099.1002
/Applications/ “IronPython” 6.15.19099.12046


(Wim Dekeyser) #4

Thanks for that information, Tom.

You might already know this, but when the display mode is set to any of the so-called Technical display modes, among which is the Artistic mode, Rhino has to create a new set of display meshes. On large models, this can take some time. Once those meshes are created, you can switch to other display modes and back without these meshes having to be created again.

Are you saying that the exact same model produces these meshes much faster on your Rhino 5 installation than on Rhino 6?