Thanks for the reply Jeffrey, but I'm not sure that is actually the issue -
notice in the attached image, I've got the Beam tool selected, and the H
series open web joists are showing up in the type list. These are what I'm
using.
I had a backchannel discussion with Greg on this and he suggested that it
might be because the open web joists were not created with the right
structural template and therefore don't respect workplanes other than the
current level.
On the elevation view, that was my mistake. I could have sworn I had done a
zoom to fit, but at some point I entered ZA and viola, there was the joist
in my view.
Thanks,
--
Matt Dillon
"JeffreyMcGrew" wrote in message
news:22040377.1083603037587.JavaMail.jive@jiveforum1.autodesk.com...
> Matt:
>
> The reason the 'beam' in this case isn't sloping is because it's not a
beam. What Greg's talking about here is drawing beams using the beam tool.
What you are doing is placing a truss using the component tool. When placing
components, they 'land' on the level currently active and ignore whatever
ref. plane you have active, for this is how they are 'built' in the family
editor- they are set to default to be 'flat'.
>
> So what you would do in this instance is place one, then go to your
elevation view, and then rotate the truss to the slope you need. Then you
could go back to plan and array/copy/move it where you need it.
>
> One of the biggest frustration to new users I've found from teaching
people Revit is the learning curve involved with the content. With Revit the
intelligent content is key, and if you don't understand yet how certain
items behave, then you'll find yourself frustrated at times because things
aren't behaving the way that you expect them to, so you think they aren't
working and that there is problem with the software. It's really that
certain items, esp. the structural ones, behave in a way that's common for
structural engineers and as such are trying their best to follow that set of
rules- not yours as an Architect. Once you have more experience with Revit
and it's content (and begin making custom content) then all these issues go
away, for then you'll understand why things are acting the way they are.
Revit's interface is very simple, and it's workflow straightforward- it's
complexity is in the Content, which is something that can throw a lot of
people, esp. those used to the complexity being in the interface or program.
;-)
>
> The second part of your question I think has to do with your Elevation
depth or clipping or something. Maybe the truss is below the bottom crop of
your elevation? I just did exactly what you outline here and it worked
fine. So check your elevation's depth and make certain that your web truss
is within the view. I drew the exact same truss in plan, then went to an
structural elevation view, and could see it...