We can apply the Spot Slope annotation to a ramp but it isn't very useful because, while Revit does acknowledge the ramp element, when you attempt to tag it you see [no slope] (image using 2014).
Alfredo replied to my previous post with a tip in his comment:
In this image I've dragged a slope annotation from a floor element over to a ramp element and it recognizes the ramp's slope!
Definitely quirky and subtle but at least it is possible after all. A word of caution, it will probably be necessary to check the slope value before printing, for example if Revit regenerates information because the ramp is altered. The tag could could start to report [no slope] again. Fwiw, in my casual testing so far it hasn't broken the slope value even after altering a ramp's parameters. Your mileage may vary...
Alfredo replied to my previous post with a tip in his comment:
- If you first place the spot slope tool on a floor and then move the slope annotation to a ramp, it works!
In this image I've dragged a slope annotation from a floor element over to a ramp element and it recognizes the ramp's slope!
Definitely quirky and subtle but at least it is possible after all. A word of caution, it will probably be necessary to check the slope value before printing, for example if Revit regenerates information because the ramp is altered. The tag could could start to report [no slope] again. Fwiw, in my casual testing so far it hasn't broken the slope value even after altering a ramp's parameters. Your mileage may vary...
11 comments:
I am surprised that they let another Revit version go out without fixing this, which has been around for so long. Now we have Revit 2014, and a ramp still reports "no slope" when the spot slope tool is applied on the ramp! Well, is it not supposed to be one of the uses of the tool, to report the slope of a ramp? Or the programmers thought that the tool was only for floors and roofs? It might be considered such a small "project" to do at the factory, that nobody has taken care of this in years, which forces people to do workarounds that should not be necessary, or use floors where they could have used ramps. I can understand that one issue gets not taken care of in one or two versions of Revit, but seeing the same issue again year after year is disappointing (And I know that the issue has been reported and is known). Some other improvements would be nice to have to make ramps more useful for architectural offices, such as: having layers of materials (as in floors and roofs), having the ability to display a surface pattern for the material in floor plan views, and having a tool for attaching walls to ramps, and of course having the slope annotation tool report the slope, without workarounds. Can anybody there remember about the "Ramps" department, please?
Well, what would we do if Revit was perfect - no workarounds, no tips, no tricks :-) We would all get fat and lazy and life would become boring! But seriously - the ramp tool is long overdue to be reworked.
Do you want to know why spot ramps slope dosen´t work?. Look this video:
http://www.youtube.com/watch?v=9amlOiXFMaU
It`s in Spanish but it is very visual.
hi. thanks for sharing, but how can you explain this:
i need to model road side drains that has slope varying from 1/500 to 1/1000
my problem is when the slope is higher than 1/572 , the annotation will then show [No Slope]
i used slab and slab edges to model drains. rvt 2013
any chance to adjust the slope limit, tolerance, if theres any?
And the story continues... Now we have Revit 2015, and a ramp still reports "no slope" when the spot slope tool is applied on the ramp!...
have you ever tried to anotate a spot slope onto a linked model file? I can't get it, can you? is there any reason? do you know how to fix it?
Still dealing with this. Come on Autodesk.
The best part is they removed this workaround in 2019, but kept the bug.
The workaround worked for me on 2019.
The workaround doesn't work for me in 2019, or 2020. Are there any updates to this?
Moving the tag doesn't refresh the host/reference, so it wants to be deleted.
Yes...sigh...it appears that this is A still with us and B they've "fixed" the workaround so it isn't a work around anymore. In 2020 and 2021 tests so far.
Post a Comment