Technical layout detail not rendering, or printing, properly with clipping planes


(Tim Gift) #1

A have a model with a several clipping planes which are active in different details on a layout page. The details are rendering using the Technical display mode. Though this problem also happens in Artistic and Pen modes. When viewing the layout page, it appears like all the edges generated by the clipping plane are not always being rendered.

Sometimes panning, zooming, or activating another detail, will cause one detail to refresh and the lines will appear, rendering correctly, but then the next detail will render incorrectly.

This incorrect rendering is reflected in the printing output. Even if I get the layout page to refresh and look correct, the printed output (to PDF) is always wrong, missing lines.

Detail%202 Detail%201


#2

Hi Tim,
I’ve encountered similar issues in the last few weeks.
It was only with shaded views, and custom variations of shaded views

I’ve found no systematical workaround, and just like you panning, zooming and activating other details sometimes works.
Another trick that works about 80% of the time is to enable the problematic detail, select all and refresh shade, exit the detail, print.

In one of my layout with 6 details I just could not get all of 6 looking properly at the same time.
I needed to put 1 of the 6 details on another layout, then merge the 2 pdf with Indesign.

I’ve also found that I often needed to explode block to get proper clipping plane edges.

One weird thing is that often, the ‘printing panel’ thumbnail looks just fine, but the outputted pdf doesn’t.
It is true in either raster or vector mode.

Rhino 5.4.2
MacOS 10.13.6


(Tim Gift) #3

Sounds like the same problem. I thought it was related to the edge views, but obviously not. It would be nice if McNeel would give us a better handle on the problem and a more consistent work-around. I’m also on Rhino 5.4.2.


#4

Is there no one else than me and Tim that experiences such issues?
As of last week I still unfortunately encounter theses nearly daily.


(Tim Gift) #5

Still running into it myself. Just refunded my Rhino 5, bought a 6 license, obtained a legacy key for my 5 installation, will get a windows box for 6 and print from there. If I wasn’t in pressed for time, I’d wait for a fix, but things don’t seem to be moving very fast. When I talked to sales about the refund, they said they pinged one of the tech guys about this issue, but no response.

I actually ran into a number of issues with the clipping planes and the layout view. Detail’s not showing up in the plane property panels, details names incorrect, etc. Exiting a reloading seems to fix those, but the edge issue is persistent.

I’m new to Rhino, so I’m not sure things normally flow here, but so far I’m not impressed.


(Tim Gift) #6

Got my windows box up and running and Rhino 6 installed, and unfortunately the same issue.


(jesterKing) #7

@stevebaer clippingplanes and printing troubles, you might want to take a look.


(Steve Baer) #8

Hi Tom,
If you have a file we can see that repeats this issue, we would appreciate it if you can share it with us. I can’t figure out how to repeat this issue.


(Tim Gift) #9

I email a dropbox link to the tech@mcneel address. Also sent an email with a list of other issues, which could be related to this file.


(Tim Gift) #10

This file… If I just open with Mac Rhino 5.4.2 and then open the layout window, several of the details will be missing clipped edges. Press print, and edges missing. If I pan/zoom I can get them to appear.

Bug1.3dm (2.7 MB)


(Dan Belcher) #11

@stevebaer Is this something you can reproduce on your end?


(Steve Baer) #12

Jeff and I just fixed some clipping plane issues in the last couple weeks that sound related to this. I would suggest trying the latest WIP build from this week.


(Dan Belcher) #13

Hi @tim.gift-

Can you please test out the latest RhinoWIP for Rhino 6 for Mac and see if you can reproduce this issue there? We might have fixed this.

Thanks in advance.


(Tim Gift) #14

Definitely some odd clipping going on now. Is there anything I need to “reset” when I load the file? These are screenshots with WIP (6.12.18324.12016, 2018-11-20)

An on the layouts:


(Dan Belcher) #15

Thanks for testing that in the RhinoWIP, @tim.gift. Next, can you please run _SystemInfo (in the RhinoWIP) and copy the report back into a reply here?


(Tim Gift) #16

Rhino 6 SR12 2018-11-20 (Public Build, 6.12.18324.12016, Git hash:master @ 7f7fefb5133293bd18d1eae5c5d426e53e00f502)

License type: Beta, build 2018-11-20

License details: Cloud Zoo. In use by: Tim ()

Expires on: 2019-01-04

Apple Intel 64-bit macOS Version 10.13.6 (Build 17G3025) (Physical RAM: 8Gb)

Mac Model Identifier: MacBookPro8,2

Machine name: Tim’s MacBook Pro (2)

Language: en-US (MacOS default)

AMD Radeon HD 6770M 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: 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: 1 GB

Graphics: AMD Radeon HD 6770M

Displays: Color LCD (129dpi 1x)

Screen size: 1680 x 1050

USB devices

Apple Inc.: FaceTime HD Camera (Built-in)

Apple Inc.: Apple Internal Keyboard / Trackpad

Apple Inc.: Bluetooth USB Host Controller

Apple Computer, Inc.: IR Receiver

Bluetooth devices

None

Third party kernel extensions

at.obdev.nke.LittleSnitch (5207) 9FEE069A-6B44-395D-B154-411C856CB951

com.dvdfab.kext.fabio (1) no UUID

Third party plugins

None

Rhino plugins

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/RhinoBonusTools.rhp “Rhino Bonus Tools” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/Alerter.rhp “Alerter” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/NamedPositions.rhp “Named Position” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/BlockEdit.rhp “BlockEdit” 6.12.18324.12016

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 5.1.2015.132

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 6.12.18324.12016

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 6.12.18324.12016

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 6.12.18324.12016

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/Displacement.rhp “Displacement” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/PlugIns/RhinoRender.rhp “Rhino Render” 6.12.18324.1002

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 6.12.18324.12016

/Users/timgift/Applications/Modelling/RhinoWIP.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 6.12.18324.1002


(Tim Gift) #17

I tested on a new MacBook with a Radeon Vega chip set. The 5.5 version continues to exhibit the same problems, but the version 6 WIP does not. So the issue appears to be fixed with the Radeon drivers.

A side note, on the new MacBook ,the WIP was rendering much faster than 5.5 in the normal 3d view, but was extremely slow in the layout view. A lot slower than 5.5, so something going on there.