Autodesk Revit Architecture

[#1]

Hello,

We are currently using Autodesk Revit 2013.  The new additions to the stairs are a great start, I look forward to the further changes in 2014.  My issue in this instant is regarding the plan representation of the notched precast stairs.  In plan there appears to be an extra riser line where the stair notches.  This is very confusing as if you where to count the risers in the plan it woudl appear to have 1 extra.

Has anyone else had issue with this, and also is there a solution, other than using the linework tool to change the riser to a invisible line?

Thanks in advance, 

Kevin

[#2]

I think there should be a new subcategory in VG under "Stairs" such as "notched joints". Until that happens you will need to put a note on the floor plans indicating that edge as the joint, otherwise, if you don't want to see it, the invisible line would be the only solution.

[#3]

To see what category that line was part of, I went into the Visibility/Graphic Overrides dialog, and started turning off visibility of the different Sub Categories.

I think the line you are referring to is part of the stair outline (Outlines Sub Category in the Stairs Category).

If you want to differentiate the lines, you could override the display of the riser lines (or the outlines) so that you can clearly see which lines represent risers.

Having Notched Join as a separate subcategory would make it easier to hide/override.

[#4]

Thanks to you both, I am well aware of the Visibility and Graphics, however turning off the visibility of the Outline doesn't work as it remove the whole outline.  

As Alfredo said it requires a notched joint or similar display category. I'm surprised this wasn't considered when the notched stairs were created, as it looks graphically incorrect in plan. Each component is effectively a separate/component entity brought together under one 'stair', it is understandable that the Outline category behaves the way it does.

Looks like the workaround is the good old modify linework tool.  Hopefully this will be resolved in 2014, although I imagine it's probably too late now.

K