Thanks to all of you that explained the problem.
Printing to vector is a must have if Rhino aspires to be a professional software rather than a tool for hobbysts. I hope it will happen very soon!
@wim: Can we expect to have it solved inthe next release (SR10)?
@wim Greatly appreciate your attention to this issue.
We’ve seen multiple updates since April, some have opened up new issues which I post in a different thread, but namely we have not seen the vector printing issue resolved yet.
Do you have a timeline on a solution to this critical problem? Printing vector is a core component to our business model, and we’ve been jumping through hoops since January.
3 Likes
Seconded, it’s been a while since I’ve seen any movement on this outside discussion on this forum. The issue tracker links show this has been gathering cobwebs for 7 months now.
I understand development takes time and there are issues on multiple fronts with any product, but if you’ll please forgive me being a squeaky wheel and have a look it soon. I have a team of only 5, but all of us are using a workaround to deal with this and raster just doesn’t looks as professional as vector. This affects our primary product as a drafting service.
As before, I’d happily work with whoever gets assigned to the task as a free tester.
6 Likes
@wortley.jb is there a specific issue that you are most interested in getting fixed right away? There are several different bug reports in this thread and it is getting difficult to tell what people are referring to.
Hi @stevebaer,
These issues all seem pretty related to each other. The main thing I want is for vector printing to work for blocks and nested blocks without lines going missing or planes being see-through randomly on complex shapes and curves. I believe the main issue tracker for this is RH-79540
If we can get that, vector is back on the table for us!
If Santa was coming to town for this request, it would be nice if vector mode objects also properly obscured textures and images behind them, as described here:
Hi Steve,
Just installed the newest update (Version 8 SR11 (8.11.24240.13481, 2024-08-27) Commercial) and I’d like to report that the major issue of certain round geometry/complex geometry failing to print in non-wireframe vector still persists.
@rrom I can’t tell what the problem is based solely on this image. Would it be possible to provide a small sample file?
Hi Steve,
Sorry for the delayed reply. I’ve complied a small example that hopefully will give you some insight to what is happening. We’ve done a few tests and somewhat honed in certain geometry seemingly causing the issue.
ERROR REPORT PDF EXAMPLE - VECTOR PRINTING ISSUE 1.pdf (711.4 KB)
ERROR REPORT - VECTOR PRINTING EXAMPLE 1.3dm (579.5 KB)
I’ve put together an example file for you that shows 2 blocks we use, one that prints correctly and one that does not (Ledger A and Ledger C, respectively). Ledger B is a rebuild of Ledger C that does print correctly. While we know this could possibly be a solution, our library of blocks is immense and a complete rebuild would be impossible.
Please let me know if there is anything else I can provide to help drill down further on this problem.
hi @rrom ,
thanks for sending the file. In the file you sent however, I don’t see a layout that represents what you are showing in the pdf.
If you are using any modified display modes, pls also provide these (.ini)
That being said, if I create a similar page in either Technical or Pen view, I see some issues. They don’t seem to be related to blocks though, because after exploding the blocks the print issues persist.
Thank you @Gijs ,
Rom is using my modified display mode template. Please see the linked file as requested:
WD_Drafting.ini (14.1 KB)
It is just a modified version of Pen from memory, (or maybe technical? it’s been a while) - either way, they should behave the same as those.
hi @wortley.jb after further investigation, I believe this to be a meshing issue rather than a vector/block print issue. If you increase the mesh settings (Slider all the way to the right > More polygons) does it then print correctly for you?
Thank you @Gijs!
Your solution worked. I would not have thought a model’s render mesh option would affect printing. Good to know.
For reference, I isolated the culprit:
For those who are new to the issue and want to know:
Turning off simple planes fixes the remaining issues with lines not printing right.
If we can fix clipping sections, images etc showing through the vectors (think there might be a masking plane missing from these or something) then vector print is fully functional. It looks stellar and we are so close now!
Here is a test file outlining the remaining issues:
ERROR REPORT - VECTOR PRINTING EXAMPLE 2.3dm (925.1 KB)
I have tried a bunch of settings, but what’s on the sheet never gets properly reflected on the drawings:
We can probably close out the other issues now. The only one remaining is this one: RH-81588
Actually, that one covers half the issue. The other half of the issue is that clipping sections masking background planes are not applied and the two might not be related?
Neither did I, and I would not like to call it a solution. I just wanted to make clear the issue is not a block issue and that some meshes are not interpreted well by the Fake2D process.
RH-83747 Mesh settings affect the correctness of Vector output
As for the other issue, where the ‘fill’ is missing in Vector:
RH-83748 Print to vector supporting object masks
1 Like
Thank @Gijs
Also in that example, any idea why the perspective view wouldn’t show the image’s texture on print?
not supported in the current way Vector output is generated, see RH-62120 Print: Vector output does not print Pictures in Wireframe perspective views
1 Like
Interesting. Would be really nice if that worked too but I’d honestly already be over the moon with just getting 2D vector. Thanks for looking at all these for me.
I too am having problems with Vector print in R8,I had to resave to V7 and it prints fine,I have wasted hours looking for dodgy geometry,But it appears it’s probably a bug…
Rhino 8 SR11 2024-9-10 (Rhino 8, 8.11.24254.15001, Git hash:master @ d3c11108eae09fadc146928ba51b9b182a05303f)
License type: Commercial, build 2024-09-10
License details: Cloud Zoo
Windows 11 (10.0.22000 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.20
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3070 (NVidia) Memory: 8GB, Driver date: 9-5-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 561.09
> Accelerated graphics device with 4 adapter port(s)
- Secondary monitor attached to adapter port #0
- Windows Main Display attached to adapter port #1
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: 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: 9-5-2024
Driver Version: 32.0.15.6109
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.11.24254.15001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.11.24254.15001
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.11.24254.15001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.11.24254.15001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.11.24254.15001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.11.24254.15001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
Hi Jason -
Can you post or upload a file that does not behave?
There is a test command in Rhino 8 that disables vector printing from details in a technical display mode, thus making Rhino 8 behave like Rhino 7. When all else fails, that could be a way out, but it might not help making this work better in the future. → TestToggleTechnicalVectorOutput
-wim
I will try that,Thanks Wim
This drawing is under an NDA so i can’t share it.