What Revit Wants
This fixes the relatively nasty addin incompatibility issue that was floating around…
Direct link for Revit 2015:
http://download.autodesk.com/SWDLDDLM/Updates/RVT/2015/Autodesk_Collaboration_v7_for_Revit_2015.exe
Direct link for Revit 2016:
http://download.autodesk.com/SWDLDDLM/Updates/RVT/2016/Autodesk_Collaboration_v2_for_Revit_2016.exe
Known issues and Fixes:
http://download.autodesk.com/SWDLDDLM/Updates/RVT/2016/KnownIssuesA360Collaboration_v7_2015and_v2_2016.htm
A while back I started using the hashtag GoodRevit to share workflow tips that I’ve found useful when working in large teams and on large projects. Here are some of those tweets:
Establish Project Origin and Grid Layouts as early as possible, and share with each team member as they join the project #GoodRevit— Luke Johnson (@lukeyjohnson) August 10, 2014
Use View Templates as much as possible #GoodRevit— Luke Johnson (@lukeyjohnson) August 11, 2014
Naming your Reference Planes is #GoodRevit— Luke Johnson (@lukeyjohnson) August 13, 2014
Using Tags instead of Text is #GoodRevit (where it is possible and logical to do so)— Luke Johnson (@lukeyjohnson) August 14, 2014
Setting a useful and informative Starting View is #GoodRevit— Luke Johnson (@lukeyjohnson) August 16, 2014
Using View Filters more than other VG methods (like Category, Subcategory, especially Element) for visibility is #GoodRevit— Luke Johnson (@lukeyjohnson) August 18, 2014
Using Project Origin-to-origin linking for team collaboration is #GoodRevit. Set it up correctly at the start, save yourself much pain.— Luke Johnson (@lukeyjohnson) August 19, 2014
Using Property Lines for the property line is #GoodRevit. Whoever said Revit doesn’t make sense?— Luke Johnson (@lukeyjohnson) August 22, 2014
In the Family Editor, it is #GoodRevit to keep all of the dimensional constraints in 1 or 2 views, to improve discovery and predictability.— Luke Johnson (@lukeyjohnson) September 1, 2014
It is #GoodRevit to use Save/Load selection, especially for large sets of dissimilar objects. Much faster than crossing-window.— Luke Johnson (@lukeyjohnson) September 18, 2014
When moving Tags around in a complicated #Revit model, turn Snaps Off. It will make moving them around much quicker. #GoodRevit— Luke Johnson (@lukeyjohnson) May 18, 2015
In a large & complicated model, if you temporarily hide everything *before* placing a new Group instance, it will be much faster #GoodRevit— Luke Johnson (@lukeyjohnson) May 27, 2015
On large projects with many links, temporarily turn off all RVT Links in VisibilityGraphics before attempting to place on a sheet #GoodRevit— Luke Johnson (@lukeyjohnson) July 15, 2015
Performance wise it is very ‘cheap’ to push items and RVT links into *Closed* rather than Open worksets on large federated models #GoodRevit— Luke Johnson (@lukeyjohnson) July 28, 2015
Do you have any tips for Good Revit? Join the hashtag, or freel free to comment at this post.
Special promotion on RTV Xporter, by RTV Tools:
Here: https://data.sa.gov.au/data/dataset/3d-model
or direct: http://opendata.adelaidecitycouncil.com/3D_Model/BASE%20MODEL%20with%20textures.zip
Its a 1.9 gb dataset with textures, delivered under Creative Commons. How long until we have access to the same thing for every city in the world?
via email:
URL Changes – Please note the changes below:
Previous URL: https://app.prod.gteam.com/gteam/app
New URL: https://app.prod.gteam.com/tc/app The previous URL will remain active for 60 days after the update.
Sync Tool Changes – A new version of the Sync Tool will be released. It will need to be downloaded and installed after the update is in place. More information on the Sync Tool changes can be found here
Let’s say you have some linked RVT files and you are using ‘By Linked View’ for visibility. What if you just want to hide off a single type of Filled Region from that Linked View? Is it possible? Yep, here’s how:
Done!
I reported this issue on github a while back, but it turns out it is a reasonably serious DLL conflict. More details here:
Collaboration for Revit: 2015.6/2016.1 breaks other add-ins | Revit Products | Autodesk Knowledge Network
Issue:
Users reported that installing the Collaboration for Revit® 2015.6 or 2016.1 add-in is causing other add-ins to stop working.
Causes:
There seems to be a DLL conflict with the latest Collaboration for Revit add-in.
Solution:
Status: This incident is currently being investigated for a possible cause and resolution
Incident ID: 72448
Workaround: Continue using the 2015.5 or 2016.0 version of the Collaboration for Revit Add-in.
Note: If you need to remove the newer add-in (Autodesk A360 Collaboration for Revit…), you will also want to remove the new version of the “Personal Accelerator for Revit” and “Dynamo 0.8.1”
So what’s the deal with Stingray? Basically we are talking about a realtime rendering engine that talks to 3ds Max. As we know, Max talks to Revit. Autodesk is essentially providing (another) realtime rendering workflow from the BIM environment, and that is obviously a good thing…
Here’s a snippet from In the Fold:
To understand the impact of this new capability within 3ds Max, let’s take a look at the state of a BIM workflow using Autodesk solutions before today’s announcement.
 |
