My observations on the crashing of update preview 28.1:
- After sending the bug report and restarting ArchiCAD, i have not had any loss of information on the file - last save is practically at the point of crashing. So there's smooth sailing and drastically reduced frustrations. That helps and that's why I won't revert to 28.0.3 - I lose a few minutes of work at most, basically the time needed to restart ArchiCAD and reload the file I'm working on.
- I had dozens of crashes on a file which had many library parts from monolith library. Once I converted to global libraries (and used CI Tools to convert as many library parts and elements as possible) to the global library, I experienced fewer crashes by the order of magnitude. It's been in single digits since. Still occuring but much less frequently. Also to note: there is still one missing part I haven't been able to erradicate from my file - "Rail 27" if I remember correctly. I have tried redoing all the railings and the default rail to select global library sub-parts but to no avail. All objects display fine, but under library manager it's still there. I cannot get more info (it's grayed out) so I really can't find it and everything looks fine. If anyone has suggestions to fix it, I'll be very grateful.
- Dragging, keyboard shortcuts, panning while system is not fully ready (especially with pick-up / inject properties tools which are awfully laggy) seem to be the most common actions resulting in crashes.
- I have not been taking notes on the bug report identifiers. There have been way too many to count and the frustration of the program crashes has something to do with the will to write it down. Also, if there isn't, there should be an integrated bug report logging tool which should give the users reports on bug reports, meaning a user should be able to see data from the reports - when, why, was it resolved and how... The last one is of course unrealistic. But the first two should be readily available.
ArchiCAD 28 | INT - Cro | Forward | WIN 10 / 11
