Rhino 6 mac Beta

I would have thought next year as well, but then they dropped the 10,000 dollar Intel machine on our laps, and people will want those to last for a few years…

But Metal for Rhino 8 sounds great (but on the other hand I don’t think neither ARM nor the crazy expensive Mac line is doing anything to increase the MacOS market share, so it might not be as important then).

that would not exclude even having a macpro update by next year. i am also still thinking about buying that stupidly expensive computer, not that i can afford it. barley to be honest.

maybe, but i am happy that there is that little ying in the yang or yang in the ying. without it where would we be now… would we be at all.

I don’t really follow Metal development and I sort of quit worrying about what’s going on under the hood and instead just buy the hardware/software that does what I need it to… like- pay the devs/engineers to just make it work please :wink:

but-- if McNeel decides to integrate Metal into Rhino, does that mean it’s entirely different code for Mac graphics vs Windows? or, just sort of different?

or- how much work are we talking here and into the future, how much of the code could remain shared between the two platforms?
and can Metal only be used in conjunction with Apple’s operating systems?

Just tested here with testmaxspeed and got 2.37 with the new beta vs 3.41 with the previous beta.
no significant differences in the other modes I tested (technical, pen shaded, wireframe)

Thanks for testing. The changes I made would only affect objects with transparency which is why you wouldn’t see any changes with these other display modes.

I am working on some tweaks this weekend that will hopefully show improvements in technical and pen modes.

Please have a look also at wireframe mode.

Working in 2d with hatches, dimensions, curves and imported technical dwg files is still quiet unresponsive.

Hi, big problem…if I open recent model, Rhino doesn’t work…01
the only way is new model and import…

Rhino 6 SR16 2019-7-10 (Public Build, 6.16.19191.20064, Git hash:master @ 4fd981cd026fa4d158ffae1c86df15124b0847ba)
License type: Beta, build 2019-07-10
License details: Cloud Zoo. In use by: Pasquale Vazzano ()
Expires on: 2019-08-24

Apple Intel 64-bit macOS Version 10.14.5 (Build 18F132) (Physical RAM: 16Gb)
Mac Model Identifier: MacPro6,1
Machine name: Mac Pro di Vaz
Language: en

AMD Radeon HD - FirePro D500 OpenGL Engine (OpenGL ver:4.1 ATI-2.9.26)

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: Height

Vendor Name: ATI Technologies Inc.
Render version: 4.1
Shading Language: 4.10
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 3 GB
Graphics: AMD FirePro D500
Displays: HS246 (94dpi 1x), HS221HPB (102dpi 1x)

Graphics processors
AMD FirePro D500 (3 GB)
AMD FirePro D500 (3 GB)
HS246 (1920 x 1080 @ 59 Hz)
HS221HPB (1920 x 1080 @ 59 Hz)

USB devices
Apple Inc.: Bluetooth USB Host Controller
Mitsumi Electric: Apple Optical USB Mouse
Apple Inc.: Apple Keyboard
Generic: Mass Storage Device

Bluetooth devices

Third party kernel extensions

Third party plugins

Rhino plugins
/Applications/RhinoBETA.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 6.16.19191.20064
/Applications/RhinoBETA.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 6.16.19191.1002
/Applications/RhinoBETA.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 6.16.19191.20064
/Applications/RhinoBETA.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 6.16.19191.1002
/Applications/RhinoBETA.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 6.16.19191.1002
/Applications/RhinoBETA.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 6.16.19191.20064
/Applications/RhinoBETA.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 6.16.19191.1002
/Applications/RhinoBETA.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 6.16.19191.20064
/Applications/RhinoBETA.app/Contents/PlugIns/Displacement.rhp “Displacement” 6.16.19191.1002
/Users/pasvaz/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/Iris.Mac.rhp “Iris”
/Users/pasvaz/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/AsuniClasses.Common.rhp “LayerClasses”
/Applications/RhinoBETA.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 6.16.19191.20064
/Applications/RhinoBETA.app/Contents/PlugIns/RhinoRender.rhp “Rhino Render” 6.16.19191.1002

What kind of results do you get with TestMaxSpeed on the 2d wireframe model you sent me as well as your template model? I’m having trouble repeating the problems you are reporting for this model.

It does help, thanks. You should see noticeable improvements in performance for technical, artistic, and pen modes in tomorrow’s beta. Please test them out if you get a chance.

