2026-02-11
11:36 AM
- last edited on
2026-02-12
02:09 AM
by
Laszlo Nagy
Hello,
I'm having an issue with labels being exported to .mod file and then back to the host, even though they don't exist in the exported view.
As you can see, it's reimported as the unlinked labels blocked by the hotlink and placed on the missing layer, so that they can't be hidden. I've found a stupid sollution, which is to use graphics overrides, find unlinked labels and paint them white, but that's very annoying because those labels are being printed on layouts and it looks very unprofessional.
It looks like there were some labels for the doors, that were inserted previously, then the elements, that were associated with them were deleted, now some weird things are happening.
This is the base view, that is published as .mod, settings are:
-current level only
-don't include important elements from different levels
-only visible elements
So, there's no longer elements, that are hosting the labels, no labels on the exported view, but in the .mod file:
there are labels and those labels are on the layer that doesn't exist in the base file:
layers in the base file:
layers in the .mod file:
it looks like the layer is from the map file in dwg that was insertet as the XRef and was later deleted alongside all of the XRef layers.
I can't think of the other sollution than to manually open the .mod file, delete the faulty layer with it's content and then reload the hotlink, but that's not a sollution in the long run.
This isn't the first time that this happens, some time ago the same problem appeared in the different project, in Archicad 26, however then it wasn't as annoying, as there were 2 missing unremovable labels, that I've dealt with by graphics overrides.
Overall working with hotlinks is very beneficial in some ways, but some quirks of the workflow makes them absolutley painfull to work with, especially atribute management between 5 different files that are a part of the same project in teamwork is an absolute hellscape.
2026-02-12 02:23 AM - edited 2026-02-12 02:25 AM
In the source file you save/publish the MODs from: Can you try opening it with the "Open & Repair selected file" command?
I think there is dead/ghost data in the file, and the above command might find them and repair them.
2026-02-13 10:44 AM
Unfortunetly it didn't help, archicad says that file have been repaired with some data lost, but labels stay the same way they were before.
I don't know if that changes anything, but I'm working in teamwork with 10 other architects, so I was thinking it might be some local data issue, but now after repair it is a standalone file.
Also I was thinking about simmilar but quite the opposite issue that I had in one project, window schedules annotated with dimmensions and some 2d info were purged of this info and had to be redone at least 4 times, so there was a sollution, that required going into the registry and turning off some script that was purging "unused data" even if it was in fact used. I'll check if turning back that script helps, if not I'm out of ideas.
2026-02-13 11:50 AM - last edited on 2026-02-13 12:55 PM by Barry Kelly
I can't find the registy element that I was talking about, few years back it looked like this:
now there's no scripts at all:
but the script in question was strictly schedule related, so I assume it was dead end anyways.
2026-02-13 01:27 PM - edited 2026-02-13 01:29 PM
You can try deleting Local Teamwork Data the following way. This was suggested by someone in another Teamwork-related topic:
I am thinking it may be advisable for all project participants to do this so all Local Teamwork Data is deleted on all computers.
2026-02-18 01:49 PM
Can you find these label elements in the original file, even if they are "empty" or referencing objects that have since been deleted? By some smart find & select maybe?
Or I've found that labels that have the setting "hide with associated elements" will be hidden from view if their element is hidden, but it will still be exported WITHOUT their reference object leading to "empty" labels with the errors you show. The solution in that case would be to ensure that the label itself is placed on a layer that is not included in the mod export, not just its host object. Hidden != "not visible" in terms of mod export.