Hello,
I need to use a stair tag to tag single flights of a multistory stairs, but the tabbing does not work. Only on the first level of the multistory stair I can tab the single flights, like normally.
Any reason for this behavior?
thanks
regads
gio
I don't have an issue tagging individual flights of a Multistory. No tabbing necessary either.
...What version?
Well, it's weird, but it works now.
My top 3 stairs got grouped within the multistory group. The stairs had a lock (sort of "by-type" lock) and once I unlock them, the single flights became taggable again, using tab. (By the way, if you do not use Tab, you are tagging the whole stair, not its flights).
This might have happen when I removed the last 2 levels, made adjustments to the stair, and added those levels again. Since then, those top 3 stairs became somehow grouped, within the multistory group...
Thank you
The pin/link icon is meant to indicate that they are derived from a parent (the first instance). Unpinning/locking means you want to override them, make them different from the parent. I believe their intent is to expect you to select/edit the first one (parent).
Edit to add: I find it necessary to TAB twice to select an individual stair that goes between levels. The primary selection is the entire Mult-story stair. The first TAB allows me to isolate each different repeating stair type (different floor to floor heights). The second TAB allows me to select the individual stair spanning a pair of levels.
Also with Worksets I find it necessary to borrow the stair (click the Workset icon "stacked blocks" or right click make element editable) first sometimes.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
That's what I thought,
but the fact that you cannot tag the individual flights of a locked stair is not good, since we do not just put "SEE OTHER ENLARGED PLAN" note, but we normally re-tag the stairs even if they are identical to the level below...
Thank you
regards
gio
I'm not following. They only need to be unpinned in 2018 and 2019 to affect changes to individual flights in the Multistory, but tagging isn't affected by the pinned or unpinned status.
I don't see any issue with tagging individual flights...as the other reply says...either.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Yeah, it's because you guys need to have different height levels.
Within a multistory stair, Revit automatically "Groups" stairs of the same height, even if they are not sequential.
This are the Sub-groups I mentioned in my post.
Now, the first stair of the Sub-group, you can tab and reach the flights, while all other above, you cannot, unless you unlock the stair whose flights you wish to tag or select...
This is clearly visible in elevation or section, see attached sketch.First TAB on bottom stair selects the sub-group (in this case 10' tall stairs)
The second TAB selects the stair, the third TAB selects the flight...
However, the flights of the top 10' stair can be tagged only if the stair is unlocked...
... and note that "tagged", "selected" and "tab-able" are interchangeable terms in this example.
I think there is a logic in grouping the same height stairs in a multistory, but I am not sure about preventing tagging the single flights in the stairs above above...
If we unlock and change the stairs, the tag should follow... right? It's a BIM software...?
Anyways, the workaround in this case is simple, just unlock the stairs above the first one to be able to tag its flights...
Thank you
Regards
gio
My stair has more than one floor to floor height and I can tag the stairs individually.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
So, Steve, in that example, the first and the second stair are taggable, while the ones above need to be UNLOCKED in order to be taggable... Also remember, I am talking about the single FLIGHTS, from floor to landing, not the floor-to-floor stairs.
This happens to me in Revit 2018.3.2.7.
@gsucci: Is the 28R the multistory source? Regarding tagging flights: I can flight without needing to unpin in 2018.2. Also, I have to unpin to make changes to individual flights in Multstory Stairs. When pinned, they cannot differ from source, which is why I'm asking if the 28R is the source.
Note: I had to touch the end riser, in order to tag just the flight. It wasn't recognized by touching the flight at any other location.
In my example the source was the first stair (level 1)...
In Revit 2018.3.2.7 this is a reproducible behavior: single flights of stairs locked within a multistory stair, do not tag / select, unless they belong to the first instance of the floor-to-floor height group.
Once unlocked, they tag / select normally.
thanks
gio
No, it was/is not necessary to unpin any part of the stair to tag what I show in my image. However, what you wrote in your last reply clears up the difference, tagging an individual run, not the stair overall from floor to floor. I do have to unpin the upper stairs to tag an individual run within a stair.
Yup, quirky.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.