Working in Autocad is a standard way of collaborating with other people who do now work with rhino/VA. So Autocad is a must when working on a complex project involving many people from different fields. What I missed personally from VA is a) exporting plans and sections to dwg but at the same time being able to control all the lines properties b) solving intersection lines between beams and slabs etc. a) From VA styles it is not possible to export sectioned and projected elements with separate layers, but only with the parent layer and properties bycolor, bylinetype etc. In the conrtary we should have the ability to export with separate layers, and everything else bylayer. Everyone collaborator has his own layer structure, so this is mandatory. Also, we had been working on workarounds such as exporting plans and sections automatically with one click using grasshopper and humanui, which is beatibul but needs a lot of maintance. So a dialogue would be useful such as: selecting plan, export to file with the right layers etc. I think we would contribute a lot on that if it is possible. b) We had been working on workarounds with grasshopper reading hatches, grabbing boundary polyline, and then solving the intersections with regionboundary and then hatching the new polyline etc. But this leads to numerous hatches : ConcreteSlab, ConcreteBeam, ConcreteColumn but with the same pattern. So, this messes everything a lot. Also what we miss is hatch for projected elements too. There are workarounds but again involving grasshopper. Also, one thing is that when exporting a plan from rhino to dwg the hacth are not associated with the boundary polylines. It is crucial to have the hatch associated with the boundary curve to control the hatch by the polyline just like the way autocad does it. Also, when exporting the plan there are no polylines connected. Printing live sections and plans with hidden mode is perfect but has no usability other than printing to pdf or paper.
1 Like