Steven wrote:
Doing a little research, it seems that there is not definite way to figure out what is the problem, just through the process of elimination. There should be a way to jump to the error or the element that is causing the error. This would save many people a lot of time...
Actually, the solution is for Graphisoft to produce library parts that work - then nobody will see this and other errors. The problem is that many Graphisoft library parts do not do sufficient error-checking and consistency-checking on their parameters, allowing the entry of values (as you've seen in the past) that cause the part to bomb out.
I would much prefer seeing proper quality control for library releases to better tools for tacking down errors which are not really caused by the user.
😉
Cheers,
Karl
