Minh, Schagemann,
Thank you for your replies, I have updated to version 5005 and have to see if the issue persists. List of improvements included something similar to what I had. If not I will generate an error report.
Schagemann, I mostly use Mods which their origin not within a main file but the mod itself. In place modeling with mods (working in one file as source) it can make things complicated sometimes, like working in more than one level, grouping elements and many other. I switch between two methods.
As for modelling in context : I can use two methods to have a context of where I am drawing (which I haven't used in the above example). One is to trace over an overlay of a parallel archicad instance, the other one is quickly copy/pasting a floorplan 2d to a worksheet (which is deleted anyway once the mod is saved).
The mod itself from the example above, was originally in a main file, which had the crashing issue, and when I split our project into pieces the error remained on the mod file, which can indicate a graphical issue that links to one of the library files. I think all are the defaults of AC23. Resaving / recreating doesn't help.
Another thing - working with BIM cloud we save our IFC's as mod's while the main downside is not being able to overwrite elements materials etc' in a structured way, I find it horrible to every time copy libraries of our IFC's to our BIMcloud and getting an endless collection of those.
I know how weird this workflow might sound, for me it works perfect ! When I see other projects' mess concerning all the view types, groups and filters they use to manage mods it scares me.
For me not being able to edit .mods in place and dealing with IFC's in the context of BIM cloud , are by far the most two downsides of archicad (i'm an ex Revit user). I think not something that is impossible to change.
AC23 NED 7000 | AC24 NED 5000
Win10 | i9-9900k | 32GB | RTX 2080 Ti