Lots of artifacts everywhere in Mac WIP


No idea what is up. Just installed the WIP. Ran V5.5 first as suggested. Restarted a couple of times. An oldy but goody Mac Mini Mid-2011, 2.5 GHZ, with 16 GB Ram, AMD Radeon HD 6630M 256 MB, latest High Sierra, and SSD drive. Are there any minimum requirements?


Well. I have installed Rhino 6 for Mac WIP on my 2013 MacBook Pro with an NVIDIA GT 650M and am not experiencing the same artifacts. So at least for me it is computer specific. Anyone have any ideas how I can work around this for my mac mini? Thanks.

(John Brock) #3

Please run the Rhino V6 “SystemInfo” command and post the results, or send them to tech@mcneel.com with a reference to this Discourse message thread: Lots of artifacts everywhere in Mac WIP


John, thanks for the reply. Here are the results of SystemInfo:

Rhino 6 SR11 2018-10-2 (Public Build, 6.11.18275.12016, Git hash:master @ d78712fd9dafadb872ea02627ab9759113ea6615)
Licence type: Beta, build 2018-10-02
License details: Cloud Zoo. In use by: Carter ()
Expires on: 2018-11-16

Apple Intel 64-bit macOS Version 10.13.6 (Build 17G65) (Physical RAM: 16Gb)
Machine name: Carter’s Mac Mini

AMD Radeon HD 6630M OpenGL Engine (OpenGL ver:4.1 ATI-1.68.20)

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

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

Vendor Name: ATI Technologies Inc.
Render version: 4.1
Shading Language: 4.10
Driver Date: (null)
Driver Version: (null)
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 256 MB

/Applications/RhinoWIP.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 6.11.18275.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 5.1.2015.132
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 6.11.18275.12016
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 6.11.18275.12016
/Applications/RhinoWIP.app/Contents/PlugIns/Alerter.rhp “Alerter” 6.11.18275.1002
/Applications/RhinoWIP.app/Contents/PlugIns/Displacement.rhp “Displacement” 6.11.18275.1002
/Applications/RhinoWIP.app/Contents/PlugIns/RhinoRender.rhp “Rhino Render” 6.11.18275.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 6.11.18275.12016
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 6.11.18275.12016
/Applications/RhinoWIP.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 6.11.18275.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 6.11.18275.1002

(Steve Baer) #7

This looks like a driver bug for one of the OpenGL shaders that we use to draw geometry. Do you see artifacts on the screen when there is no geometry at all in the model?


Yes. Even with a brand new file and zero geometry there are artifacts with the grid, and both the xyz and the origin indicators(first image). Also when dragging a selection(second image).

(Steve Baer) #12

This means that the OpenGL driver on this computer has a bug with respect to our shader for drawing lines on the screen. It would be interesting to see if an update to mojave fixes this driver bug. If it doesn’t, we would have to report this to Apple.


Currently Apple is not supporting a mid-2011 mac mini for updating to Mojave.

(Steve Baer) #14

I’m not too sure what we are going to be able to do about this. We might not be able to support this model either then. We may eventually get enough “legacy” shader support or work arounds in place to support this system, but if the basic wire drawing shader is failing then I would suspect a lot of other display problems are going to pop up with fancier display modes.


I guess time moves forward and the old stuff gets obsolete. Just disappointing that a 2.5ghz core i5, 500GB SSD, with a dedicated graphics card is obsolete at 7 years old. Definitely not on you guys, but on Apple. Apple hasn’t even updated the Mac Mini in four years and now one just a generation or two old gets kicked out the back. Blah.

(Steve Baer) #16

I agree, but I also don’t know how we would work around a bug like this in the driver. I’m sure we could eventually get this to work, but the man hours alone just to work around something like this would be massive.