Navisworks 2017 not seeing Fabrication 2017 items

regal180 · ‎11-22-2016

Help

markcalloway · ‎11-22-2016

Hi,

Please install the Fabrication Object Enabler, this should resolve this issue:

https://knowledge.autodesk.com/support/fabrication-products/downloads/caas/downloads/content/autodes...

Regards,

________________________________________________________________________________
If you find this post helpful, please LIKE.
If you have solved you issue please mark as ACCEPTED SOLUTION so other forum users can see how to fix this issue.

Follow me on Twitter / Follow me on Linkedin / Blog

regal180 · ‎11-22-2016

The OE won't install. We're using Autocad MEP / Fabrication and Navis 2017 and it won't install overtop of our 2017 programs.

RobertAGlover · ‎11-22-2016

How are you bringing the Fab models into Navisworks? Are you linking in DWGs, exporting NWCs, or some other process? Does the computer your using to append the DWG into Navisworks have the Fabrication CADmep loaded and installed?

If you want to send me the file I can take a look and see if it works for me. Thanks.

Robert Glover
VDC Manager

regal180 · ‎11-22-2016

Yes we are loading a DWG and yes the system has fabrication 2017 loaded on it. This is a brand new computer we're setting up for one of our detailers.

RobertAGlover · ‎11-22-2016

