All in All I think the VaPlanviews are great - but they still need some improvement.
In this thread I want to talk about some problems I found, with no particular order.
All of those issues, can be verified with the attached rhino model, if you use blockeditnew, you can still open visualarq elements, blocks, planviews and look at their properties (please don’t patch this out, being able to alter those, even if they reset after a vaUpdate is a nice-to-have)
vaGuides, lose their layer when “backed” into a visulaarq planview thus, all properties set to “bylayer” get lost and we are left with a few lines and text sitting on default-layer
Spaces get converted to hatches when performing planviews - but some spaces/hatches, just dont make it - I believe this could be a tolerance issue / bad object issue - but most of the hatches created for visualarq walls are bad object and still print / export fine. spaces/hatches on the other hand, often get lost and dont show up in the planview and / or some hatches get exploded into linework. (the explosion into linework is not in this model, but I encountered this quite often)
some lines inside the planview block get funky scalings, I cant get my head arround it why this happens - I normally reset those with a simple script, but I don’t think there is a need for these linetypescaling at all, and if you dont know this, it makes exporting those files cumbersome. (sometimes I even find NaN as a scaling value, which is not good)
4)Sometimes lines get mixed / messed up, for example I had cases (not sure if its in this testfile) where the leaf of the same door which is used several times, has different properties in vaplanview that the others, altought in 3d space its exactly the same door
Best regards,
SeboWim
PS: In addition, lately I get a lot of bad objects, maybe some of those errors are bc. of those - I am unsure why this happens and what I could do against it.
Hi @Sebastian_Wimmer I could reproduce the issues 1, #2, and #3. I’ve reported them to the development team, and get back to you when they are fixed.
Regarding the #4, I suspect that the lines that are mixed up correspond to the overhead representation of the door, whose 2D lines get the attributes of the “overhead display attributes”, (in the Document Properties > VisualARQ).
If there is no need to show the overhead representation of the door, you can turn it off from the door properties > Display > Plan Visibility (and change it to “Projection”)
By the way, I’ve noticed that some door styles have a frame of 1mm width. I’d rather delete that Frame component than having one that small (almost inexistent).
Also, I may have asked this before, but what is the reason why you are generating 2D plan views, instead of showing real-time plan views in page layout?
the door style is a workarround - most of the time I just need the doors as simple linework, you are right - I could get rid of the 1mm frame. This is just because I us “openings” with the 1mm frame (which unfortunately is mandatory to use, and using va_openings is not very usefull because converting them in a later stage to doors is cumbersome) and thus also inherited the 1mm frame into the door → when I feel like I need a door at a certain stage
I am generating 2D Plan views for numerous reasons: 1) exporting them as .dwg 2) being able to alter them in 2D (explode or change stuff with blockeditnew) 3) having clean linework: printing a real-time plan always introduces unclean linework, thats not a big deal if you print bus using this for a presentation where you have a beamer and zooming in you can tell very fast. 4) there might be more that I dont think of right now.
Keep in mind that this new update won’t fix the objects that already got those wrong values (you can edit them manually), but this problem should not happen again.
