VaExportToDwg still unreliable and confusing (3.3 RC1)

VisualARQ
1

Hi all,

I switched to RC3.3 to test the current version of VaExportToDwg.

Here are a few points from the list of fixes (as written in “the list of fixes and changes” for VA releases 3.2 RC1, 3.2, and 3.3 RC1 by @enric) which do not seem to work on my side:

My test of #14522: Geometry on hidden layers is still exported to DWG. When I speak about hidden layers, I mean “Hide in detail” layers. I need to export only the geometry visible on layouts. Currently, all other geometry from the model is also included in the DWG model space.

During my tests, the detail settings are changed after export - (floor plan turned to ceiling plan), corrupting the prepared layout.

My tests:
14676: Still not working. Details with active sections get broken (in Rhino) - they turn into floor plans with the section cut active. DWG exports are bugged in the same way.
14635: Guides are exported correctly, but their linetype is lost (dashed lines turn to continuous, and so on).

14661: Section text (and section marks) was preserved only for native section styles, not for custom styles with custom block marks.

The ultimate problem is that after every VaExportToDwg, all details with regular floor plans turn into ceiling plans, and all details with active and aligned sections are turned into floor plans with active section cuts. It basically breaks all layout details.

Minor bugs: The export order does not respect the order of my layouts as seen in Rhino’s “Layouts” tab. It seems to follow only the order of layout creation, ignoring user adjustments (you can see this in the DWG below).

Here I provide all my test files and layout PDF exports from Rhino before and after VaExportToDwg, demonstrating the problems described above:

File before VaExportToDWG.3dm (6.0 MB)
Rhino Layouts before VaExportToDWG.pdf (255.1 KB)
Dwg export.dwg (2.6 MB)
File after VaExportToDWG.3dm (6.0 MB)
Rhino Layouts after VaExportToDWG.pdf (222.0 KB)

Edit: I just realised the broken detail views are not even ceiling plans. Floor plans just get mirrored around Y axis. Very strange.

1 Like
2

Same here, the exported results are turned into pieces,
these are what I got from VaExportToDwg
From viewports: (Sections wanted to be exported)

image
image542×388 6.81 KB
image
image378×423 5.86 KB
image
image518×311 7.65 KB

Exported results:

image
image1025×167 2.36 KB

All Sections.zip (12.8 MB)

and two of my original layout drawings are affected by this function and some places are wrecked:

image
image882×495 22.9 KB
image
image695×460 15.7 KB

I’m still looking forward to this feature, since this is what I can have a better and neat management to export to dwg from layout, otherwise, I’m going to only draw things in the model space.

1 Like
3

I have confirmed that ExportToDwg function is not working properly. The ExportToDwg function is a core feature of VisualArq 3. If it does not function correctly, it will cause serious issues in collaboration and make VisualArq 3 unusable in practical work. I hope for a prompt fix.
Thanks.

1 Like
4

@fsalla any thoughts on this?
Were you able to review the files I provided? I put quite some time into collecting them. :slightly_smiling_face:

VaExportToDwg is a crucial one for us, fellow architects… Is there anything else we can do to help with the troubleshooting?

Thanks in advance!

5

Hi @MichalKrizo thanks for the full report of issues related to the vaExportToDWG command, and providing the involved files. That’s very helpful!

You are right. We will fix this in the 3.3 release.

Yes, this was reported by @Steven_Kim as well. We have already fixed it and it will be available in the next 3.3 RC2.

This was fixed in other files, but I could reproduce the problem in yours. We will revise it as well.

Noted it.

I could not reproduce this issue with your file. The Section line with custom block is exported to DWG, after changing the Projection Print Width to “By Layer” or “By Object”. (Take into account that in your model you have it as “No Print”):

image
image1278×619 43 KB

As mentioned above, this has been already fixed for the 3.3 RC2.

1 Like
6

@Tanik Can you share the 3dm file as well? thanks!

7

@fsalla, No problem.
Sorry for being a bit late. I sent it via e-mail.

8

Another bug to consider, export to DWG seems to be exporting section drawings with a plan cut on, so only the bottom of the drawing is output. This is with v 3.3.0.19490

image
image1006×518 11.1 KB

9

Hi @Clayton_Muhleman thanks for reporting this error. We will revise it as well.

1 Like
10

Hi @MichalKrizo, @Steven_Kim, @Tanik we have just published VisualARQ 3.3 RC2 which fixes some of the errors reported here:

  • Objects in hidden layers are exported to DWG
  • Section is not preserved in DWG Export
  • Some texts are not exported to DWG
  • Level view is changed after exporting layout to DWG

See the complete details here: VisualARQ 3 - Version 3.3 RC2 released

Let me know if you see any other issues.

@Clayton_Muhleman the issue of the elevations exported with the cut plane on is scheduled for the 3.4 version.

1 Like
11

Hi @fsalla,

tested now on the files from the first post, everything I reported seems to be working now, even “hide in detail”, which made me very happy, thanks!

Only this one still persist:

I will test it all again on a real project and write about new findings, if any.

Thanks a lot!

1 Like
12

Hi, @fsalla
This is the exported file from the same model I sent to you,
All Sections.dwg (6.8 MB)

The spotted problems:
●The drawings are repeated in 3 times, and some redundancy of others.
●The hatch pattern scale remains as in the model space and the dimensions and other drawings are not exported from the layout.
●The hatch patterns are exploded into curves, which would be nicer if it remains hatch type.
●Hope the segments from the same object can be auto-joined.
●The layer of some curves from the corresponding object is misplaced, for example, the Beam’s curves are in Slab layer.
Thank you. Hope you are doing great.

13

Hi @Tanik can you send me the 3dm file that generated that DWG again? I’ll revise these problems.

14

Hi, @fsalla The file is sent, please let me know if you don’t receive it.

15

Hi @Tanik I haven’t received it. Have you sent it to visualarq@asuni.com?

16

@fsalla yes, please check it again.

17

Hi @Tanik we haven’t received it yet. Please try to send it to my email as well (fsalla@asuni.com)

1 Like