topic Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module in Modeling

Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

rob-faam — Wed, 24 Sep 2025 08:24:38 GMT

Since the 6003 update, Archicad crashes when trying to copy parts from a hotlinked module.

(Groups suspended > select one or more elements from the hotlink > ctrl+c > ctrl+v > crash)

Please fix this urgently!

Operating system used: Windows 11 23H2

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

Laszlo Nagy — Wed, 24 Sep 2025 13:23:57 GMT

Can you paste them back into the Hotlinked Module source file from you copied them? Or will that crash as well?

Will it also crash when you start a brand new Archicad project based on the default template and paste into that file?

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

rob-faam — Thu, 25 Sep 2025 14:37:55 GMT

Just to be clear: the crash happens in the main project PLN file (into which the MOD file is already placed).

Before the update we could use group suspension and select a single element or a few elements from the placed module (e.g. a wall or a single fill).

Then use ctrl+c and ctrl+v to copy and paste this elements somewhere in the view, apart from the module content.

After making the selection of hotlink parts, the crash occurs when hitting ctrl+c.

All colleagues have the same problem, regardless of which project file or module.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

Barry Kelly — Fri, 26 Sep 2025 01:30:47 GMT

I just upgraded to 6003 to try and I could copy & paste from a suspended module with no crash.

Does this happen to you with any module in any file, or is it a specific module in a specific file?

I am quite surprised you can do that as you can't drag a copy from a module.

I am sure you are aware you can at least ALT-click to get the properties of the element, and then place a new one.

Barry.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

rob-faam — Fri, 26 Sep 2025 07:49:14 GMT

Hi, just tested with a new file and new module (general template 28) and the problem doesn't occur.
When testing the relevant modules within the clean file, it does crash.

So: it appears to be module specific. However, not too specific as multiple of our current project files with hotlinked modules have this issue.
We don't know yet what the common denominator of these modules could be...

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

Barry Kelly — Fri, 26 Sep 2025 08:40:08 GMT

@rob-faam wrote:

We don't know yet what the common denominator of these modules could be...

That is the problem to determine.

If it is just particular modules, is it particular elements in those modules?

If you re-save the module, does that help?

If you are crashing and the Bug Reporter comes up, complete the details, take note of the report number, and then send it off.

Then contact your local support with that report number, and ask them to check it out.

They hopefully will be able to tell what caused the crash.

Barry.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

parvink — Mon, 27 Oct 2025 08:30:27 GMT

Others have reported similar crashes after the 6003 update. In the meantime, try exploding the hotlinked module or breaking the link before copying elements, as a temporary workaround. Also, make sure your graphics drivers and Archicad library are up to date.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

Barry Kelly — Mon, 27 Oct 2025 08:56:36 GMT

So now the question is, was is peculiar to some of Robs modules and not others, in that some crash and some don't?

Is it the element being copied.

Is it a MEP element.?

Does it have a Design Option set?

Does it have a Renovation status different to other elements?

I am just guessing.

Hopefully the crash report will shed some light on the problem.

Barry.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

cagarruta — Sat, 24 Jan 2026 09:04:05 GMT

i´m with @rob-faam, all is updated and the crash is constantly. Atributtes are ok, I think maybe is global vs local libraries issues.

I´ll hope fix urgently.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

Laszlo Nagy — Sat, 24 Jan 2026 11:59:15 GMT

If you think the crash is related to a specific file, there are two things you can try to fix it:

1. Use the "Open & Repair selected file" in the Open Dialog when opening the file.

2. Do a so-called forward merge into a new file. Start a brand new file (possibly based on the same template so settings and attributes will be the same), and use the "File > Interoperability > Merge > Merge from file" menu command to merge the problematic file into the new file. This will get rid of any possible bad data that exists in the problematic file.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

Bawar Tanay — Mon, 26 Jan 2026 14:09:18 GMT

We have the exact same problem.

We are using the iceberg method in a teamwork file.

Will let you know if above resolves the issue.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

rob-faam — Tue, 27 Jan 2026 07:55:11 GMT

I think it has to do with the global library. Some of our files use some older 27 library parts that maybe conflict with the 28 global library.

The problem was fixed with update to 28.2, now with 28.3 the problem is reoccuring.

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

Barry Kelly — Tue, 27 Jan 2026 08:47:36 GMT

Another reason maybe not to mix libraries (unless the old objects are your own custom objects).

Use either the 27 or 28/29 libraries, but not both at the same time.

Barry,

Re: Archicad 28 update 6003 > Crash on copying parts from a hotlinked module

cagarruta — Tue, 27 Jan 2026 17:29:14 GMT

Hello again, problem resolved!

After a lot of trial and error, in our case, the issue was with Archicad classifications.

We erased the classifications we knew we didn't use, generated new HLM, updated the Host and closed the file. Afterwards we opened the file and it worked. I believe there was a conflict in the blurred classifications.

Ill hope work for you

Note: Something similar maybe occur with properties