With the recent freeware-version release of the famous 3D-file optimizer Chisel, usage has increased dramatically. Because no software that writes code is ever truly perfect, a previously unreported bug was noticed by the Pacoima Ranch Web3D development teams. The files involved described related organic shapes, some using protos, other using nurbs. The commonality was one or more extremely long string of coordinates that Chisel was tempted to line wrap. The line wrapping introduced an error that strict VRML browsers and X3D parsers choked on, then refused to show the file.

By carefully comparing the preChiseled and Chiseled version, the offending lines can be found. Also, if the text editor allows it, using the "display all characters" or "display invisible characters" command, the linebreak symbol (frequently a ^P) can be easily seen. By changing the linebreak symbol to a comma, the error was removed and a complete and proper long string is reintroduced. If your text editor cannot show invisible characters, look for an extremely long line near the start with one or more smaller lines after it that have incorrect ending and starting brackets (usually missing altogether). Delete all spaces between the ending and beginning coordinates of the lines, then add a comma and a single space after it.