Just downloaded the latest WIP as my previous one was out of date. I opened a legacy file (V7) with nothing but a bunch of curves in groups (not a heavy file) and started to move stuff around, ungrouping and grouping, copying, and using the gumball to move stuff. I usually work in Testmetal mode (MacBook Pro M1Max chip) but was shocked to find it way slower than when I last used RhinoWIP in January.
Previously, I was getting 100+fps in Testmetal, but tonight it couldn’t have been over about 5 fps.
I switched into legacy OpenGL to keep editing my curves and after maybe 5 minutes of move copy delete commands, I tried to do a free gumball rotation on a group of 10 or so curves, WIP froze and crashed! I can’t remember the last time rhino actually pinwheeled and crashed.
I submitted the crash report of course, but was wondering if others were also having performance losses in the latest WIP release.
I reopened the file (of course I lost my revisions because I didn’t upgrade) and did a Testmaxspeed in wireframe view.
testmetal: 210FPS
legacy openGL: 123FPS
I switched into shaded mode and set the single color background, and altered the curve thickness in Preferences → Display Modes → Shaded as I did before my crash last time and repeated the Testmaxspeed command again with the following results:
When doing these tests, in Testmetal the viewport froze for the duration of the test and in openGL it did actually spin. I reverted the background setting back to Use Application settings and repeated the tests:
I reentered the settings I had in the previous file to the Wireframe view mode (Curve width 2 px, Single color background) and repeated the test in the two modes again:
I’ve moved your post to the more appropriate Serengeti category that is about RhinoWIP.
I remember noticing sluggish viewport behaviour, but instantly rolled back to the previous version (8.0.22130.14236, 2022-05-10), when I noticed that Grasshopper was broken. I’m skipping this one.
You can find the link to the download here in Wim’s reply:
I wonder whether the test is working right, but it’s a beast of a computer considering its size and energy consumption.
As you may know, Rhino doesn’t take full advantage of Apple Silicon chips yet. However, in other, more optimized applications - like Blender - you really notice what it can do.
Yesterday, I saw this on the Bella Renderer website:
On the right they compare their render engine Vs. Cycles on the left.
So I tried the classroom scene in Blender with Cycles GPU and 800 samples, which produces a much less noisy and clear image than in the Bella comparison.
The scene is not identical to the one from blender, it was given to me by a user who converted it by hand, and it uses different lighting – I’ll redo this comparison on the site using some different scene, since I see it caused some confusion here.
At this point, we are still working on just making things work with different scenes and different hardware. Performance optimizations come after that work is done. That said, without specific information and a model, you are not giving us anything that we can work with. What is slower? Launching Rhino, exporting a STEP file, modifying an annotation style, …? I can only guess…
That turned out to be crashing on many Macs and was taken out. Rhino 8 will be running Metal and OpenGL, if still available, will only be a backup.
-wim
I have macbook pro 2017 with radeon pro 560.
When i turn off antialiasing in both version and switch viewport mode on shaded in Rhino 7 is moving with complicated model very smooth and no lagging compared to verison 8.
I will record short video in the evening.
P.S. Maybe reading 3dm file is a little bit longer in v8. But I’m not sure now.
We haven’t turned on Metal by default because of a few remaining issues on specific hardware, but, to test display performance of the Rhino WIP on macOS, you’ll have to run TestMetal to switch to that. As I said, OpenGL will only serve as a backup, if at all it’s still included when we ship Rhino 8. If it is, we’ll try to make sure that it won’t crash on systems but you shouldn’t expect performance in that mode.
-wim
hello. it happens to me in rhino wip for a long time that after 3 -4 hours of work rhino is terribly slow and I have to restart it. Does anyone have a similar problem?
Apple macOS Version 13.5 (Build 22G74) (Physical RAM: 24Gb)
Mac Model Identifier: Mac14,7
Language: en-GB (MacOS default)
Apple M2 (OpenGL ver:4.1 Metal - 83.1)
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: Apple
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: 16 GB
Graphics: Apple M2
Displays: Unknown (108dpi 1x)
Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M2
DELL U2719DC (2560 x 1440 @ 60.00Hz)
USB devices
CalDigit, Inc.: USB-C SOHO Card Reader
3Dconnexion: CadMouse Pro Wireless
CalDigit, Inc. : USB-C SOHO Dock
Rhino plugins that do not ship with Rhino
/Users/petermasek/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/DatasmithRhino7.rhp “Datasmith Exporter” 5.2.1.0
/Users/petermasek/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/bella_rhino.rhp “Bella” 23.4.0.0
