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.
It is Autodesk’s mobile-centric implementation of an integrated FM system… It hasn’t been around for long, but it already allows you to export Equipment directly from BIM 360 Field. It also allows you to view the equipment in context, and attach photos and other information.
It would seem like the current cloud model and sharing workflow from Autodesk currently looks something like this:
If you are having trouble getting a particular NWC uploaded to Glue, here are some steps to try:
you can open it in Navisworks, export to DWF and try Uploading that using the Glue client
you could open it in Navisworks 2015 and then Glue It from there. Unfortunately, there is no ‘Glue It’ addin available for Navisworks 2016. As I understand it, the new Glue sync features in 2016 mean that a simple Glue It button for Navisworks will not be available in Navisworks 2016.
Also, there are new addins available today (11 May 2015):
Firstly, make sure you have a model on Glue that you can access. Did you know that when you Glue something from Navisworks, it makes an NWD and puts it in a folder like this: “C:UsersLuke JohnsonAppDataLocalNavisworksPlugin63baac4b-76c8-4ff8-9039-d51645fd1ddc.nwd”
Once you have a model on Glue that you would like to download and use as modelling context in Revit, make a new Navisworks file and:
Append that model back to Navisworks from Glue (it will look like you opened an NWD, with Clashes, Search Sets and Viewpoints all appearing. This tells us that BIM 360 Glue stores all that information in the cloud, at least when the model “originated” in Navisworks.)
Make a new Revit file. I had problems using the Construction template – it seemed to break the coordinates somehow… In any case, when I just used “None” template, it worked fine.
Link the DWG into Revit, Origin to Origin
Do your Revit modelling (in the screenshots below, I modelled part of a roof)
Glue the new roof directly from Revit (you may want to Hide the DWG file prior to Appending). This will create a new Model. On BIM 360 Glue, you now have the original model plus this new model from Revit.
Go to Glue app in Windows and make a new Merged Model. Tick the boxes for the original model, and this new model from Revit.
Back in Navisworks, we can either choose to Append the entire new merged model, or just the new “piece” that we modelled in Revit.
Hear more about Autodesk® Navisworks® and the Glue Connection, including answers to these important questions: How do Navisworks and Autodesk® BIM 360™ Glue® work together? How can BIM 360 Glue bring value to my project? How does BIM 360 Glue integrate with other applications? Where does mobile app access fit into the workflow? To watch this on-demand webcast, fill out form at link below: Autodesk – On Demand Webcast: Navisworks and the Glue Connection