Download custom pattern files for revit

When the appearance of the element is not controlled by an element category or subcategory, it is using a line style. A line style defines the line weight how thick the line is drawn , the line color, and the line pattern solid or a series of dashes, dots, and spaces. All Revit models start with a number of default line styles.

These line styles are needed for different system elements. Use these default line styles, or customize line styles for elements. Default line styles are defined to system elements in Revit. For system elements, the default line style assigned can not be changed, but you can alter the appearance of the line style assigned. This, by default, is a purple solid line. Default line styles can not be removed from a model. The name displays under Category in the Line Styles dialog.

In the line weights dialog you find three tabs. Each tab allows you to define the width of the line depending on how the line is being used. Widths of lines are defined for model lines, perspective lines, and annotation lines.

Line patterns define a series of dashes, dots, and spaces repeated over the length of the line. In the line pattern editor you can define a type dash, dot, or space and the length of the dash or space.

The length is not dependent on the scale of the view and represents the length of the segment when printed. Line patterns are used in the definition of a line style and are also used to define line used for categories and subcategories in Revit. Default line styles used for elements defined by Revit. What should happen is the opening should remain, and you should explicitly have to create a new infill object, so that you can quantify it as part of the building works.

Any BIM modeling program has the concept of relationships between elements. For instance, in IFC, a building storey must belong in a building. If you demolish the building, by extension, the building storey is also demolished. In Revit, this is the same: walls must belong to a level unless you come across that issue with curtain walls where they can disassociate themselves with deleted levels and just float in space.

This means that if you delete a level, all elements on that level are also deleted. This is known as a tree, graph, or hierarchical structure, where elements depend on one another. What is not good is that Revit does not acknowledge that elements have relationships. It will scold you in a warning and happily delete or ungroup objects to fix a broken graph, but it will never actually allow you to view this relationship.

For instance, you cannot select all elements that are part of a level. You cannot select all elements that have a constraint or working plane that derives from another object. If you select a tag, you cannot select the element that is being tagged. The result is that people become scared to perform graph-breaking operations like ungrouping objects because they cannot be fixed in Revit.

People are hesitant to delete levels, or just sigh when dimensions drop off. The section box is really hard to control when in perspective views since it generally goes out to infinity.

The workaround is the adjust it in parallel view, and then switch to perspective view. The crop box also loses its scale and position, so you end up getting lost in space. Revit manages to be spectacularly bad at both 2D and 3D. The end result? Revit will barely support LOD in a large project, but the added geometry and the inability to manage external documents as mentioned before will cause Revit to be unable to scale to LOD It might go on a small project, but not further than that.

Unfortunately, its object types and object instances which so clearly mirror the software concept of classes and objects, do not use the full potential of OO.

This is unlike IFC, which specifies object typing. Surface normals on masses are very important because they determine the wall orientation when you do wall-by-face to create complex geometries. If you want to do a wall with finishes and substructure that align to a datum, you need to make sure your normals are all facing the same way. This means you often need to create two versions of walls - one front-face, and one back-face, and use trial and error to work out which one goes where.

If you are doing a custom shape, Revit does not offer any tools to check planarity. This usually means that fabricators cannot set out, nor actually construct the funky shape you have drawn. Revit will happily distort hatches and other 3D elements to fit. This means that project-specific data is inlined into the project files, and non-project specific data is referenced from an external, linked library, so it can be reused and seen as a source of truth for many projects.

So you are unable to link in families or project settings. This means that every single project essentially duplicates every single company asset that it needs. Not only is this inefficient, it means it is difficult to propagate changes across the company. If we improve an asset, we cannot easily roll it out to every project. It also encourages project members to make changes locally and not share their improvements to the rest of the company. Why would you ever do such a thing? Add an image into a Revit project.

Now delete it. Is it gone? Manage Images dialog back into your file? Even though it stores a path to show the source, can it detect duplicate sources? Unlike IFC, where you can happily connect external resources to elements, such as supporting product documentation and brochures, or external databases and schedules, Revit does not support any such thing.

Instead, people rely on using third-party plugins, such as dRofus. This is odd, because dRofus supports IFC. If you want a view template to apply to multiple types of plans, such as floor plans and area plans, the colourschemes will only work for one or the other. This means you need to do a manual setting, or create two view templates. Profiles are pink. Specifically, they are FF00FF. Errors are orange, or FF This provides a WCAG contrast ratio of 1. In practice, this means that it is really hard to spot where the mistakes are when you draw an incorrect profile.

This makes it really hard to even see what you have selected. Architectural convention states that a plan is essentially a horizontal section - a boolean operation that displays what is in front of the cutting plane, and whatever is behind it is not shown, or when relevant, shown in a different visual representation e.

Lines further than a certain threshold in the distance may be shown in a lighter or faded representation to show that it is far into the background. An even more bizarre example is where a Revit floor will disregard your view depth and show anyway , as long as it is within an arbitrarily picked range of 4 feet of your bottom clip.

Stairs also have their own cutting plane and view range rules , which become especially confusing when you create your own in-place stair model, or even convert that in-place model into a stair family. Furniture families also ignore the cutting plane. There are also no ways to change the rules for cutting, which results in people doing hacks like invisible geometry to be cut , or placing objects with certain offsets.

In Revit, by default, all doors need a wall to be hosted in. In order to do this in Revit you need to trick it by creating a generic model, and then changing the category to door.

It may or may not show up in your door schedule, though. Unfortunately, Revit does not allow you to assign a construction phase in a wall opening. An unsemantic workaround is to create a void family. The IFC spec supports element relationships, where elements can be related to one another. A common usecase for this is doors, where a door goes to a space, and from another space.

You can work around it, using custom parameters, API calls, and Dynamo scripts, but fundamentally Revit does not make it easy to expose element relationships. Certain families are considered to be special for whatever Autodesk reason, and cannot be created in the traditional family way. They can only be created as an in-place model. Some Revit users have been taught that in-place models are always bad, and therefore will resort to misclassification of BIM elements instead of actually building the object properly.

Even if an in-place model is used, it is difficult to propagate, and if it uses openings, it is very difficult to copy around the project, and you cannot create instances of it. A little known fact is that roofs also do this. An even lesser known fact is that a roof things that above is interior, and below is exterior. For roofs with complex layered families, or by face, or curtain walls, this symptom will show and you will then have to basically draw an upside down roof.

Given that metal profiled sheet roofs are absolutely everywhere in construction, it is surprising how hard it is to draw in Revit. This suggests that the renderer used for views and sheets are different, and may account for inconsistent visuals between the two. This is not an easily replicated one but does occur, especially in 3D views where you are constantly changing section boxes and orbiting. A strange occurance might be where a large link does not show up in a section or elevation.

Yeah, I see now that I can use that offset for my needs. What I am trying to build is shown in the screenshot above - you are looking at two overlapping rail families: one is the standard cable guard with flat bar stock, and the other is a slightly modified handrail, rectangular type which utilizes round stock for the top and bottom rail.

Revit Architecture Forum. Share your knowledge, ask questions, and explore popular Revit Architecture topics. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Message 2 of 5. If you have AutoCAD, you already have them. Rob Drafting is a breeze and Revit doesn't always work the way you think it should. Message 3 of 5. If this solved your issue, please Accept it as Solution help other forum users with similar issues to find answers easily.

Mirko Jurcevic My blog: www. Message 4 of 5. Message 5 of 5.