Annotation Symbols Not Allowing Placement

[Anonymous]

I'm using Revit Architecture 2017 and want to place copies of the standard Revit annotation family Anno_Spot_Elevation_Target_Filled on plans. Unfortunately, the only symbols that are available to me in plan (and section and elevation) views are those in the attached screenshot.

I tried to use the right-click menu on the annotation family in the project browser to 'create instance', but I just get the warning message: Can't create this kind of element in this view in the current mode. I've worked around this by creating my own version of the family, but I don't want to have to roll this out across the organisation and want to use the OOTB family. How can I do this?

[ennujozlagam]

hello, if i understand you correctly, you can do this > go to properties > edit type > duplicate (create name) > change leader arrowhead. thanks

[Anonymous]

Sorry - the problem is nothing to do with leaders. It is simply a symbol that I am trying to place. It is not part of a label or anything like that.

[kadmonkee]

try placing a vertical reference line in the generic symbol or the host family that is long enough to exceed the cut plane

some symbols in "plan view" will not display without recognizing its designated elevation level

you may need to create a custom generic annotative family to accommodate this scenario.

[Anonymous]

If I need to edit the OOTB families to make them work, then there is nothing gained - I already have a custom symbol of my own that works, so it does not seem to be related to the cut plane in any case. Thanks for the suggestions though!

[kadmonkee · Accepted solution]

"Can't create this kind of element in this view in the current mode"

this relates to a specific view type and possibly the families category (they don't belong together).

if you found a solution that works then why not roll it out to everyone and teach them how it works?

the cut plane option allows for more flexibility in other view types Floor Plans, Reflected Ceiling Plan, Plan Regions etc.

categories are effected by these view types, so they need to be taken into consideration.