Marlin’s post on the difference of TestMaxSpeed is accurate, but I would say it is fine to continue to use this command to test differences in performance. If V5 gives you a result of 1 second and V6 gives you 5 seconds, then we know there is a real problem to address. If we see 0.5 second differences in time, then we may be splitting hairs and are simply seeing the results in changes to the command.

You have the same MacPro6,1 as I. Do you see a marked difference in line quality between v5 and v6 on the MacPro - whatever display your using? (the sharpness of lines and arc, or wireframe mode)

For me v5 is sharp and v6 quite noticeably and annoyingly inferior on the 6,1. Note - I do not see this discrepancy in behavior on any other 5k iMac I’ve tried. v6 looks great in wireframe on 5k iMacs.



Try closing Rhino, move these two MacPlugIns to a different location on your computer and then restart. I would like to eliminate the possibility that these plug-ins are causing the problem.

I think it is likely to do with the history of how and why the modes have been developed.

Others can explain better but the viewport mode that is called ‘rendered’ is rendered a bit like a computer game, ie the lighting is an unrealistic fudge and, I imagine, rendered by the GPU.

Using the render tool has traditionally used the rhino render engine which uses the CPU to calculate a higher quality image based more accurately on the lighting within the scene. I’m not sure what rendering technique has been used historically here but I don’t think it is raytraced. It appears to similar in some ways to the scanline renderer I used to use in another app years ago. This has always been far too slow to have as a live viewport display mode. It is also not as good as raytracing.

It is only fairly recently that raytracing could conceivably be performed in real time or near real-time. This, in theory should hopefully allow the two other tools / modes to be mothballed in due course which would remove the undeniable confusion that comes from there being two different images styles produced using tools called ‘render’ and a third by a tool called ‘raytrace’.

Now for hoping that raytrace mode and rendering speeds up a bit because the performance on my pretty new Mac is still really bad! I have to remember (this is vitally important) to not save and close a file with raytrace display mode activated. If I forget, the file takes FOREVER to load as Rhino prepares and starts rendering the raytraced view. So so painful.

ok…I just move “AsuniClasses.Common.rhp “LayerClasses”” and now works…great!!!

In the latest RhinoBETA, you can use TestToggleTechDisplayMode to turn on some recent optimizations that may - depending on your feedback - make their way into a subsequent service release. You can run the command again to turn it off. As always, please report any bugs you see.

Based on the test command name, these optimizations are specifically for technical, pen and artistic modes.

We do know that there are issues with this command and blocks right now. This should be fixed by next week.

On my machine (mid-2018 15" Pro with 560X) I notice improvements in performance and no change in visual quality in all three modes, particularly pen mode. It’s not the best, but it is much better. Thank you!

A post was split to a new topic: Merge Layers

I don’t use any of these except Blueprint which I believe is based off one of them (?)…

but yeah, the test command does improve this mode… without the TechMode test, there’s a slight delay prior to accelerating the navigation (using a trackpad which has a sort of acceleration/deceleration thing)

after running the test command, this little lag goes away…

also, if I TestMaxSpeed, I get nearly double the frame rate with TestTechDisplayMode toggled on…

(36FPS vs 20)

sorry, that’s all I got for this particular test :wink:

Don’t be sorry, that is great. Also, yes blueprint would be affected by this change. I’m hoping to get this feature turned on by default in the initial service release, but there is a bug with blocks I need to fix first as well as another optimization that will speed up the drawing of the intersection curves.

@stevebaer TestToggleTechDisplayMode:

not as spectacular as Jeff, but better: old vs new:
technical, pen, pen outline with the file posted earlier. Still in these modes this feels very laggy.

Also when rotating the viewport with the trackpad, when I give it a swing, there is a hickup after I release the trackpad. While swiping it kind of ok and after release also, but in between it stalls for a short moment.

Command: testmaxspeed

Time to regen viewport 100 times = 10.20 seconds. (9.81 FPS)
Time to regen viewport 100 times = 6.24 seconds. (16.02 FPS)
Time to regen viewport 100 times = 6.66 seconds. (15.03 FPS)

Time to regen viewport 100 times = 7.87 seconds. (12.71 FPS)
Time to regen viewport 100 times = 4.46 seconds. (22.42 FPS)
Time to regen viewport 100 times = 5.51 seconds. (18.16 FPS)