Announcement

Collapse
No announcement yet.

Assemblies

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #1

    Assemblies

    Hi,

    did anyone else experience problems with braces in an assembly?

    When I create the assembly they are fine and when you copy the assembly they go nuts.
    Tags: None
    #2
    How are you using assemblies? What are you getting out of it opposed to using a group?

    Comment

      #3
      I was just looking into assemblies and found them to be promising. You can tag an assembly and you can create assembly views (neither of which can you do with groups). Neat, but looks like you can't edit the assembly and then have the changes affect all the others (similar to groups). Instead it creates a new assembly type. Not sure if I'm missing something but I'm reluctant to use the tool if I have to model it perfect the first time.

      Comment

        #4
        I agree with you. Copying an assembly should create an instance and not a new type.
        I don't use them a lot because of that.
        Julien
        "Au royaume des aveugles, les borgnes sont mal vus!"
        P. DAC
        Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/

        Comment

          #5
          Copying an assembly does create an other instance only if things are exactly the same. If you are comping something that is hosted to another host that is different it will create a new assembly. If you are copying a column, that does not have any host from one spot to another then you will have two instaces of the same assembly. Now if you change one of those columns it will now make a new assembly.

          I find assembly views to not be worth while, becasue as discussed in an other thread...if something is not in the assembly you can not see it in the assembly view...levels, grids, hosts...

          Comment

            #6
            Originally posted by gdoherty0102 View Post
            Copying an assembly does create an other instance only if things are exactly the same. If you are comping something that is hosted to another host that is different it will create a new assembly. If you are copying a column, that does not have any host from one spot to another then you will have two instaces of the same assembly. Now if you change one of those columns it will now make a new assembly.

            I find assembly views to not be worth while, becasue as discussed in an other thread...if something is not in the assembly you can not see it in the assembly view...levels, grids, hosts...
            Well, that makes sense. If I created an assembly of, for instance a truss, I would want to have it make another type if the walls to which it's attached ar different. Seems like normal behaviour to me. If it's not the same, it's not the same.

            Back to the OP: could you be more specific?
            Martijn de Riet
            Professional Revit Consultant | Revit API Developer
            MdR Advies
            Planta1 Revit Online Consulting

            Comment

              #7
              Humm, I have to disagree. It could be the same not at the same place. should be a new type only if what's belongs to the assembly changes, not the host. replace assembly with any other Revit element, you'll see what I mean. assembly changes, new type; same at another place, new instance.
              Julien
              "Au royaume des aveugles, les borgnes sont mal vus!"
              P. DAC
              Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/

              Comment

                #8
                I cant be 100% sure without being in your project to test it, but if You are referring to what I think you are, it is related to the analytical nodes.
                Your first brace connects the analytical points (which you probably have turned off in VG settings). In the case of a vertical brace for example, the brace will be connected to the centrelines or end points of your columns. When you copy this group (regardless of if you group it or not) the analytical nodes remain attached to the original columns. The same happens when copying trusses around especially with webs although trusses will usually remain in the correct planes, if you turn analytical lines on in your 3d model you will see they are all connected to the original location of the first truss u made.
                As a check, turn on your framing analytical lines, and see if they all point back to an incorrect bracing bay.

                Comment

                  #9
                  Braces seem to be very fickel...assemblies are not as constrainging as groups are. Groups tend to override snaps allowing you to control things a little better than you do outside a group. Though asseblies will help you create your views and such, most frames will need grids. I still say that groups would be the way to go for a brace rather than an assebmly.

                  Comment

                    #10
                    assembly

                    I was away so I couldn't reply earlier.

                    i'll add the rvt file for the assembly

                    try making a copy of the assembly and you will see the braces go crazy.
                    Attached Files

                    Comment

                    Previous 1 2 template Next

                    Related Topics

                    Collapse
                    Working...
                    X