Can you send a screenshot of the DWG settings from Navisworks (N>Options>File Readers>DWG (and the Convert Object Properties subsection)?

Also if you are opening Navisworks and appending the DWG from fabrication, try exporting from FabCADmep to a different format, DWF or similar then append that into your model. One option is you could export to MAJ, import MAJ into Revit, then link the Revit model. Unfortunately Revit doesn't read MAJ (wish it did).

Robert Glover
VDC Manager

regal180 · ‎12-05-2016

Just a follow up on this problem. We tried every which way of installing the 2017 Autocad MEP with the Fabrication CADMep and Navis Manage 2017 and could not get the Navis Manage to see the Fabrication items at all. Like the object enabler was the issue which we have seen many times and been able to fix by loading the DBX.

Mind you this was a out of the box brand new Dell 7710. Seems the Autocad keeps many registries stashed all over the place that the uninstall doesn't remove so we kept having the same issue over and over so we finally did a full re-image of the new computer then re-installed Autocad Mep, Then Fired it up and made sure things looked correct then added the Fabrication and did the same. Once the Autocad and Fabrication looked good we installed Navis Manage last and things works right off the bat.

Bottom line is be sure you install the Navis last when using Fabrication.

Thanks for the help.

RobertAGlover · ‎12-05-2016

Glad you found A solution. If it continues to be a continuing problem, I think we should try and trouble-shoot to see if we can find a way short of a complete wipe and reinstall? Thanks.

Robert Glover
VDC Manager

bjwardlow · ‎03-22-2017

I am having this issue as well. I was using Navis 2016 and am using Fab Cad MEP 2016. I recently purchased the AEC and got Navis Manage with it. I downloaded Navis Manage 2017. It works fine for Navis files that I get from others, I can see all objects, even my own Cad MEP items I have sent to the general contractor to be included in their model. When I try to merge or append my duct into the model, it does not show up. I never had this problem in 2016, but I just opened it and tried it to see if I could keep going while looking for a solution. It is now doing the same thing. I downloaded the 2017 Object enabler, do I need to download the 2016 object enabler since I am using 2016 Cad MEP? Or is it a completely different problem? I really don't want to have to wipe my whole computer and re-download everything.

MOatman · ‎03-22-2017

Installing the 2017 Fabrication object enabler should be all you have to do. This happened to me recently with 2017 Navis and it was because the object enabler was not updating the registry properly.

The path location to dbx file was wrong in my registry.

The key location in registry is here:

HKEY_CURRENT_USER\SOFTWARE\Autodesk\ObjectDBX\R21.0\Applications\Maps_Solids

Make sure the Path in the LOADER value is pointing to the location of the dbx file installed by the object enabler.

My path is set here:

c:\program files\autodesk\fabrication 2017\cadmep\cadmep21_x64.dbx

Anonymous · ‎04-24-2017

I am having a similar issue. I can not open a Fabrication MEP 2016 file in Navis 2017, but I can in Navis simulate 2016. Thanks In advance.

bjwardlow · ‎04-24-2017

Here is the response from TSI on this issue, it worked for me:

Do me a favor and open up the drawing in CADmep.

Then go to the Main Database->Takeoff->CAD Setting and check Save Graphics with Drawing.

Then Save the drawing and you should be able to see those items in Navis.

Also you would need the 2017 Object Enabler installed.

Anonymous · ‎04-24-2017

Thank you, It worked for me as well....

Anonymous · ‎04-24-2017

Yeah that sounds like a typical TSI solution. You may as well go ahead and put in your next support ticket in for why the size of your models have all doubled. Hopefully you don't need to post things for coordination....

RobertAGlover · ‎04-25-2017

File size is pretty important in Navisworks. We export out our NWD and our field guys use that with BIM 360 Glue to view the model in the field. However Glue apparently has a ±50MB file size limit. As such I've had to be very picky about what I include in my models.

Back to the issue at hand...

Have you tried to reinstall the Navisworks Exporter? Go to the control panel > Programs > search for Navis > find the relevant version of Navis exporter > Uninstall/Change > Repair or Reinstall > Reinstall

If it doesn't work rinse and repeat with the full Navisworks.

Robert Glover
VDC Manager

Anonymous · ‎06-14-2017

@MOatman wrote:
Installing the 2017 Fabrication object enabler should be all you have to do. This happened to me recently with 2017 Navis and it was because the object enabler was not updating the registry properly.

The path location to dbx file was wrong in my registry.

The key location in registry is here:
HKEY_CURRENT_USER\SOFTWARE\Autodesk\ObjectDBX\R21.0\Applications\Maps_Solids
Make sure the Path in the LOADER value is pointing to the location of the dbx file installed by the object enabler.
My path is set here:
c:\program files\autodesk\fabrication 2017\cadmep\cadmep21_x64.dbx

Moatman,

This was exactly the problem with our install. I came here looking for a reason why someone with Building Design Suite 2017 and Fabrication CADmep 2017 installed on their computer couldn't see Fabrication objects in Navisworks Simulate 2017.

When I went to the location in the registry editor that you mentioned, our LOADER path was incorrect. It had added one additional folder level so it read "c:\program files\autodesk\fabrication 2017\cadmep\DBX\cadmep21_x64.dbx". I eliminated the "DBX" folder after verifying that your suggested path was correct, and it worked perfectly upon reopening Navisworks.

Thank you very much for this solution.

[Edited to include quote]

Anonymous · ‎07-11-2017

I have had that issue multiple times. I found the fastest way to fix it is to uninstall Fabrication and reinstall it. When you are setting up a computer and installing Autodesk software, be sure fabrication is the last thing you install. But if you install fabrication before Navisworks then it is a 50/50 shot if your items will show up.

RobertAGlover · ‎07-12-2017

I find it annoying how order of operation is so critical when installing Autodesk software. I understand much of it, but it's annoying. This is made worse with the new collections (AEC Collection is my experience). I am currently putting together the process order for removing and reinstalling all of our Autodesk software. Because we use standalone licenses, I have been informed that we will have to uninstall our existing software suites and reinstall the software one program at a time. The up side is it allows us to only install the software we need and easily add software at a later date without downloading the entire suite install. But the downside is that I have to make sure my order of installation is correct to ensure inter-program cooperation.

Joy be to the Autodesk.

Robert Glover
VDC Manager

jrogershmcc · ‎04-10-2018

This was the fix for me. Thanks!