Rhino 7 Feature: Display Performance

I’ve been working on a very object heavy 1GB Rhino file with a single detail view in Layout Space, and I’ve just installed Rhino 7 WIP to see how this file handles in comparison to Rhino 6…

Rhino 7 is actually much slower than Rhino 6 when panning around Layout Space. Unfortunately I can’t share this specific file with you, but maybe when I get a chance I can recreate one just as big.

FYI - It’s Arctic display mode that endures the lag, and it’s more so when I zoom rather than pan.
TestMaxSpeed results: Rhino 6 = 10.27 seconds. (9.74 FPS) / Rhino 7 = 13.69 seconds. (7.31 FPS)

I’m actually seeing a small decrease according to TestMaxSpeed
R6: 6.84FPS
Rwip: 5.99FPS

Mine doesn’t have Nested Blocks or Text. It’s mostly weighed down by Point Lights. It was also built in R4.0 originally.

I checked file 162 MB with Rihno WIP. Display opens in 6 sec. Save’s in 70 sec. Meanwhile Rihno 6 display open’s in 20 sec and save’s in 82 sec. I think it much depends on the computer specification.

Please edit this before I kill a baby panda.

What on earth is the problem? All I’m trying to do is help and improve Rhino/Grasshopper for our users.

2 Likes

Saying Nested blocks often come from OUTSIDE Rhino is exactly like saying :
“Nested Blocks in Rhino are a steaming, stinking pile of s__t, and we don’t give a f__k, but don’t worry, you can make them elsewhere and import them juuuuuust fine !”

If, like me and many others, your whole business relied on models almost entirely composed of blocks, you would never have the nerves to write something like that.
Get working on the damned blocks already !!!

1 Like

in other words: please put this high on the list :slight_smile:

1 Like

Guess I’ll never get this thread cleaned up from cross posting. We released an email about display performance improvements pointing to this thread and have gotten quite a number of posts here unrelated to display performance. I was trying to clean things up and keep them organized.

1 Like

I’m going to hire you as my Public Relations Officer :grin:

1 Like

3D model with a size about 2GB, containing blocks, texts. Didn’t feel any faster comparing to R6.

TESTED on MacBook Pro
File - 320 mb / containing a big mesh landscape, 2 objects / houses (quite detailed), no text or annotations

TEST MAX SPEED - SHADED

Version 6 (6.23.20035.13182, 2020-02-04)
9.2 sec, 10.87 FPS

Version 7 WIP (7.0.20014.12056, 2020-01-14)
11.45 sec, 8.74 FPS

SI:
Apple Intel 64-bit macOS Version 10.15.2 (Build 19C57) (Physical RAM: 16Gb)
Mac Model Identifier: MacBookPro14,3
Machine name: newyork
Language: en-NO (MacOS default)

AMD Radeon Pro 560 OpenGL Engine (OpenGL ver:4.1 ATI-3.4.19)

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: ATI Technologies 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: 4 GB
Graphics: Radeon Pro 560
Displays: Color LCD (258dpi 2x), LG UltraFine (173dpi 2x)

Graphics processors
Intel HD Graphics 630 (1536 MB)
Radeon Pro 560 (4 GB)
Color LCD (1680 x 1050)
LG UltraFine (2048 x 1152)

USB devices
Apple Inc.: Apple T1 Controller
LG Electronlcs Inc.: LG UltraFine Display Camera
3Dconnexion: CadMouse
LG Electronics Inc.: USB Controls
LG Electronics Inc.: USB Audio

Bluetooth devices
Broadcom: Magic Keyboard

Third party kernel extensions
com.f-secure.kext.nke (1.0.1) 36363734-C01F-3B4D-B7B5-672287228D6F
com.3dconnexion.driver (1.1.0) 94E8C49C-EDED-3526-88BE-E7207560C0D2
com.f-secure.kext.fsauth (1.0.5d1) 82AD7A11-7E6E-31C0-8A45-309DFCA2105A

Third party plugins
/Library/Frameworks/3DconnexionClient.framework/Versions/A/3DconnexionClient
/usr/lib/log/liblog_network.dylib

Rhino plugins
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 7.0.20014.12056
/Applications/RhinoWIP.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 7.0.20014.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 7.0.20014.12056
/Applications/RhinoWIP.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 7.0.20014.1002
/Applications/RhinoWIP.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 7.0.20014.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 7.0.20014.12056
/Applications/RhinoWIP.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 7.0.20014.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 7.0.20014.12056
/Applications/RhinoWIP.app/Contents/PlugIns/Displacement.rhp “Displacement” 7.0.20014.1002
/Applications/RhinoWIP.app/Contents/PlugIns/NamedPositions.rhp “Named Position” 7.0.20014.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp “Rhino Render” 7.0.20014.12056
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 7.0.20014.12056
/Applications/RhinoWIP.app/Contents/PlugIns/RhinoRender.rhp “Legacy Rhino Render” 7.0.20014.1002

Macs are a different story at the moment (as of yesterday). We are testing a bugfix that Apple has made in their display drivers which should be available in the next update to the OS. We’ve tested on one AMD based Mac so far and saw great results so fingers crossed we will get a nice boost even on V6 for Mac in the near future. I would hold off with doing any comparisons until that point.

well done, very fast for the nested blocks than v6, and 10x faster than v5

I’ve tested file with '25’528’363 total triangular polygons’, it works on WIP7 very well!

1 Like

Thanks @stevebaer,
I am fully aware of the different mac story, just wanted to give you some feedback on performance with R7 on mac. I don’t have any doubts there will be a great improvement in terms of performance in the future :slight_smile: Good luck anyway!

Petr

how did you check your fps? couldn’t find the TestMaxSpeed command on the Mac versions…

The command doesn’t have autocomplete… copy/paste is your friend! TestMaxSpeed

Cheers

Andreas

thanks a lot, this makes sense…
and btw. ich checked some heavier models and couldn’t see any improvements on the Mac platform yet - @stevebaer mentioned that already.

Did you try to update OS? @stevebaer also mentioned that some improvement comes with the newest OS update, though I don’t know if it has been published…

The OS service release has not been published by Apple yet. We’ve been testing with their beta