Troubleshooting stair in plan region

[randy_lmn]

I am running Revit 2020, build 20.2.0.48.  

We are running into a plan region that is not functioning as expected with a stair.  The stair and all its parts are fully enclosed within the plan region.  Please see the sample file and screen shot.  I have tried to see if this is a reversed curve, moving the stair into different positions, etc.  We need the plan region to be as close to the stair as possible, but it appears that when at an angle, there is some phantom problem preventing this from functioning properly.  

[hmunsell]

if you select the full stair on the top angle, and shorten the base by 2 steps it seems to cut. when messing with plan regions the element has to be entirely inside the plan region for it to work.  check all your parameters and elements that you want effected by the plan region. 

[hmunsell]

the bottom tread of the stair has a full the others do not....

[randy_lmn]

Thanks for looking hmunsell, but I don't know that this resolves the issue.  The section of these stairs is irrelevant.  I can change the top and bottom of the plan region to unlimited and the bottom range well below the level.  The stairs are direct copies from one another, so they should not act any differently.  All stairs except for the bottom right stair (intentionally intersecting the plan region) are fully within the plan region.  The issue is in plan and it seems to be that the stair is at an angle.  If I take the offending stair (top right) and scoot it south an inch, it acts appropriately.  However, it should be able to be within 0" of the boundary same as the stair on the bottom left and still cut. 

Taking this one step further, if the only thing I do is rotate the top right stair orthogonal, it cuts, and if I scoot top left stair north an inch, it fails.  

all green checks are stairs acting appropriately

[barthbradley]

.

[ToanDN]

See screenshots.  Do they explain enough for you?  Keyword: bounding box. 

[randy_lmn]

Thanks.  I had a theory on this too and had a very similar diagram internally.  I am hoping autodesk will see this bug and resolve it.  I guess this does not really resolve the issue for the team, but confirms that the plan region works with an asterisk. 

*as long as there are no angles.

[randy_lmn · Accepted solution]

Just to put a close to this issue, I have confirmed that this is in fact a somewhat known issue, however the way autodesk describes it doesn't get to the root of the issue.  We recreated this in every version of Revit from 2017 to 2020 using a much simpler test.  Get the plan region as close to an orthagonal stair as possible to demonstrate the correct graphic expectation > copy the same plan region and stair > rotate 15°.  It is pretty clear that it is the phantom orthagonal bounding box on a plan region that is causing the issue just as ToanDN noted.  Hopefully Autodesk can resolve the issue in the next release.

  

FOR A BAND-AIDE SOLUTION: We will be using a second view set to the level below and layer it on top of the first and we will pull the crop region in really close.  Basically a round about plan region.

"Stair cut symbol in wrong position within plan regions"

[Rao_]

Thank you so much Mr. ToanDN and Mr. Randy_lmn. Initially I was having problem to understand how it was working. but thanks to your screenshots and example I now know and understood completely.

[Michel-FabeckArchitectes]

Release 2023 et 2024 still not fixed! It's not issued only with stairs but also with furnitures. Revit consider the larger rectangle around evry family that must be completely into the plan region. Boring indeed. Could Autodesk take care of the users? This kind of issues are all but pleasant for customers.

Also, the plan region must be rectangle AND align with Project view, a polygonal region doensn't work neither.