Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Titleblock Family loads into Project incorrectly

11 ANTWORTEN 11
GELÖST
Antworten
Nachricht 1 von 12
Anonymous
1993 Aufrufe, 11 Antworten

Titleblock Family loads into Project incorrectly

Ok so I'm new to Revit and am trying to make a basic titleblock. The Family file itself is done. However, when I try to load it into a Project, it appears differently. 

 

The things that do not match include an imported .DWG file for the architectural seal (shown in Capture-1.jpg), and 2 labels (shown in pink in Capture-1.jpg and Capture-2.jpg). The "PROJECT ISSUE DATE" Label shows up as "Issue Date," and the "ISSUE DATE" Label doesn't show up at all. When I select the Family in the Project, The missing label appears as a question mark (Capture-3.jpg). 

 

In the Family, the two Labels are assigned to default parameters with the same name as their sample text. However, I at one point tried to create a shared parameter for a new label. I struggled to make it work, so I deleted the test .txt file and made sure that parameter is in neither the Family nor the Project. The loaded Family in a Project has differed from the Family itself ever since. This was also before I added the seal, so it's almost like it "remembers" how it was when I loaded it with the shared parameter.

 

I tried loading this family into a different project with the same results. In both cases, when I click "Edit Family" from the Project, the Family that opens does not match what appears in the Project. 

11 ANTWORTEN 11
Nachricht 2 von 12
barthbradley
als Antwort auf: Anonymous

What would speed this up, is if we could see the actual Titleblock family. Want to post it? 

Nachricht 3 von 12
Anonymous
als Antwort auf: Anonymous

Once  a parameter is loaded in the project from an external file it stays in the project until it is deleted.  So if you modify it in the text file it needs to be deleted in the project.  This happens quite a bit to me when I accidentally create a text parameter and I wanted an integer.

 

Now with Titleblocks, shared parameters don't follow the family like they do other families.  So you have to load the shared parameter into the titleblock and the project.

 

As for your titleblock itself.  Use your DWG as a guide, but create using the lines in the titleblock family then remove the dwg.  Then you can modify the lines in the project to the thickness you want.  

 

For your stamp, try to create as an annotation symbol within Revit vs using a dwg.  You can control the lines better that way.  If you can't, edit the dwg so that all lines and colors are bylayer, no overrides.  Revit will only see the layer properties, so if you are familiar with using STB's vs CTB's you will understand how Revit works with Autocad...CTB files take a bit more work/layer manipulation.  Load the dwg into an annotation symbol then into the titleblock.

Nachricht 4 von 12
barthbradley
als Antwort auf: Anonymous


@Anonymous wrote:

 

Now with Titleblocks, shared parameters don't follow the family like they do other families.  So you have to load the shared parameter into the titleblock and the project.


What do you mean by this? 

Nachricht 5 von 12
Anonymous
als Antwort auf: barthbradley

Here ya go! I removed identifying info, so it looks bare, but the funky labels are still there. 

Nachricht 6 von 12
Anonymous
als Antwort auf: barthbradley

(my original reply was posted twice and I don't know how to delete these)

Nachricht 7 von 12
Anonymous
als Antwort auf: barthbradley

Just what it says.....you have to load the new shared parameter into the titleblock and the project.  You don't have to do the same with other families because they are already attached to the category of the family (ie doors, windows, generic models, etc)

Nachricht 8 von 12
barthbradley
als Antwort auf: Anonymous

Sorry, @Anonymous: Either you're teaching me something new, or I'm just not reading too well today.  Regarding the Project Issue Date thing, it shows up fine in my Project Information.  Check it for yourself. 

 

...regarding the ISSUE DATE thing, the label is using CURRENT REVISION DATE parameter -- not Issue Date.  

Nachricht 9 von 12
barthbradley
als Antwort auf: Anonymous

@Anonymous: Is there a reason the Project Name and Address are not associated to ANY parameter at all?  There are Shared Parameter Fields for those as well. If you label them, they will populate automatically with the Project Information.

Nachricht 10 von 12
Anonymous
als Antwort auf: barthbradley

So you got the family to load into a project properly? With all the labels matching?

 

And, regarding the Project Name and Address, I see what you mean. I did that on a Friday afternoon, you know how those go...

 

Edit: I loaded it into a new project and it worked just as you described. I wonder why it didn't work the first two times I tried it. Thanks!

Nachricht 11 von 12
barthbradley
als Antwort auf: Anonymous


@Anonymous wrote:

So you got the family to load into a project properly? With all the labels matching?

 

And, regarding the Project Name and Address, I see what you mean. I did that on a Friday afternoon, you know how those go...


 

Well, I can say it's working in the Project  -- that is, the labels are being read correctly.   You just need to associate to the labels in the family to the correct parameter, and I'd label Project Name and Project Address as well. But you're off to a good start.  I took an easier route on my first titleblock. I did my first one by opening up the OOTB Titleblock and deleting everything in it except for the labels, and then proceeding from there.   

 

Good luck to you!  

Nachricht 12 von 12
Anonymous
als Antwort auf: barthbradley

@barthbradley Any new parameters that are not already included with the titleblock I should say.  Thought OP mentioned creating a new one.

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report