Hello!
Just messing around a bit with VA3…
I’ve placed the dimensions on top of the Detail (where they belong). Those measurements can’t be right, can they.
test export DWG.3dm (3.6 MB)
Thanks!
Here we go again:
After vaExportToDWG command (nothing else), annotations are broken.
You must understand, things like this are the reason why Rhino+VA cannot yet be taken seriously as a reliable BIM solution. As much as I hate to say this!
I know, messed up layout annotations are a bug (also) on McNeel’s side, but this needs fixing.
We could debate (again) if annotations should sit in model or layout space - or some yet non-existing 2d space inbetween, which would be the best idea.
The ideal approach, as I see it, is to keep the model space clean of any 2d elements, because they get in the way, and thus layout space (or another new 2d space) should be used for it.
I’m used to Archicad since a while now, and I can tell you, all these layout related things work flawlessly there. Create parts in 3D space, annotate/hatch etc. in automatic 2D spaces (floorplans, sections), put these 2D drawings in layouts, then publish the layouts in any combination.
Ok. it was optimized around this workflow right from the beginning. Rhino users, though, are still forced to complicated workarounds and shortcomings. The system has become convoluted and lacks a clear ‘vision’.
I see how much good ideas and efforts you put into VA3, and I salute you for that, but it’s disappointing to see that the Rhino8 / VA3 combo still suffers from these same old problems.
Thanks!
3 Likes
this is really awkard. to me it seems like there was no testing because these are obvious errors.
on special 2d space: microstation has it. model space - drawing space - layout space. model geometry drawing dimensions layout is just composition of more frawings plus notes
Great concepts and creativity but ya… If it doesn’t work it doesn’t work. They really need to hammer down.
I tried it out recently. I don’t think it’s weeks away from release. More like months.
Even with the added benefit of having us (well mostly you guys, and thank-you!!), the bugs aren’t being worked out. The approach to fixing them isn’t working. I think it’s a matter of having their resources stretched too thin.
1 Like
I’m wondering how have you created those dimensions. I can’t reproduce that issue:
I could reproduce this one. I think this error might be related to another one you reported here: Dimension Shift With Detail Window Activation/Deactivation - #19 by Eugen
But I can’t confirm it. We will revise it.
I totally understand.
1 Like
I was simply using the DimAligned command.
Wait… I have written my own CreateSimilar command, which copies the properties of the source object. Will ckeck if that has anything to do.
Ok, found the reason for the wrong annotations (initial topic).
In layout space, when a Dim command is run and geometry (from the Detail below) is picked, the measurement will be correctly in model units. When an existing dimension point is picked, Rhino thinks you want to annotate in layout space, and uses layout units.
Although this is kind of logical, it can be quite confusing from a user’s perspective. Who would ever want to mix model and layout units in an annotation chain?
→ Wish: in layout space, when another annotation control point is picked in an annotation command, the annotation should connect to the target of the existing point, not the the point itself.
Hope this makes sense.
Thanks!
Hi Eugen -
Is this something that you can reproduce from scratch in Rhino without running any plug-ins? This seems to work as expected here.
-wim
Yes.
I’ve disabled the Tibidabo plugin (VisualArq), created 2 simple rectangles in model space, and on top of a Detail in layout space drew one annotation (DimAligned) snapping to the rectangles, and a second one snapping to the first annotation. The second annotation will use layout units:
test annotations in layout.3dm (56.0 KB)
Also, second issue, when zooming inside the Detail, the annotation in layout space breaks.
