“Revit makes available the following IFC-specific files:
IFC Metric Template.rte. This file allows you to create new projects that are already set to the IFC standard.
IFC Parameter Upgrade.rvt. This file enables you to upgrade an existing project to contain IFC parameters by reading the instructions contained in the IFC Parameter Upgrade.rvt file.
IFC Shared Parameters.txt. This file contains the shared IFC parameters if you want to manually update an existing project to contain all or some of these parameters.
Note: It is recommended that you use the IFC Parameter Upgrade.rvt file. If you use IFC Shared Parameters.txt, you must add parameters one at a time, setting the correct categories for each. If you use IFC Parameter Upgrade.rvt, you can use the Transfer Project Standards tool to add the parameters in one operation.”
It hasn’t shown up on Exchange yet, but it is already available for download on the Sourceforge page. There is an update to IFC 2015 (the one that is really robust, fast and accurate for Import and Export), and also some updates to 2014 IFC addins.
Some of my testing: 30% file size reduction in RVT when using Link IFC on 85mb steel model from Tekla v16.1 v15.1.0 = 297mb v15.2.0 = 210mb
66% file size increase in IFC when using export IFC to all proxies: v15.1.0 = 288mb v15.2.0 = 478mb
Some key Export improvements from the readme (I’ve underlined points of interest): – The functionality for creating and using user-defined property sets has been greatly enhanced. This includes: – Added a “DefaultUserDefinedParameterSets.txt” file to allow a user to create user-defined property sets for any setup, including the in-session setup. – Added the “IFC2x3 Extended FM Handover View.txt” user-defined property sets file to the installation. This also fixes a typo in the original version. – Allow the user to specify any file as a user-defined property set file, instead of being forced to use the default name and location. – Increased the types of fields that can be used from the original 4. The full list is detailed in the DefaultUserDefinedParameterSets.txt file. – The Setup dialog for the export alternate UI has been split into 3 tabbed pages to make it easier to find and understand the export options. – Significantly improve performance when trying to export a highly-tessellated geometry. New Import Functionality:
– Add an “IfcMaterial” field that contains the material name(s) associated with the element. – Add an “IfcSpatialContainer” field that contains the name of the project, building, building story or space that contains the element. – Create multiple layers for simple cases of elements where IfcMateralLayerSetUsage is defined. – Import IfcGrids. There are some fundamental differences between IFC and Revit Grids, most notably that IFC grids are per-view, and Revit Grids are per-model. As such, there may be cases where some grid lines show up in more views than initially designated in the IFC file. – Improve healing and logging of imported solid data that is slightly dirty. This should result in fewer missing objects.
Import Bug Fixes: – Fix “missing” faces when elements were cut by openings and the IfcOpeningElement sub-category had its visibility turned off. – Handle unbound circles used for profile definitions in certain cases.
After joining and logging in, access the downloads section, download the ZIP file and run the EXE. You should be greeted with something like this as the Citrix hosted solution starts up:
Once you have joined and have access to Revit Skyscraper, please feel free to comment below and I can add you to a Sandbox Project I have set up, and also add you as a contact for chat. Have fun!
I recommend you join the project and read some of the early forum posts, particularly if you pondering issues of IP, who owns the model, permissions and the like.
I noticed these CIP folders were consuming huge amounts of space:
So, I basically deleted everything out of these CIP folders and freed up a lot of space. Upon restart, Navisworks re-created the necessary support files. The current path on latest Navisworks version is: C:UsersUSERNAMEAppDataRoamingAutodeskNAVMAN2015ENU6412.3.1157.50MC3AvroCIP
Close Navisworks, go to this CIP folder and select all – Delete. Send them to Recycle Bin if you are worried something will break. Open Navisworks, check everything is OK, then you should be able to delete them permanently.
These were the files:
Across various Navis versions:
Sometimes, when enabling and disabling CIP in Navisworks 2015, I will get a crash. Save before you do it!
Check it out, pretty amazing stuff. Take a virtual in-browser tour of Sydney Cricket Ground: SCENE Webshare Cloud
The implications of this technology for facilities management are pretty significant. In some cases, projects may skip the BIM process and go straight from laser scan to FM (where the brief allows for it).
Surprisingly, the model did not crash at this point.
Screencast below shows what happened when I tried to draw a section in this model. I had to click ok and then repeatedly smash Esc key to get out of this loop:
“This talk will cover some of the general principles of parametric design, and specific implementations of the principles in Revit via Dynamo. Attendees will come away with ideas about how Dynamo can be used in their offices, and resources for getting a deeper understanding of the application.”
