I raised the following issue on speckle.community here. Perhaps anyone from Asuni can comment on what might be done to improve VisualArq compatibility with speckle?
I started experimenting with speckle 2.0 and tried to send some VisualArq objects (e.g., a slab and a few columns) from within Rhino to the speckle server. From the results on the browser I figure that VisualArq objects may not be supported. The objects seem to be placed on the origin (perhaps they are all overlapped) and there are some points on the locations where they were inserted in the model. I imagine this must be related with how VisualArq creates the objects as blocks.
So the question is what can be done to improve the compatibility of VisualArq with speckle?
I think what we’d need to chat through is having a Speckle converter for VisualARQ that would be able to create native visual arq elements. Since Rhino doesn’t come with it by default, we don’t tackle it. To be upfront about it, we’re really stretched out at the moment and won’t be able to prioritise this soon, but we do welcome contributions as all our stuff is open source:
VisualArq is in a strange place for us: it’s basically a whole new authoring software (that we don’t support) within an existing authoring software that we support (Rhino).
What would help us @Filipe_Brandao is to understand what workflows you’re having in mind when sending VisualArq objects around! For example, do you want to send them from Rhino to Rhino, or simply view them in the browser, or collaborate with multiple teams, or from Rhino/VisualArq to Revit, etc.
I’m looking into ways of sharing the models with colleagues working in the same project using different software (Revit and ArchiCad) and engineers (Revit). Here we would need to send back and forth VA objects, and convert Revit and ArchiCad objects into VA and vice-versa. This is the top priority.
A second use-case is to show the model in a browser for client review and retrieve comments back.
On the bottom of the list is internal use, from VA/Rhino - VA/Rhino. This is something that might percolate into the design process when we are very familiar with the versioning system and confident that everything flows without hicks.
unfortunately no we haven’t gotten enough “shouts” in this direction. We should be able to though support visual arq > viewer though, if that’s not happening do let me know!
we haven’t gotten enough “shouts” in this direction. We should be able to though support visual arq > viewer though, if that’s not happening do let me know!