NWF hangs when deleting appended files

[Anonymous]

I'm working with a .nwf file that has several .nwd files appended into it.  When I try to delete any of the .nwd files, I see the spinning "in progress" circle for hours (6 and counting).  The memory usage for Navisworks 2018 changes slightly over time, but holds around 10.6 GB while the CPU usage stays at about 17%.  I've done  a reboot and no other programs are currently running.

Any ideas on why Navisworks won't delete the appended .nwd from my .nwf?

Thanks,

[Patrick_Aps_9121]

No,

But a workaround would be to rename the NWD you want to delete before opening the NWF.

Then, when you open the NWF, the missing NWD causes an error message.

You then should resolve the missing NWD to a tiny NWD on your C:\ and after that, you should delete that tiny NWD.

If you press ignore on the error message, the NWD seems to have dissipated, but there still seem to be entries pointing to that file in the NWF. (you need API to see them, but you cannot delete them with API)

And it might be the case that when you rename the NWD back to it's original location and filename, the NWF will show and/or access this NWD again.

[Anonymous]

Patrick,

I have 40 NWD files in my NWF and I only need 6.  It seems like an inefficient method for deleting files.  They seem to get deleted after about 12 hours or so, but that is too long to wait for each one.  I can delete an XRef in AutoCAD in less that a minute or break a link in Revit just as fast.  Why is it such a problem with Navisworks?

[chris.leighton]

I have the same problem. When I try to delete DWG, NWD or NWC files from my NWF Navisworks actually crashes completely. There has to be a solution for this. Why even have the option to delete? And the workaround proposed seems absurd.

[Anonymous]

I think there is no solution to this.

It's now September 2020 and I am sitting here watching the spinning wheel while Navisworks deletes NWC files from the selection tree.

There should be a replace file option in this app.

[Mohamed-Nassar]

Use Merge when u work with NWD file this is the best way to work with NWD to replace as u need with out any problems.

[Anonymous]

Having the same issue often with dwg files. What worked for me was:

-Select the file to be deleted

-Hide Unselected

-Delete 

-Unhide all

[mpriestman]

I'm not sure why Navisworks would be hanging when trying to delete a file. Do you have a lot of saved viewpoints in your model? And what source CAD application did the NWDs come from?

It possible, are you able to force a CER when it has hung and let me know the CER number? Then I can have a look at see what NW was actually doing at the time.

To force a CER, hold down CTRL + ALT + CAPS LOCK for at least 5 seconds, and a CER window should appear. Enter a comment saying what you were doing and after you submit it you should get a CER number you can reply with.

Michael

[Anonymous]

Hi, I have the same issue. Deleting a large NWD from an NWF takes practically forever (hours, days?). Windows reports Navisworks has stopped responding during the deleting process.

Renaming or removing the appended NWD in Windows explorer, then refreshing the NWF allows deletion (detachment) of the NWD instantly.

Tried in NW simulate 2018 and 2020.

[o.abdelghaney]

Trying to delete appended .nwd files from the .nwf file does usually work but can take a very very long time. A useful workaround is to go the original .nwf file, go to the 'batch utility' under the home tab. In there you will find the appended files as file paths. Select the file paths of the files you want to delete and click on 'remove item'. Below that for the output select the 'as single file' tab and choose where you want to save this new file. At the bottom hit 'run command' and wait for it to complete the process. This will create a duplicate of the original .nwf file but now without the files you wanted to delete. You can then rename/replace the original .nwf file as needed. This usually takes minutes to complete as opposed to the very time-consuming process of deleting the appended files.

[Mohamed-Nassar]

i think you have no problem with NWD as standalone file but ram consume this storage because this is the function of ram it save the file in RAM may you need to open it again and in this case it will open or upload quickly instead of first time to open r upload, may navisworks delete this file from nwf from selection tree you can choose them and delete inside navisworks and save it.

[Mohamed-Nassar]

you can't do this with multiple select quick properties working without select any element it works when you be on the element without select it when you select element the info will appear in properties tab but not for multiple elements

[ilya-frumkin]

 Hi Michael ( @mpriestman ), 

I hope you can still follow this thread, as I have a CER number for you, for the same issue still happening using Navis Manage 2021:

CER #:  326420935

[mdrahilahsan]

thanks! it worked for delete part but all the view points saved in nwf file seems lost their coordinates. can you please help me on this part?

[loki.law.lhk]

small update here

It's now J,ul2023 and I am sitting here watching the spinning wheel while Navisworks deletes NWC files from the selection tree.

[ppourmand9FBP3]

Same here. August 23, and any appended model takes for ever to be removed from the model. Even though no test or view points are linked to it. 

[robert.levyWUHML]

I might be wrong here but...It's a problem because Autodesk doesn't want to redo Navisworks source code that is decades old. There is no return on investment for Autodesk. Autodesk would rather invest the money into marketing to get new customers than to fix something like this which won't increase their stock price.

[Sæmorr]

Does this still happen in Navisworks 2024?

[Eric.Johnson-3DBIMworx.com]

Yes.  The reason is simple.  Autodesk is not a software company.  They do not create, develop, or improve software.

They are an acquisition and marketing company.  They buy software someone else created, market it, sell it at a ridiculous profit until someone develops something better and then the process repeats.

[robert.levyWUHML]

I'm still scared to use 2024. IT is still the case in 2023 though.