Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Support cloud path (Desktop Connector) for Navisworks (NWD and NWC) links
Currently RVTs, DWGs, keynotes and assembly codes are supported for cloud pathing (Autodesk Desktop Connector). NWD and NWC links are currently not supported for cloud pathing.
For searching, the words Coordination Model in the title would help We had a customer who could not find this to vote. We added the tag Coordination Model also to help.
I agree. All files that can be linked into Revit, and can be stored in BIM 360 should have Cloud Path. It is not very useful to have my username in the filepath when linking nwc/nwd.
This shouldn't be something we even have to vote on - this is a pretty glaring omission in the Revit/BIM360 interoperability that needs to be rectified.
I was hoping the last update with the folder name change would have resolved the issue but it didn't.
I agree, we shouldn't have to vote on this. We should be able to specify the folder location. Specifying the folder should be through deployment so we can ensure all our workstations are set up the same.
Came here to reiterate the point everyone has been making, this seems like an easy fix for Autodesk to implement. This will be the final element of getting us off of Sharepoint for cloud hosting files that need an absolute file path.
Pathing every machine in our office to Sharepoint/OneDrive has been successful this far but adds points of failure. Also it adds the task of having to download and upload the latest models from other trades. It would only make sense to be able to path coordination models to BIM360.
Gathering Support for 5 years seams like this idea isn't getting any traction at all. Come on Autodesk, changing a path shouldn't been this hard. Divert some resources from ACC for 2 days and that should do it!
Almost five years later and still no support? This is something DESPERATELY needed as more and more firms are moving files to BIM360/ACC. It makes no sense to tell users to path everything to the cloud except Navis Coordination models. Not every partner on a project uses Revit or even an Autodesk Product leaving NWD's as the only legit option to use to coordinate with inside of Revit.
It's almost like they heard me. The latest Desktop Connector (15.6) allows a custom local workspace to be created. I tested this and it has promise. Basically create a common local BIM 360 folder (we used C:\BIM360). Set desktop connector to the new local workspace and then link your coordinate Navisworks model into Revit that way. Each user has to setup this up (once) for it to work. But so far it avoids the broken link error.
Yes, we can now have a common link to a local drive, BUT, Desktop Connector does not autosync/update Coordination Models like it does for RVT or DWG files that are linked in through the Desktop Connector.
The local files have to be manually synced every time they are updated by each user or they will not have the latest files.
Currently, when linking Coordination Model NWC and NWD files through the Desktop Connector the files do not Live Update like a linked DWG, RVT or IFC linked file.
We have multiple users working in a Revit model that has many linked Coordination models. We need to host these models in Autodesk Construction Cloud so that we can use them as links in our Revit model and as Clash Models for use in ACC Model Coordination. These files are updated on a weekly basis at a minimum.
We had hoped that when we could change the Workspace of the Desktop Connector to a common path on our local drive, this would solve the problem, but it does not. It does solve the problem of the links being broken because the files were pathed to the users local cache and now they can be pathed to a common drive designation, but, the files do not automatically update and have to be manually synced with every update.
This causes a tremendous drag on our workflow and can cause issues if a user does not sync and have the latest models available.
