Just a comment to add ... that relates to the problem-tracking process below and not necessarily to the subject of this thread!
A variety of errors do not appear in plan (2D) because the 3D view of objects is most often generated by a completely independent script from the 2D view.
A client had a similar problem with multiple errors in the 3D (or elevation) window. I ended up marqueeing various areas until I found the problem
You can avoid this 3D "surprises" relatively easily:
[Tip]: Before
leaving the Settings dialog for any library part, click on the 3D (axo) preview
as well as
the 2D previews. If any errors will be generated, you'll almost always get the message right there and then. This way, you
know
that you are only placing valid elements in the project.
Naturally, more rigorous error-checking in all library parts would prevent many of these error messages - most of which arise when something is set to zero that cannot be zero (or less) - such as trim thickness. Users should never see messages like that that prompted this thread. Like James said: it is the windows (graphisoft's) fault, but is the user's problem to fix it (today).
HTH,
Karl
One of the forum moderators
AC 28 USA and earlier • macOS Sequoia 15.2, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB