Several issues with non standard stairs

[Prvoime]

I have this slightly odd stair, but nothing to crazy, standard stair by sketch.

Issue 1: stair path arrow is being cut off, but the line itself continues. Looks pretty awful. "Distance to cut mark" has no affect.

Issue 2: Railing. This is what Revit creates. I solved it by creating three completely different railings, not ideal, but eh, good enough for what I need (one for each run and one for the landing). Still would like to know if there is a better solution. I tried creating them as single sketch with multiple lines (one for the run, second for landing), same result.

Issue 3: Slab gets this nasty jag. Any way to get rid of it?

Link to the file: https://we.tl/t-o3a1AEex65

Thanks in advance!

[barthbradley]

View Range is what effects the Auto Up/Down Stair Direction Arrow.

The rest of the stair elements are controlled via Object Styles/VGOs.

[barthbradley]

I see a number of other issues.  You're welcome to post your Project File (rvt) here as an Attachment for us to examine/correct.  That's the most efficient way to use this forum to troubleshoot problems such as you are describing.  FWIW.    

[RDAOU]

@barthbradley 

Thats a wetransfer link ...the file a there, good luck with it I do not like stairs heh 😄

[barthbradley]

I don't like to download from third-parties.  It's a hassle and it's risky. That's why I instructed the OP to use ATTACHMENT to post the File here directly.  That way anyone and everyone can get involved.  The more the merrier.  

[ToanDN · Accepted solution]

Instead of making a single u-shaped run by sketch, make two straight runs + one landing then convert them to sketches individually.

See revised stair and railing (the railing generated itself, I didn't touch it).  

[Prvoime]

---

@ToanDN wrote:

Instead of making a single u-shaped run by sketch, make two straight runs + one landing then convert them to sketches individually.

---

This worked! Not only for the railing, but it also fixed the path arrow being cut off. Thank you!

[Prvoime]

---

@barthbradley wrote:

View Range is what effects the Auto Up/Down Stair Direction Arrow.

---

I think my defective stairs was to blame, not View range. Here's a screenshot, same issue with two values for Cut plane, just moves the arrow. But now that I've recreated it as per ToanDNs instruction, it fixed it self. Two issues solved!

The only issue remaining is the jag on the slab. I've seen this issue before in my testing, comes up when you have threads of different depth, and since it's an existing stair, it has to be like that.

As for the file, sorry, I must be going blind. I looked and didn't see an option to upload file. Just checked again, and sure, there it is 🙂 So here is revised file, with fixed railing and arrow.

[ToanDN · Accepted solution]

---

@Prvoime wrote:

---

@barthbradley wrote:

View Range is what effects the Auto Up/Down Stair Direction Arrow.

---

I think my defective stairs was to blame, not View range. Here's a screenshot, same issue with two values for Cut plane, just moves the arrow. But now that I've recreated it as per ToanDNs instruction, it fixed it self. Two issues solved!

The only issue remaining is the jag on the slab. I've seen this issue before in my testing, comes up when you have threads of different depth, and since it's an existing stair, it has to be like that.

As for the file, sorry, I must be going blind. I looked and didn't see an option to upload file. Just checked again, and sure, there it is 🙂 So here is revised file, with fixed railing and arrow.

---

You can fix the jag on section/elevation using Cut profile tool.

The 30 cm landing seems very thick.  I changed the landing type to 15 cm to match your original stair, assuming 15 cm is what you want.  That fixed the nasty notch between the  landing and the upper run.

[Prvoime]

---

@ToanDN wrote:

You can fix the jag on section/elevation using Cut profile tool.

---

Oh, you can add with that tool too! I thought if was just for cutting things out (little arrow deciding what stays and what goes away).

Calling this one solved!

Thanks!