@fsalla Hi, yeah, I forgot the big detail that I aligned with the border, even though it is empty, it still prints all of the section views.
And I hided all the curves and sections in the model, it did help, thank you.
Btw, I guess the hatch pattern scale is something related to Rhino8, as this thread pointed out, and just makes it clearer:
@Clayton_Muhleman We have fixed this error in VisualARQ 3.4 RC1: VisualARQ 3 - Version 3.4 RC1 released
Hi @Tanik I let you know we have fixed this issue in the DWG export in the VisualARQ 3.4 RC1 version that you can download here: VisualARQ 3 - Version 3.4 RC1 released
Hi @Tanik I let you know that we have fixed this issue in VisualARQ 3.5 rc1 update, available here: VisualARQ 3 - Version 3.5 RC1 released
Now, unless the hatches are partially occluded by other objects, they will be kept as hatches in the DWG export, and not exploded into curves as before.
This also applies to space hatches, or patterns assigned as section styles to objects displayed in section.
Just confirming this one’s solved. Haven’t seen it pop up since I installed the latest patch. Thanks again!
I’m loving the idea of the VaExportToDwg, but am having some issues with the scale and drawing location.
When I export an imperial scaled file is appears to come in at the wrong scale. See below and attached.
Also, is there any way to control the spacing between drawings in the model space? I’d love to be able to space them, say, 100 or 200 feet apart consistently every time. This can become somewhat tedious if there are lots of plans, elevations, and sections all spaced about 1000 feet apart.
DWGexportscaletest.dwg (1.9 MB)
thanks,
Thomas
Hi Thomas,
Can you share that file?
Not right now. We may add an option in the DWG Export options to control that distance, in future versions.
Sure thing. See attached.
You’ll also notice that in addition to the scale being inches instead of feet in the dwg, the height of the levels is not consistent from reference to reference. This could cause confusion for consultants. I’ve included a screen shot below of what my ideal is when sending to consultants, with each plan spaced consistently and aligned as well as each section and elevation space consistently and aligned.
I’ve also included a rhino file of the dwg exports aligned in a way (old school drafting style) where the plans are at their relative heights and the elevations and sections are spaced equal distances from the plan and aligned to the plan. This makes it a little harder to compare one elevation to another, but easier to check alignments with the plans and from one plan to another.
I personally don’t have a preference one way or the other. Though the aligned method may be harder to set up for larger and larger projects, but easier for consultants to work with.
251201_DWGExportTest.zip (8.7 MB)
Hi @arcus thanks for the file.
I can see the text in the dimensions change format, so we will revise this to find a solution.
We will also study if it is feasible to export the views to DWG in a more ordered way (aligning elevation/section views by their elevation, or plan views from a reference point), and providing export options to setup the spacing between 2D drawings.
@arcus Developers have figure out that the problem with the imperial dimensions changing format is caused by a bug in Rhino.
Simply save the document as DWG (with VisualARQ unloaded), open the resulting DWG, and you will see the dimensions are also wrong. I’ve reported it already : https://mcneel.myjetbrains.com/youtrack/issue/RH-90804/Imperial-dimensions-change-format-when-saving-file-to-DWG
Ok thank you, hopefully McNeel will fix it on their end.


