I typically convert IFCs using the Link method, which results in DirectShape objects. It seems that one of the Architectural files that I converted this way from ArchiCAD to Revit and then to BIM 360 Glue was stopping the colours from getting baked into the BIM 360 Shared View.
To workaround this issue:
Determine what problem model/s you have (possibly those converted from IFC)
Open your Merged Model in Navisworks for BIM360
Hide these problem models in Navisworks scene
Run Appearance Profiler or otherwise apply colour overrides
In the BIM 360 Shared Views pane, click New to make a new Shared View on BIM 360 Glue with the colours ‘baked in’
Go to Glue desktop app and confirm the colours are working
Then, Unhide the problem model here…
And then make a new view in the desktop app
This new view should have all models you want showing, and the colour overrides working ok.
On a related note, you may have seen this warning:
View in model is still processing and some items may not be overridden
It seems that this might put your Glue merged model in a dirty state? Try deleting all views with this message before trying to create Shared Views from Navisworks with colour overrides.
The fact that I’m posting about it means that it probably isn’t really that easy, right? There are a few challenging pieces of the puzzle that all need to come together to get C4R or Collaboration for Revit working on a real project. I just went through this process with a mechanical firm so it is all pretty fresh in my mind.
Firstly, note that A360 Team has been rebranded as BIM 360 Team and will be migrated, more details at this post.
Secondly, Autodesk really wants your whole team (like everyone, every consultant, every Revit link) on Collaboration for Revit. However, out in the real world it is just happening bit-by-bit, and in the meantime some hacks and workarounds can make the process a little bit easier.
A Quick Overview
Ok, so Collaboration for Revit runs on top of BIM 360 Team. What this means is that you need to have an active BIM 360 Team license if you wish to run projects. Then, you need a Collaboration for Revit license for each Revit user who will be connecting to that BIM 360 Team site. You still with me? This also means that persons outside of your firm may connect to your projects, provided they have their own Collaboration for Revit entitlement applied to their Autodesk account.
Once you have the BIM 360 Team license, and the Collaboration for Revit licenses, you then need to “Assign” the Collaboration for Revit licenses out to the users (using their Autodesk login details).
Finally, you need to actually do some stuff, like:
make a BIM 360 Team project,
invite the users,
initiate Revit models, and
get the links working.
Its a lot to take in, so you can see that the blog title is actually a half-joke 🙂 However, we were able to get all this up and running in about 4 hours for one firm, so you can too. Hopefully. Something that will help
Given that there are a lot of moving pieces, I turned to my favourite research and documentation tool, OneNote. I have created a public notebook that you can view at this link: Revit Collaboration Public Help
Basically all of the steps involved in getting the licensing setup, inviting users, installing the addin, and initiating models onto Collaboration for Revit are in the notebook linked above. I will continue to update and add to this over time.
Just comment to this post and I will endeavour to answer your question in the notebook, or point you toward the answer.
Now, here are a few other bits and pieces that may be useful, if the notebook doesn’t answer your questions…
Sometimes in Glue addin for Revit will fail with the message “Oneormoregluingerrorsoccurred“.
You may be able to workaround this problem by following these steps:
After receiving the error, immediately browse to your Temp directory. To do this, open Windows Explorer and type %TEMP% in the address bar.
Sort by Date Modified
Look for a DWF or NWC that matches the View Name that failed to Glue in Revit
Grab that file, and remove the suffix (usually a few digits) so that the DWF Filename = View Name = Glue Model name
Using the Glue desktop app, upload that model manually
Renamed model ready for upload
This process opens up an interesting possibility… usually when exporting a DWF using plain Revit, it will always use Project Internal coordinates. However, the Glue addin can actually export DWFs with Shared Coordinates (if you choose that in the Glue export More Options dialog).
Using the above steps 1-5, you can ‘find’ this DWF with Shared Coordinates and use it wherever you please… such as in Navisworks.
Interestingly, there is some talk of a completely free offering, after the free preview: Autodesk is now accepting reservations for a limited release and free preview version of Autodesk BIM360Docs at www.bim360.com/docs. The product is expected to come to market in early 2016. In addition to the free, limited version of BIM360Docs, Autodesk will offer the option to subscribe to additional capabilities that scale to meet more advanced needs of construction firms. The product will initially be available in English only.