Hi all,
Thanks for bringing this discussion into this public forum. We are following it up with big interest, and it will contribute for sure to the future development of VisualARQ.
You can use IFC for that. Some Revit families will be identified as VisualARQ object styles when you export them from Revit to Rhino through IFC. This will depend on the object type or how the object is created, since each object is created with different parameters in each program, and it is not always possible to preserve their parametric properties when they travel through IFC. When it is not possible o preserve that, the objects are exported/imported as geometry with data, and tagged with the corresponding IFC type. This IFC guide from VA to Revit adds some more details about this workflow.
I donât see this reverse-engineer miracle happening either. We rely on IFC to bring 3d models with data from these public libraries into Rhino, which depending on how they are created, can be identified as VisualARQ object types and styles, or just objects with data.
BUT. When printing to pdf. vector output does not work. So I proceeded to use raster, BUT when exporting a small groundplan, few random bugs started to occur - missing opening lines of some doors, missing random texts from annotationsâŚ
To overcome this problem and to make vector output possible, i tried to create a copy of Hidden display mode (VA native). But found out it has no âclipping planesâ - âsolid colorâ - âblackâ option!:
hi! thanks for sharing this. now that VA3 is out, I canât seem to replicate this option because the clipping plane customization doesnât have the solid fill option anymore (R8).
has anyone managed to successfully implement a workaround for LODs in drawings? I am trying to complete a drawing set in VA but thereâs a significant learning curve.
It will require some time to match your own workflow, but in our practice it works quite well to quickly modify section attributes on a whole model to print it at different scales. It works with both VisualArq and Rhino objects.
It is a workaround, and weâre currently working on a new version of it that should work with the native SectionTools in Rhino 8.
Since this post is being mentioned from other posts, Iâm just updating the link to the documentation. It is now available at this address: vaSetSectionAttributes