topic Re: Create .MOD files without including Hotlinks Modules in Teamwork & BIMcloud

Create .MOD files without including Hotlinks Modules

gdford — Tue, 22 Nov 2022 17:39:01 GMT

Is it possible to "Save As" a .mod module without automatically including Hotlink files that are attached to the project? The only way I see to do this is to remove the hotlink modules and then save out as as .MOD -- This sucks as a workflow!!
Any Suggestions?

Also - I have noticed that when I save out a .MOD file to my computer and then upload the .mod file to the bim server that when I go through the motions of updating the .mod file I saved to the computer the Save As goes through its normal process, but the file I am trying to over-write does not actually get overwritten... I assume this is due to some internal link between the bimserver version of the file and the original one on my computer.... I guess I need to delete the version from the bimserver first.
Any Thoughts on this??

Re: Create .MOD files without including Hotlinks Modules

Rex Maximilian — Tue, 22 Nov 2022 17:56:39 GMT

I guess you could "Select All" and then "deselect" (with grouping turned on) the hotlinks. Then copy to your clipboard and then "Save Clipboard as Module"

99% of the modules I save are from the clipboard, so maybe this solution would work for you?

Re: Create .MOD files without including Hotlinks Modules

vlahtinen — Tue, 22 Nov 2022 19:25:52 GMT

One option is to create a publishing set from floor plan views. Under the publishing settings of each item, you can choose to break hotlinks when saving the mod files. With Archicad 25 onwards you can also publish directly to BIMcloud.

Re: Create .MOD files without including Hotlinks Modules

PVBergkrantz — Wed, 23 Nov 2022 08:44:09 GMT

Breaking the hotlinks only embeds them, the objects in them are still included in the saved .mod-file but not AS hotlinks, just as normal objects. If the user would like to completely exclude the content from the hotlinks one method would be to do a publishing set for the mods, with a layer combination that has the mod master layer hidden.

Re: Create .MOD files without including Hotlinks Modules

vlahtinen — Wed, 23 Nov 2022 11:20:23 GMT

~~I used the wrong term. There’s an option to not to include hotlinks altogether.~~

Edit: Oops, I was wrong. The option doesn't ignore hotlinks, it works as you described. Also your method to ignore the hotlinks is valid. Sorry for confusion!

Re: Create .MOD files without including Hotlinks Modules

gdford — Fri, 25 Nov 2022 12:27:37 GMT

Hey - Thanks for the heads up on this. I knew breaking the hotlinks was not a solution and I had checked publishing a 3d view as a MOD, which is not available, but I never checked publishing from a plan view because I expected it would only publish from one story... Now I see the light!!! And now I can publish directly to Bim Server.... double cool and very much in my workflow. I love it!!
Thanks to all who contributed to this effort.

Re: Create .MOD files without including Hotlinks Modules

PVBergkrantz — Mon, 28 Nov 2022 16:20:52 GMT

Glad it was of help. Publishing mods is a powerful feature if you can get people on board with the workflow and use smart layer combinations.

Re: Create .MOD files without including Hotlinks Modules

Lingwisyer — Tue, 29 Nov 2022 01:56:28 GMT

Is it possible to isolate by a custom property via the Publisher? I had one project in which I was creating MODs by turning off all the mod masters, then selecting building parts via a custom property...

Re: Create .MOD files without including Hotlinks Modules

PVBergkrantz — Tue, 29 Nov 2022 08:41:12 GMT

I think not, the publisher basically uses views so only settings associated with that can be used, like layer combination or story. I guess you could do it semi-manually by setting up a find and select criteria, selecting, copying and using the save mod from clipboard, but that would have to be done story by story.

Re: Create .MOD files without including Hotlinks Modules

Marko Zeko — Thu, 26 Jun 2025 06:39:37 GMT

So this makes publishing modules useless - from floor plan.

In my example:

I have residential building with two apartments per floor.

I want only one to be published.

I put walls on layers by material and structural function.

So I end up with external and internal load bearing concrete walls on the same layer, while I want to export only internal walls and objects.

I could add additional story for modules to be published, but then I am not working in real environment (original story is just trace) and problem is with quantity take offs.

Is there any other way to isolate them? I am not planning to do layer combinations for apartment itself.

It would be perfect if it can be done from 3d, but problem would be if you add a new element and it won't be visible in 3d.

Re: Create .MOD files without including Hotlinks Modules

PVBergkrantz — Thu, 26 Jun 2025 07:35:18 GMT

You can't publish mod from 3d, it only works from plan. I think your best choice would be to split your wall layer into two, internal concrete and external concrete.

Re: Create .MOD files without including Hotlinks Modules

Marko Zeko — Thu, 26 Jun 2025 07:44:22 GMT

And splitting them to different layers raises possibility to make mistakes.

Then What about objects? or ig I have 10 apartments on one story then I have to have 10 sets of layers. This is really bad workflow. NO GO!

Re: Create .MOD files without including Hotlinks Modules

Lingwisyer — Thu, 26 Jun 2025 09:07:55 GMT

You cannot limit the storey range for quantity take offs? If that is the case, I wonder how the Iceberg hotlink method has survived... Maybe if someone who uses that method regularly has any input?

Re: Create .MOD files without including Hotlinks Modules

Lpalma — Thu, 26 Jun 2025 13:41:14 GMT

Hi, You can filter schedules by the hotlink's master layer or master ID, both of which can be configured from Hotlink Selection Settings. This way, you can segregate modules. This assumes you're quantifying from schedules.

Hotlink Settings

Re: Create .MOD files without including Hotlinks Modules

PVBergkrantz — Fri, 27 Jun 2025 07:54:23 GMT

The way we do it is to have one file for apartments, one apartment per story, exported to a mod file and then story by story into a master file. The same story from the mod file (that is, the same apartment) can be placed multiple times into the master file, rotated, mirrored etc.

The drawback is that you work on the apartments separately, not "live" in the main file, which is a shame but manageble. Like this you keep only one set of layers, but separate the "parts"/modules of your project by story.