Conceptual massing environment adds a layer of complexity. This space is designed for ‘play’ not documentation, and as such annotations in general aren’t available.
Two possible work-arounds off the top of my head:
- Build a generic model family called “note” or similar and put some model text into that. Be sure to make all the parameter values including text height, depth, and “Text” (which is the displayed value) parameter driven. These can then be placed manually or programmatically, and serve the purpose of communicating the textural content. The drawback is they are 3d objects so controlling the visibility will be tough, and they’re going to add some complex geometry to the model. Sparse use is fine as a result, but don’t get elaborate with it.
- Load the conceptual mass into a project and place the notes there. This is pretty straightforward as to how it works from the UI perspective, but gets a bit difficult from an automation standpoint. Writing the values you want to annotate out to an intermediate file, and then running a second command in the project environment after loading in the mass may be the fastest way to progress without some significant coding time. As difficult as this would be, it’d be my preference for a long term workflow involving more annotative complexity then “option 1” type tags.