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:
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)
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.
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.