Freedom Autodesk

[Jason]

I am having a problem where I have a point cloud attached to my drawing and it shows up fine when I open the NWF file in Simulate, but when I save it out to an NWD file so the client can see it with freedom the point cloud shows up as a bunch of boxes instead of points. I have included a screen shot, where I did a saveas from the NWF file to a NWD file and then reopened that NWD file with simulate and instead of showing up as points they are showing up as a bunch of boxes. I assume that I am doing something wrong when I save it to a NWD as I have seen other NWD files that have the point cloud information in them so I know it can be done. Any help would be greatly appreciated.

2. When I published it then the resulting NWD file would open on my machine with the point cloud displayed using Simulate but when the guy sitting next to me tried to open it with Freedom it still displays boxes instead of points.

That would be fine if it were my people doing the review. I can not tell the client that they need to upgrade their software. They have told me that I need to put it out in the 2014 NWD version, so my question remains is there a way to do that?

If the NWD is for internal use only, you could append the cloud using an UNC path that is accessable to every user and then try to use the Project Link instead of Voxels. Then the cloud is not embedded in the NWD, but the link to the cloud is.

I tried all of the recommendations and I can not get it to work. Changing from Voxels to Scans does not appear to change anything with regard to the problem I am having. I can not use the links option, as I need to send the file to clients offsite.

An interesting side note when I do the save as and go back to the 2014NWD it will create the 2014 version and it will have the point cloud displayed as long as I still keep the file open but when I shut it down and reopen the exact same file with the exact same program it will not display the point cloud.

The Navisworks Coordination Issues Add-In with Navisworks 2024 further extends connection to the Autodesk Construction Cloud, now providing cloud managed Navisworks data enabling multi-user participation on desktop. Save and edit Model Coordination aggregated Views directly from Navisworks. Automatic NWF management facilitates multi-Navisworks user workflows and includes Navisworks-data merging.

The Model Coordination app with the Autodesk construction Cloud enables creation of coordination spaces with the auto-clash process disabled, benefiting Navisworks users utilizing Clash Detective. These spaces provide direct access to latest model versions published to Autodesk Docs.

While using find items in Navisworks to define search sets, two 'AND' conditions do not work. Only one condition can be satisfied. Critically, I have used the same search sets on the same NWF with the same NWCs linked from the local drive - the conditions work fine.There looks a bug or some change in metadata meaning stacked 'AND' conditions do not work when files are linked through model coordination? Is there a solution to avoid to avoid making search set redundant and thereby revising the whole clash process via navisworks- otherwise we will not be able to uwe the add-in

Constant issue even before the latest update. The ACC issues are not showing. Each time it take 15mins to reload navis (due to over 370 models on this project), this is now affecting the modelling production and clash checking.

1 - Currently, you must select the clashes, then right-click to create issues from clashes. It would be great to create batch issues across multiple clash tests, e.g. from all new, or all active, etc. If so, the BIM Coordinator could go quickly through the clashes to filter out the false positive, then, at the end of the process, create all the clashes from the new or active ones. It would be great to have a panel where assigning an issue template for each clash test. That would incredibly speed up the process, as common workflows define the clash tests so that all the clashes in that specific clash test are assigned to the first model.

2. It is critical to create a clash-issues synch feature, so all the clashes geometrically resolved can be automatically marked as closed (or assigned a parameter, should the BIM Coordinator want absolute control on closing them). Manually closing issues is a very tedious process, and should be left for "custom" issues created by project memebers, not by Navisworks.

100% behind your comment. There is minimum integration with issues and clashes- which is what model coordination is for...how was this missed? And Issue pins XYZ or basic clash report exports are lacking in model coordination. If it is supposed to be Navis replacement for those who do not have the software, at least provide the basic clash features and ability to save tests and export results properly. Max The limit of 100 issues published from clashes is relatively low, and should be increased up to 500 minimum.

