Got a scene with a VA building including walls. Inserting other scenes (design variation) with some ‘floating’ windows (meaning not embedded in a wall), using the option 'Embedded and linked" (like you recommend because worksessions don’t work yet).
Shouldn’t the inserted windows and the walls connect automatically? Because they don’t.
Is this a limitation?
Maybe I better put the walls in the inserted file, too…
If I understand correctly, you’re inserting an external 3DM with the option “Embedded and linked”. That means that the imported geometry will lie inside a block, which means objects inside this block will not interfere with objects on other blocks or directly in the model.
Understood. However, using the insert option ‘embedded and linked’ is, as of now, the only way to get VA sections to work correctly.
Ideally, I would like to use worksessions, because I have to collaborate with my workmates often on the same file, and also because they are very practical to do design options. By that I mean some part of the building/scene can easily be swapped with another part by attaching another 3dm file.
Also, I like to keep one very light master file that contains the layouts, attach the design files as needed, and print this same layout for all variations.
So, worksessions! Yet they don’t work with VA yet.
I read you have plans to make it happen. Does this mean VA parts will connect correctly across worsessions? After all, they are not blocks.
Add support for Rhino worksessions is already in out list. We will let you know when it is available.
However it won’t happen before version 3.
Ok, thank you!
You will be releasing VA for R7 in a couple of weeks, right? Will this be VA3 already?
This will be a version of VisualARQ 2 compatible with Rhino 7.
Take into account that Worksessions will not solve the floating windows issue. Only elements that are in the same document, and in the same space/block will interfere.
Ok… Would it be technically solvable to interfere objects across worksessions, you think? Because if not, that would be quite a limitation. Worksessions are THE Rhino solution for a collaborative workflow, and a nice one, too. If that would be crippled forever, it would be not so good.
After all, objects in worksessions are not put into blocks, and can be used as input for most modelling commands.
I highly doubt we’ll ever support element interference between elements of different 3DM documents. Although it could be technically possible, it will be extremely difficult to implement.
Rhino worksessions allows you to edit one document, while the other documents are read-only. VisualARQ elements have some relations between them, like for example a window attached to a wall, or a wall extended to a roof. If you modify the roof, the wall must be modified. The same happens with the window if you move the wall or make it thicker. If related elements are not in the same document, relations won’t work.
For example, Rhino history doesn’t work either with objects between different files on a worksession.
This doesn’t mean that we’ll not find a solution to collaborate with multiple users on the same project, probably with a single 3DM document approach.
VisualARQ 2.12 is officially released. Including the support to worksessions:
The main limitation of this enhancement is that VisualARQ objects that are inside a non-active worksession document cannot be copied using the Copy or the CopyToClipboard commands. Hopefully we will improve this in future releases.