Hi
I am trying to tag a rebar in a section view. I have done this before without a problem. But this time I can't tag a rebar if not all of the rebar is visible in the section view. I have tried to align the section view with the rebar, but that does not solve it. Does anyone else have this problem or know how to fix it?
Solved! Go to Solution.
Solved by eirik_s. Go to Solution.
Its either outside the Scope of the View/Crop Region- Properties Palette > Extents > Tick Crop Region Visible > Untick Crop View - can you see the Tag?
This is because when you place the Tag if you have Attached End sometimes it picks the middle of the elements which may be out of View so by using Free End you can place manually.
Also check if the Tags are hidden/turned off - Click on the Lightbulb in the View control Toolbar to Reveal Hidden Elements to see if they are not turned on - You can also type VG and check what Tags are turned on/off in the Visibility Graphics Dialogue
Thank you for your reply. By unticking crop view all of the rebar is visible and the tag vil also be visible. My problem is that I want to tag the rebar even if just part of the rebar is visible (when som of the rebar goes outside of the section view/scope box).
All tags are tagged as "on" in the vibility/graphics override.
A picture from another file shows the rebar tag even if some of the rebar is outside the section view. See picture below. This is what for some reason I can not do in this other file.
This is because it it placing it using where the software thinks it should be placed, which is usually the middle of the element!
As regards the rebar in the image, it has 2 legs so has been place in the middle of one of the legs.
please refer to my last post and use the Options Bar to select “Free End” this allows manual placement of the Tag rather than it automatically choosing for you!
Thank you for your swift reply.
I am using the "Free End". The tag is placed in picture number one in the top post on the vertical leg of the rebar, and just disappears. When I drag the crop region out to cover all of the rebar, the tag automatically appears as shown in picture number two.
This model has a lot of angles in the structure, so it might have something to do with that, but I have not figured out what is causing this to happen.
I don’t really understand why this is not working then as with Free End you hover over the element and the leader follows where you mouse pointer is on the screen.
You can also press space when using the Tag command to switch between Attached/Free Ends
You may also want to look at the Annotation Crop Region/Boundary as this gives a little more flexibility on the extents of annotations within a cropped view!
Thank you for your suggestions.
The annotation crop region is big enough, and I have tried both "TAB"-ing and tried to use space.
When I am placing the tag, the leader and arrowhead appears, but when I click the last time to place the tag it all disappears and the warning appears. And the tag reappears when all of the rebar is in the crop view.
I do also not understand why this is happening in this file, and it is happening with all rebar shapes and in all the section views I make. I have never had this problem before, so I think it is a bit strange.
I have create the same scenario,
L- Bars
Annotate Tab > Tag by Category > Attached End
Free End
For the Area Reinforcement - Attached End
Free End
Even the Area Reinforcement System works as expected
Can you share your model for review?
I found a way around the problem in this case. If I select "Flip Section" and turn the section in the other direction it all works out fine. It is not optimal, but it works 🙂
I have isolated the problem and attached a file with a section that has this problem (Revit 2023).
A bit of a Strange one but i opened up your model, had to load in a Structural Rebar Tag so did this from Annotations > Structural > Rebar Tag and all worked fine in the View
The original issue could have been it was finding the very long rebar sets and placing outside of the view as it does not look 100% correct
I was running Revit 2023 and I am not sure if I had any updates. When I installed the Revit 2023.1.3 Update this problem was resolved. I guess it must have been a bug in the earlier versions of Revit 2023.
Nope, worked fine in all versions of Revit 2023 so would suggest more of a modelling issue but glad its sorted.
Can't find what you're looking for? Ask the community or share your knowledge.