There is a reasonably ok-ish reason for this, not that I expect many will agree with that assertion
. These are not our error messages; they are from ACIS. We pass them on to you.
ACIS has...a deluge...of possible error messages. And it is not always obvious what they mean, or what they imply - sometimes even to us. We have considered intercepting them in the past and trying to provide a more user-friendly presentation, but the sheer scope of the project has precluded us from doing that. Perhaps we can implement something that phones home every time an ACIS warning message is received (optionally), such that we can at least determine what the 30 most common errors are during modeling, and perhaps use that as a basis for a more limited engagement.