Project data & BIM
About BIM-based management of attributes, schedules, templates, favorites, hotlinks, projects in general, quality assurance, etc.

Problem Hotlinking Module

Anonymous
Not applicable
Hi!

I seem to be having problems hotlinking a .mod file into my model. After selecting the file as a new hotlink and selecting a multi-storey hotlink, the OK button gets greyed out.

I can hotlink renamed copies of the file, or the file in a different location but not that file with the name in the location it needs to be.

The first thing that came to mind is that the module file is already hotlinked into the model but I can't find it in the hotlink tree. Is there any chance that the file was linked previously and the link broken but somehow there's something that tells AC that it's still linked?

Cheers!
8 REPLIES 8
Laszlo Nagy
Community Admin
Community Admin
I can think of two things:
1. Maybe the name of the file plus the name of the folder it is in gives you a path name that is too long?
2. Maybe there is a character in the name of the file that ArchiCAD does not like?
Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28
Anonymous
Not applicable
Did you resolve this?

I'm having exactly the same issue. In this case, I know for a fact that the hotlink has previously been linked into this project, successfully, and that neither the name nor the directory have changed since the last time the hotlink was successfully linked to the project. As far as I can tell, the hotlink was not deliberately deleted from the host file, but is no longer listed as a linked hotlink. It just seems to have disappeared from the host file, and there doesn't seem to be a way to get it back.

If, as you suggest, it's a problem character in the hotlink's file name, it's something that was changed with the build 5005 update, as everything was working fine before that. Is that possible? There is a "(" character in the file name, however as I said, it was working fine until recently.
Anonymous
Not applicable
I did a little test, and while renaming the hotlink does work, it makes no difference whether it's with the "(" or without. So it's not a character issue, in this case anyway.

So I guess the workaround is to simply rename the hotlinks and put them back in, however there's obviously a bug here that needs to be fixed - AC can't just go around dropping hotlinks out of projects all the time!
Anonymous
Not applicable
Thanks Laszlo,

I don't think that's the problem as the same mod file has been dropped in as hotlinks into various other models. Right now we're just doing a rather dangerous workaround by making a copy of the module file with a different name and hotlinking that in. We just have to remember to update the copy as and when there are changes in the original module file.
Laszlo Nagy
Community Admin
Community Admin
For what it's worth, I am going to report this to Graphisoft.
They might have some ideas about what causes it or if not they now know there may be an issues here.
Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28
Anonymous
Not applicable
We had the same problem only yesterday. It is an intermittent occurrence so just copy & paste the grouped mod out of your template, it will remain a mod. and will appear in the hotlink manager. It will also come in as multi storey provided the mod is not broken in the template
Anonymous
Not applicable
Well, you can use Long Path Tool for such issues, it works.
Anonymous
Not applicable
My colleagues and I are all having this problem too. It''s happening randomly on single and multi-storey hotlinks. It tends to be the case that only a single story within a file will refuse to allow itself to be linked.

We did a screen recording of it not working (not sure I can post that on here) and put it to Graphisoft and got this reply...

"Unfortunately the development team could not reproduce the phenomenon. Development couldn't get out any information from the log files, but during this operation there are no logging in the system. Although the client could try some old tricks that might work? Try to rename the files (maybe foreign characters interfere with the operation somewhere), or move them to another path."

As previous posts suggest, renaming works but it has nothing to do with foreign characters etc.

(We're using v17 on Mavericks)