https://community.graphisoft.com/t5/Modeling/Error-messages/m-p/15894#M7526 <DIV class="actalk-migrated-content"><T>I was wondering why the error meesages of door and windows and object say<BR /> <BR /> "error in line 128 of 3d script blah blah blah"<BR /> <BR /> instead of telling you which parameter that was changed is causing the problem as in<BR /> <BR /> "invalid sill thickness"<BR /> <BR /> the other message is not much help if you don't know the GDL script</T></DIV> Tue, 23 May 2023 15:12:46 GMT Anonymous 2023-05-23T15:12:46Z https://community.graphisoft.com/t5/Modeling/Error-messages/m-p/15894#M7526 <DIV class="actalk-migrated-content"><T>I was wondering why the error meesages of door and windows and object say<BR /> <BR /> "error in line 128 of 3d script blah blah blah"<BR /> <BR /> instead of telling you which parameter that was changed is causing the problem as in<BR /> <BR /> "invalid sill thickness"<BR /> <BR /> the other message is not much help if you don't know the GDL script</T></DIV> Tue, 23 May 2023 15:12:46 GMT https://community.graphisoft.com/t5/Modeling/Error-messages/m-p/15894#M7526 Anonymous 2023-05-23T15:12:46Z https://community.graphisoft.com/t5/Modeling/Error-messages/m-p/15895#M7527 It's not always that simple. A single line of code could have a dozen variables that relate to it, and it could even be a problem of one variable added to or divided by another. Telling the line that causes the error is about as fine as any compiler is capable of.<BR /> <BR /> However, the better compilers out there will show you the line of code causing the problem, which I think could be tremendously useful. Even a non programmer who sees something like: sashWidth/WindowDivisions might figure out that having zero divisions would be a bad thing. Thu, 26 Oct 2006 17:12:04 GMT https://community.graphisoft.com/t5/Modeling/Error-messages/m-p/15895#M7527 TomWaltz 2006-10-26T17:12:04Z