There is also a rather tedious amount of lag when placing and adjusting the trees (I'm guessing due to the 1000s of detail lines?) Given the sizes currently go up to 25m it means that there is effectively an invisible box 25mx25m around every tree instance. The issue with this is that at 1mØ all sizes greater than 1m turn off, however, they still exist in the family and so doing a crossing box far away from the tree means that it is still selectable. This is nested into the lollipop and the varying sizes turned off/on with visibility parameters. We're avoiding the elevation issue for now and just worrying about plan, and created separate filled regions for different sizes. (We can rotate the tree to that elevation but then it likely throws it out in another view - it's not always the case that all elevations will be perfectly square with each other.)

The other issue is that as soon as there is an elevation that isn't square on to the tree, then the lollipop becomes visible. The issue is that the 2D views are filled regions that won't scale. Making the lollipop is easy enough, as is creating a 2D representation of a tree in plan and elevation. And if we're going to use a trunk I figure we might as well use a lollipop to give some sort of context for any 3D views.

Furthermore, there are scaling issues with the 2D detail components. One idea is to just use skinny 'trunks' for the trees, so that the detail components can then be aligned properly between views, but there is no way (that I'm aware) to layer the detail components behind buildings. We currently just use 2D detail components for trees but it means there is no connection between the views - if you add/move a tree in plan you have to make sure the change is reflected in all elevations. The ultimate goal would be a rather simple parametric 3D 'lollipop' tree, with instance based parameters for height and canopy width, that then has detailed 2D views in plan and elevation:

Rpc models for revit