I’m encountering some issues when printing in vector using Technical display mode. Here is the raster output, which has correct hatching and colors:
And here is the vector output:
All of the visible model geometry is inside a single block. Annotations are not. I get similar glitches (but worse) when the block is exploded.
Any ideas for a fix? I can DM the Rhino file to a McNeel employee if someone wants to take a look.
Bump. I have about 2 weeks until this goes out for bid and I start getting complaints from contractors because they can’t read fuzzy rasterized annotations.
Hi Brayton_Orchard,
I’m not seeing a similar bug report.
Please run SystemInfo in your Rhino command line and post the result.
You can upload an example file here and add a link to this thread in the comments, once we can repeat we’ll get a report going. Thanks
Thank you for responding. Here’s my system info below. I’ve uploaded my Rhino file to the link you provided.
Rhino 8 SR15 2024-12-17 (Rhino 8, 8.15.24352.13001
License type: Commercial, build 2024-12-17
License details: Cloud Zoo
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 64GB)
.NET Framework 4.8.9290.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2080 Ti (NVidia) Memory: 11GB, Driver date: 8-14-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 560.94
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 8-14-2024
Driver Version: 32.0.15.6094
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB
Rhino plugins that do not ship with Rhino
C:\ProgramData\McNeel\Rhinoceros\8.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino8.rhp “Datasmith Exporter” 5.4.2.0
D:\Life\5Work\Tools\Rhino\blockeditnew20230622\BlockEditNew.rhp “BlockEdit” 1.0.0.0
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 8\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\export_PDF.rhp “PDF Export” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.15.24352.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”
Thanks, I’m seeing this as well.
Here is the public portion of the youtrack you can follow along. RH-85392
Great, thanks!
Please also note that in addition to the hatch bleeding, when vector printing the clipped surface edges are not respecting the section style I’ve applied (black for new, gray for existing), but appear to be defaulting to per-object color.
Hi again Japhy, I reeaallly need this to work asap, but am not seeing anything happening on the Youtrack issue. I’m happy to test solutions directly if that would help.
Hi -
In the detail that you show a screenshot of in this thread, you have two clipping planes that are active. One of those is sitting in the outer wall and you are seeing the openings in that front facade in the output of the vector mode. Disabling that clipping plane should make that go away.
Also, changing the section style from solid to a hatch pattern makes that go away.
-wim
reminds me of this:
not sure if related or if corrected. last time I checked it was an old bug that was continuing to persist at the time.
I’ll be picking up on some projects soon and potentially test this stuff some more.
It’s not.
my mistake. it must be completely unrelated.
someday maybe I’ll figure out the difference. maybe it’s hatch vs no hatch or block vs no block.
Thank you Wim, I deleted all but my main clipping plane and that appears to have fixed the hatch bleed issue for now.
However, I’m still getting per-object-color lines on top of my section-styled lines.
Also I have a hatch object in the model to indicate flooring which you can see has disappeared in the vector version (parallel vertical lines). That hatch is inside the main block for the model, and if I BlockEdit, and then vector print, it will reappear.
Raster version (correct):
Vector version (incorrect):
The incorrectly colored lines on top of the section styled lines are easier to see in this image:
Notice the detail on the corners is not correct.
Seems like this bug has been ongoing for a while.
I’ve yet to verify. maybe I’m still wrong about how similar it is to an old scenario.
Soon I’ll test this again.
It’s clearly a thickness issue and the characteristics of the hidden line pattern options etc. or lack thereof.
The fun part is when the print that comes out in the real world provides yet another permutation.
I’d be interesting in seeing images of samples if possible.
It might be worth testing dpi:
I think my previous work around was printing to pdf to mitigate the issue:
Someday I hope hidden lines have more options.
@japhy or @wim I still really really need the section line color and vector hatch-object display fixed asap 
. (Note the vector hatch object disappearing (which I believe is draw-order related) is a different issue than the hatch bleed).
Happy to provide more info or testing if needed.
We hear you, the youtrack is flagged as Major and is getting attention. I’ll let you know as soon as there is a build we can test.
Okay, thank you, much appreciated!
Hi Brayton -
I’ve put this issue on the list as RH-85632 Print: Fake2D Does Not Output Hatch in Block
Note that, from that test, it looks like when you bring the objects closer to the world origin, this issue goes away. FWIW, in your file, you have the same block definition placed very many times around the scene, with the purpose, it seems, to have a separate instance for every detail/layout in the file. It seems to me that it should be able to use a single instance for all details/layouts?
I’ve put this one on the list as RH-85633 Print: Fake2D Clipped Edge Gets Layer/Object Color
-wim
Thanks Wim for the issue logging.
Noted on the distance from origin bit.
I have previously set up my files in the way you described, with a single ‘instance’ of the model (not in a block), with clipping planes, named views aligned to clipping planes, cplanes, and corresponding detail views. This works, but you have to duplicate any layers used for 2D annotations or linework for every drawing produced, since all the linework is at the same model location and needs visibility control. Tracking changes between all those layers, switching between visibility settings in details, turning clipping planes on and off, trying to copy linework between cplanes of a different orientation–all possible, but a huge mental load to use in practice.
I’ve found a single clipping plane for world top view and using block instances of the main model allows for very intuitive spatial creation and organization of drawings that is easier to handle mentally. For sure there are some downsides to working with blocks though.
Maybe there is a better workflow you know about? Would love to hear about it if so. (Clipping drawings comes to mind, but to my knowledge that carries similar issues to the first method I described (esp. layer duplication)).
