Really odd issue, I sometimes have issues with printing the arrows of dimensions:
On the left is a PDF printed with CutePDF and on the right is the same print but with RhinoPDF.
I’m almost positive that it has something to do with my annotation definition, but I can’t really figure out what it is.
Arrows.3dm (88.6 KB)
You may want to try the SR12 release candidate. There have been several PDF related bug fixes in SR12 and one may address this issue.
Rhino 6 SR12 Release Candidate 1 (6.12.18345) is now available.
To get it,
subscribe to the Release Candidate update stream .
File IO: System.NullReferenceException: System.Windows.Forms.TreeView.CustomDraw (Message& m) ( RH-49784)
Camera: Camera rotation centering ( RH-49770)
DevLoft: RhDevelopableSurface::UntwistSurface() returns false when input rulings are already perfect ( RH-49730)
Draw order incorrect ( RH-48757)
Lag with select/unselect ( RH-49812)
Sadly no dice:
Have you tried printing the attached file? This is an issue that I’m only seeing on some files, but on multiple machines, perhaps there’s some sort of tolerance or similar setting that makes this odd? Here’s the sysinfo on the machine that printed this last one:
Rhino 6 SR12 2019-1-16 (Rhino 6, 6.12.19016.7051, Git hash:master @ 41024cebfe6efcf880592c90e5204f46556bf4ed)
License type: Educational, build 2019-01-16
Windows 10.0 SR0.0 or greater (Physical RAM: 32Gb)
Machine name: DESKTOP-V3CT79H
Primary display and OpenGL: NVIDIA GeForce GTX 1080 Ti (NVidia) Memory: 11GB, Driver date: 11-29-2018 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 417.22
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 11-29-2018
Driver Version: 22.214.171.1242
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB
C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 6\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 6\Plug-ins\RPC.rhp “RPC”
C:\Users\hbxma\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\ColorPicker (336da4ab-03d3-42ca-b1fb-313bfd4c1157)\2018.2.5.819\ColorPicker.rhp “ColorPicker”
C:\Program Files\Rhino 6\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 6\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 6\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 6\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 6\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Users\hbxma\AppData\Local\Enscape\Bin64\Enscape.Rhino6.Plugin.dll “Enscape.Rhino.Plugin” 2.4.18320.832
C:\Program Files\Rhino 6\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\export_PDF.rhp “PDF Export” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 6\Plug-ins\BlockEdit.rhp “BlockEdit” 6.12.19016.7051
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”
Works here in the latest ‘in house’ SR13. I’ll try 12…
OK in 12, here.
Both pdf’s were created from the same file(Attached) but the left one was printed from model space and the right one was printed from the layout(the two dimensions to the right are on the layout page itself)
Arrows2.3dm (89.1 KB)
Hello - does the preview in the print dialog also show no arrows?
No the arrows show up in the Print Dialog:
I Attached the file from that print:
And, does a print to raster work?
Hi - I’m seeing this as well here.
If I start Rhino in Safe Mode and make sure Tibidabo isn’t loaded when I open the file, printing to PDF does have the arrows included.
@enric, could you take a look at this one?
I’ve been able to reproduce the issue. The problem is that VisualARQ uses a conduit to drawn only the visible parts of objects. When we draw a filled polygon (like a solid hatch or the end triangle of an arrow), we call directly the
DrawPolygon method from GDI, which completely bypasses the
RhinoPDF printer, which is not really a printer. We’re calling GDI because when the polygon has a void, we call
PolyPolygon instead. This feature is not supported in the Rhino pipeline of RhinoPDF.
I’ve already a working solution: generate a closed polygon with voids with just a single boundary, by connecting all boundaries between them.
I’ll do my best to include it in VisualARQ 2.4, targeted for this next Wednesday.
I forgot to mention that this issue only happens when you try to print in vector mode a viewport that uses the “Hidden” display mode, that is added by VisualARQ.
If you change the viewport to “Wireframe”, use “Raster output” mode, or use a real PDF printer, like CutePDF, you’ll not see the error.
@rheinason, the bug that was preventing from printing the dimensions arrowhead to vector output has been fixed in VisualARQ 2.5: VisualARQ 2 - Version 2.5 released