| The Stingray engine allows designers, owners and stakeholders to access and visualize a building model in real-time to fully understand the scale, feel and experience of the building before construction starts. |
Building designers using Autodesk Revit software have had the ability to easily import models into 3ds Max to create stunning, photo-real images and animations to communicate design intent. It’s a workflow that’s been widely accepted in the AEC industry and plays an integral part in the design process. Now, with the Stingray engine, Revit models can be brought into 3ds Max to be made visually stunning and then imported to the Stingray engine to be made fully interactive, allowing users to explore “what if” design changes in a compelling visual environment not unlike a first person walk-about in a physical building. The real advantage of this is that it allows designers, owners and stakeholders to access and visualize a building model in real-time to fully understand the scale, feel and experience of the building before construction starts.
Read the whole post:
Autodesk Stingray Real-Time Engine Takes Design Visualization to a New Level for AEC Industry
We’ve talked about exporting shared parameters before, but when you are editing a Titleblock (that you have inherited from somewhere) you may find that the Family Types dialog does not list all of the parameters that may already be in use in Labels in that Titleblock family.
So, how do we export those parameters? Easy:
via email:
… updates to IFC for Revit 2015 and IFC for Revit 2016, which you can get to using the links below:
IFC for Revit 2015 (v15.5):
http://apps.exchange.autodesk.com/RVT/en/Detail/Index?id=appstore.exchange.autodesk.com%3aifc2015_windows32and64%3aen
IFC for Revit 2016 (v16.2):
http://apps.exchange.autodesk.com/RVT/en/Detail/Index?id=appstore.exchange.autodesk.com%3aifc2016_windows32and64%3aen
Updates from the previous version are listed below. Please upgrade to the newest version!
NOTES:
1. IFC Exporter for Revit 2013 and IFC Exporter for Revit 2014 will no longer be getting regular updates.
2. IFC for Revit 2015 and 2016 includes export, import and the alternate export UI. There is no need for separate installs of each.
3. This update will work for both Revit and Revit LT.
What’s new for IFC for Revit 2015 v15.5.0 and IFC for Revit 2016 v16.2.0:
General:
– This is the IFC2x3 Coordination View import certified version of Revit for Link IFC, as seen on http://www.buildingsmart.org/compliance/certified-software/. At the time of this writing, it incorrectly lists “Autodesk Revit Architecture” as being import certified instead of “Autodesk Revit”.
– Both Link and Export will use the IFC4 Addendum 1 schema instead of the IFC4 schema if the IFC4_ADD1.EXP is loaded in the EDM sub-folder of your Revit executable folder.
New Export Functionality:
– Allow setting of IfcBuildingStorey element composition type via IfcElementCompositionType shared parameter for levels.
– IFC4: handle elliptical edges for IFC4 Design Transfer View export.
– Support export of volumes as liters (a.k.a cubic decimeters)
– Support export of volumetric flow rates as liters per second (a.k.a. cubic decimeters per second).
New Export UI Functionality:
– Better progress messages in the status bar.
– Remove list of “Current Options” from the starting UI dialog; only display the IFC Schema and MVD as “IFC Version”
– Remove path from “Projects to Export” list; the path is now a tooltip.
Export Bug Fixes:
– Correctly toggle between SLIDING_TO_LEFT / SLIDING_TO_RIGHT for flipped doors.
– Use the element type “Function” parameter when setting the “IsExternal” common property for all element types, not just wall types.
New Import Functionality:
– Add “IfcElement HasPorts Name” and “IfcElement HasPorts IfcGUID” parameters to show port information for elements. There will be multiple shared parameters created if the element has multiple ports.
– Add support for more thermal transmittance units.
– Entities that are decomposed by IfcBuildingElementPart will now be visible if either the top level category or the Parts category is enabled by default.
– If attempting to create an IfcShellBasedSurfaceModel as a Solid results in any dropped faces, import it as a Mesh instead.
– (2016 only) If processing an IfcBooleanResult entity results in a failed Revit Boolean operation, try again by slightly shifting (by 1mm) the second of the two geometries in the operation.
– Improve import of IfcSweptDiskSolid when the geometric description of the entity would create a self-intersecting surface. In this case, create the minimum number of solids possible to import as much as the geometry as possible.
– Read in IfcSystems that aren’t associated to the building via a IfcRelServicesBuildings relation.
– Read in IfcPropertyBoundedValues (including support for IFC4 version).
– Support import of volumes as liters.
– Support import of volumetric flow rates as liters per second.
Import Bug Fixes:
– Add a message to the log file if we skip importing an IfcProduct that neither has geometry nor is decomposed by other entities.
– Fix a potential crash if a file contains a large number of elements in system joined by ports.
– Improve log message when an entity can’t be imported because it has no geometry.
– Improve log message when an entity can’t create all of the facets of its tessellated geometric representation.
– Move some MEP entities from Generic Models category to the appropriate categories by default.
