I fully agree with @Toni_Osterlund.
For most of our production partners, and even for our internal workflows, it is very important to have a fast and reliable option to convert all our output data (finalized layouts) into ‘flat’ (i.e., model space only) .dwg files.
When we need to send an editable version of a project to our contractors, a model space-only .dwg offers several advantages:
- It is easy and fast to read (navigating between a large number of layouts in .dwg can be cumbersome).
- It minimizes the chance of human error (different annotations distributed among layouts can be easily missed or overlooked).
- The entire project can be understood within seconds of zooming and panning.
- Editing is straightforward (we often exchange multiple .dwg files with contractors, making quick sketches and iterations before applying changes to our BIM model).
- It is great for archiving purposes, providing a quick snapshot of a project’s current state with everything captured and nothing hidden in different spaces.
I also fully agree with @Eugen regarding the urgent need for a separate 2D space in Rhino, similar to what Archicad or Revit offer. This is closely related to our discussion about vaExportToDwg, but it opens up many other topics (and years of development). To keep it simple, vaExportToDwg with “model space only” option will be more than enought for now 