The plug in Locks up all sessions of Navis Manage now. In other words if one session is locked up (refreshing files or appending files, even Upating clash test), all open sessions will lock up until refresh or append is completed. Please help.

It would have been nice to have a "next issue" button when you have an issue open so that you don't have to scroll down the list to find the next issue. It would also have been good to have an option to move the pushpins if they are in the wrong position.

-there is an issue where clash viewpoint locations are lost and change. It might have to do with model locations moving. Another thing that doens't happen in BIMTrack. Please associate the viewpoint with an XYZ location NOT a model location which causes problems.

-Also you cannot update the location of the viewpoint after creating the issue. this has huge impacts because the point of using issues is that you have a history showing issue creation date. we cannot afford to have to re-create an issue just because we cannot update a viewpoint location. don't tell me to update it in the web interface because that doesn't work either. Too time consuming to go back and fourth and it doesn't actually update issue viewpoint.

-This plugin needs a separate window for viewing images. When you view images in it it expands the interface large and then we have to keep messing with the palette size every time we look at the images attached. This issue is already solved in BIMTrack

-This plugin also needs a way to send clashes to issues and bring them back from issues back to the clash detective, BIMTrack has a lot of this figured out, but if Autodesk is going to compete with BIMTRack, then you should find a better way to do this. You are a 1.27 billion corporation.

This Version 2.9 is not showing in the Navisworks model all the BIM360 issues created on the cloud platform. Previous version 2.6 allows the visibility of all the issues created on the cloud platform and the Navisworks model.
How can I get an older versions of the add-in? I need that 2.6 version.

-Update: After Installing & trying the new release, the issue was fixed.
Thanks

Are you working at all towards being able to integrate a BIM360 hosted point cloud? Not having a web based point cloud incorporated makes it difficult for several companies working together on a project to collaborate.

We lose our colors when appending files through Coordination. It also doesn't refresh when we re-export to NWC from Revit. We have to close out of the Navis file and re-open it, whereas the default Navisworks automatically refreshes models once exported.

The way issues are tied to a specific element in a specific model means that with new versions of the model sometimes the issue disappears. I understand the intent is to tie an issue to a specific model element, but drafters often delete and remodel entire sections of scope, which changes the GUIDs and disociates the issue from that point in 3D space. This is very frustrating because you then have to find the issue list online and manually locate the issue based on a screenshot or description.

Hello Colin, while the issues are referenced to specific objects in the view, deleting that object would not cause the issue to disappear. The issues are tied to specific 'views' within the model however, and if that has been removed or changed names then the related issues may only appear in the project issues list. If you are having problems, please open a support case so we can determine the root cause.

This can happen if you are not on an updated version of Navisworks 2020. Please install the latest 2020 Update in order to solve this problem. After installing the update, you may need to right click in the gray area of the ribbon and set the Coordination panel to visible.

Great plug in for navisoworks, but should be really helpful if you have and snip tool to load snapshoots from the model, and load directly to the issue, because im other way we need to create the snip, then save in a folder and load to the issue.

This is a great add-in but i am missing an important feature, which appears to be in earlier versions of the plugin (or at least when it was called B360 issues) - Templates. My version does not allow me to use template. Is there a reason this functionality is not in here anymore?

This plugin has made a HUGE difference in how Barton Malow handles model related issues. The only issues we've really seen is when multiple users are adding issues in the same NWD and they are using different versions. Easily fixed by updating the plugin but it requires a manual version check. Autoupdate would be great!

We have improved the way we handle properties for models loaded from Model Coordination in Navisworks 2022 and Navisworks 2021 Update 2. If you could try updating to one of those versions, hopefully that should improve things (note that if you upgrade to Navisworks 2021 Update 2, you will have to explicitly check the "Convert Properties" option in the Global Options -> File Loaders -> SVF section).As for the structure of DWG files, they are presented exactly as they are shown in BIM 360 Docs. Navisworks has no control over the structure of the files as they are processed by our cloud services, and not Navisworks.

c80f0f1006