Quick Tip for Publishing Hotlinks in Large Projects

Just recently came across this issue that unit modules were meant to be linked into a block file, but due to the large amount of small variations within the units, the designers wanted to have a base module to link into the unit file as well, such as:

Module A is linked to the Units file onto different stories. In the Units file, small variations are added to the base A, which eventually results in Unit A1, A2, etc. Similarly with Unit type B, C and so on. Eventually the Unit file was linked story-by story into the Block file.

Though from attribute management point of view such amount of hotlinks is not easy to manage, the designers preferred this solution to deal with the frequent design changes of the 30+ unit types. At the end of the linking process the problem was, that since the Units file already contained more than 20 hotlinks, the total number of links significantly increased in the master file, which caused slowness in general, for scheduling, for updating the links and so on. If the Units file could have been a single file without previously added links it would have been much easier to handle. To overcome this issue, a tiny, but very powerful function of the Publisher was activated: Break nested Hotlinks and Xrefs.

37_embed links.png

Whenever publishing modules – in this case every story that contains one unit type was published as a separate module -, using the embedding function under Options… allows us to get rid of the excess links. At the same time the designers could still use the Units file for doing their work, but the process was not hindered later either.
As an additional benefit, the published modules only need to be linked once into the further files (typical stories or directly into the block), whenever there is an update, they just publish again with a click and update the links.

Advertisements

IFC Export of Migrated/Linked Projects from ARCHICAD 21

Forward migration is usually relatively smooth with ARCHICAD nowadays, but if it’s paired with some hotlinking and IFC export then the new features might cause some confusion.
Two of the latest additions to ARCHICAD are the introduction of Classification Systems and the improved IFC Translator settings, which both provide a lot of opportunities and smart management functions for the user, but during migration+hotlinking+IFC export they will need some extra cautiousness, otherwise the user might get unexpected results. Even though this might not be a mainstream case, we just had a few support issues in Singapore because of this, so let me give a generic explanation, hoping to clear up the confusion as much as possible 🙂

Read More

Breaking Hotlinked Modules in Teamwork

When having Hotlinked Modules in Teamwork projects you might have run into the problem of not being able to break the hotlinks as in the solo projects. Reserving the modules and/or the Hotlink Manager dialog itself doesn’t solve the problem either, the Break Hotlink button is still greyed out…

bhl01

The reason why this just stopped working after ArchiCAD 17 is purely technical and intentional by GRAPHISOFT, therefore there is an alternative solution for this sought after function.

Read More