Hi. I am able to see the the detail view drawing inside the layout space but once plotted, the drawing is missing in the pdf print. Also, there are artefact on the reflected bottom of beams:
layout space:
pdf export:
thanks in advanced for the advice/help
I’ve experienced the same thing with RCPs recently. The planview for RCPs works correctly. But the live view isn’t printing.
Hi @gianfrancogalagar can you share that model so we make sure we fix this issue?
Hi, sorry for the delayed response @fsalla
Here is the model for your inspection.
Cheers
202_Troubleshoot.zip (14.6 MB)
Thanks @gianfrancogalagar, I’ll let you know when we fix this problem!
@fsalla any update on this issue? It’s a real pain to not print from the live rcp view.
thanks
@arcus have you tried it again with the 3.3 RC2 version? (VisualARQ 3 - Version 3.3 RC2 released)
Still seems to be an issue. This test was made built on the visualarq foot template.
Here is the view on rhino vs the pdf it prints.
Hi @arcus thanks for the files. We will revise this asap.
I noticed that this issue only occurs when printing vector files under the RCP view. The occlusion calculation for objects, which should be processed from bottom to top (level 0 to level n) during vectorization, instead reverses to top to bottom (level n to level 0). I’m unsure whether this is a problem with ARQ or Rhino’s RCP view.
Hi @slodka we are still revising this issue. If you want to provide an example, we will use it as well to test that everything works well once this is fixed.
This example clearly shows the issue. When using the hidden display mode, errors occur when printing vector drawings—the beam at the bottom layer appears at the top, whereas printing raster drawings is correct.
Hi @slodka thanks for the file. We will revise all these errors when printing the RCP to vector output. I’ll get back to you when we fix them.
Nice
Jumping in, I’ve also got some plot issues for RCPs.
Should be:
I’ll message a file. Thanks as always! -C
Hi @slodka @Clayton_Muhleman @gianfrancogalagar @arcus
I’m glad to inform you this issue have been solved in VisualARQ 3 - Version 3.6 RC1 released, which is already available to download: VisualARQ 3 - Version 3.6 RC1 released
Best,
Melissa
