It's actually a feature of the anycodings_autodesk-forge BIM 360 product that it can read the anycodings_autodesk-forge "main" Revit file, retrieve all anycodings_autodesk-forge references from it, and bundle them all anycodings_autodesk-forge together into a ZIP file. You can manually activate this workset visibility in the Visibility/Graphics menu inside of views that will be used for renderings.The OSS part of the Forge Data anycodings_autodesk-forge Management API is a simple "object anycodings_autodesk-forge storage service", so it doesn't know anycodings_autodesk-forge about any potential references between anycodings_autodesk-forge files. The first is to create a workset that is invisible by default. There are two ways to avoid issues with these RPC families.
You obviously don’t want to print a set of CD documents only to find out there are a bunch of birds, cars, plants and wine glasses in your plans. The downside is that people now place a bunch of objects in their Revit models that are only used for renderings. It is becoming more and more common to render directly in Revit by using great plugins such as Enscape. That’s what we did in the BASICS template.ġ2- Place Too Many RPC Families For Renderings It is a great idea to locate the origin using reference planes in your Revit template. Make sure to place the building in relation to this origin, usually at the intersection of two important grids. Many users are confused about this origin and end up modeling the project very far away from it. In the image below, you can see a random window family found online. Too many heavy families in a project will cause performance issues. The problem is that the family ends up being 3 MB, which is way too much for what you actually need. That means they have 50 options that can be activated by checking parameters. The other problem is that they are often built as “super-families”. It’s to create families so you will end up buying their products.įor example, most families you will find on BIM Objects will have a bunch of parameters like phone number, URL and other useless junk that doesn’t provide any meaningful value to your project. That means their incentive is not to create lean and efficient families. Manufacturers create Revit families as advertisements for their products. Remember that when something is free, it means you are the product. A good Revit family should be lean, efficient and without too many parameters. Most Revit families you will find online are terrible. If you really have to explode a CAD file, do it inside of a family or in a dummy project. Short story: purge all CAD files, use Link CAD instead of Import CAD. We wrote a guide about how to properly use CAD files inside Revit.
0 kommentar(er)
