tag:blogger.com,1999:blog-1835628312468607200.post3788434366858952863..comments2023-06-14T02:25:00.155-07:00Comments on Structural Revit Ninja: Current challengesBen Mayhttp://www.blogger.com/profile/11320697929817688619noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1835628312468607200.post-12482033822003052532013-01-11T17:49:47.293-08:002013-01-11T17:49:47.293-08:00Both beams are custom, not OOTB. The concrete infi...Both beams are custom, not OOTB. The concrete infill was specific only for this type of family, and not a standard RC beam, but the steel beam was the office standard for that beam type. All instance parameters can be mapped across in the composite family, constraints are an issue with the OOTB families, I had built the office families differently for this reason. If you dont mind having a specific family rather than using the standard beam, a simpler line based framing family is easier to constrain.Ben Mayhttps://www.blogger.com/profile/11320697929817688619noreply@blogger.comtag:blogger.com,1999:blog-1835628312468607200.post-51482227666118503492012-12-08T18:47:28.767-08:002012-12-08T18:47:28.767-08:00To clarify, you nested steel and concrete beam fam...To clarify, you nested steel and concrete beam families into a custom "composite" family, and then loaded into your project. Were these beam families out-of-the box or did you create custom profiles and insert them into your family? I'm also assuming you used instance parameters for the length. How did you keep the beams references from breaking? Were the beam orientations always horizontal--ie no need for any other parameter other than length?<br /><br />Best regards,<br /><br />Nick from MissouriAnonymousnoreply@blogger.com