Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Hyperlinks in PSet-Properties: Navisworks doesn't resolve filepaths correctly

cwr001
Collaborator

Hyperlinks in PSet-Properties: Navisworks doesn't resolve filepaths correctly

cwr001
Collaborator
Collaborator

This topic has come up in some shape or form several times but unfortunately I couldn't find any working solutions so I'll ask again, hoping for some insights:

In Civil3d I've got a 3d-Solid with an attached propertyset and some properties.
One of those properties is an absolute filepath (type: string) that, in this example, references an image:

c3d.png

After exporting, I can open the IFC in Solibri where everything works as expected and the hyperlinks are even clickable:
solibri.png
Opening the same file in BimCollab Zoom, everything works as expected and while not directly clickable, I can open the image with a right-mouse-click -> open.

bimcollab.png

In Navisworks however, my string isn't escaped correctly and I get a hot mess that looks like this:

navisworks.png

I've tried a couple of things, but no matter what, I can't get the string to display correctly:

Not working:
D:\MyTestImages\IMG_8071.JPG
Also not working:
D:\\MyTestImages\\IMG_8071.JPG


Does someone know what I have to do to make Navisworks recognize filepaths correctly?
I wanted to test @brett_parkerLUEP7 suggestion here that "Properties Panel Enhanced" makes hyperlinks clickable but as shown above, I can't even get Navisworks to display a path to begin with.

0 Likes
Reply
658 Views
7 Replies
Replies (7)

brett_parkerLUEP7
Community Manager
Community Manager

Hello,

 

Would you be able to share the file with me directly. This can be done by emailing me privately via brett.parker@autodesk.com

 

Regards


Brett Parker
Navisworks Product Manager
0 Likes

cwr001
Collaborator
Collaborator

Thank you for your response! This issue is easily reproducible and not just occuring in one file. For reference, I've attached testdrawings for Civil3d 2023 and Civil3d 2024 - it doesn't work with either version.

 

In Navisworks I'm currently on:

Navisworks Manage 2024 (64-Bit)

Version: 21.0.1397.16

brett_parkerLUEP7
Community Manager
Community Manager

.


Brett Parker
Navisworks Product Manager
0 Likes

brett_parkerLUEP7
Community Manager
Community Manager

Hello,

 

Having completed further tests, I can see the path now works. If the path is not valid or doesn't exist then it won't become a hyperlink. If the path does exist then the hyperlink should work;

 

brett_parkerLUEP7_0-1706625664674.png

 

I am not able to recreate the issue where the / is missing. Can you provide a file with this issue present?

 

Regards

 


Brett Parker
Navisworks Product Manager
0 Likes

cwr001
Collaborator
Collaborator

Thank you for looking into this.

That's curious - your hyperlinks seem to get resolved correctly with "\" between folders. When I load the prior attached files, those "\" disappear in (my) Navisworks. Maybe it's a setting somewhere?

 

I've screencasted my exact steps just to show the whole process - I'm using the files that I've attached in the above post.
- Export 3d-solids from Autocad
- Import into Navisworks (where you can see that the filepaths come in without backslashes)
- Import the same file into Solibri (where it works)

 

0 Likes

brett_parkerLUEP7
Community Manager
Community Manager

Hmmm, that is unusual. Are you able to uninstall the enhanced properties add-in and reinstall. Latest version can be got from here.

 

Alternatively, you can check the version via the Windows uninstall apps;

brett_parkerLUEP7_1-1706628105395.png

 

It is also worth deleting all the related files in the directory - E.G NWC, TXT and HTML files

brett_parkerLUEP7_0-1706628000827.png

 

Then reload the original IFC and see if it now resolves the link.

 

Regards

 


Brett Parker
Navisworks Product Manager
0 Likes

cwr001
Collaborator
Collaborator

I've done a whole reinstall of Navisworks, unfortunately, the bug still occurs.

Is there a chance it has to do with language-settings? I'll maybe try installing the english-version later.

0 Likes