{"id":4221,"date":"2018-09-22T08:32:12","date_gmt":"2018-09-22T08:32:12","guid":{"rendered":"http:\/\/avastar.guru\/?page_id=4221"},"modified":"2018-09-22T08:32:12","modified_gmt":"2018-09-22T08:32:12","slug":"tracebacks","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/292\/reference\/troubleshooting\/tracebacks\/","title":{"rendered":"Tracebacks"},"content":{"rendered":"

<\/image> Traceback Errors in Blender Console<\/h2>\n
\n
\n
\"\"<\/a>

This is an error very deep inside Avastar. It is reported back in a very technical layout. (click to zoom in)<\/p><\/div>\n<\/div>\n

\n
\"\"<\/a>

Some errors are already classified by Avastar (here it found an Export Error)<\/p><\/div>\n<\/div>\n<\/div>\n

Once in a while you get something like shown in the images above. The good news: You made nothing wrong, it is our fault.<\/p>\n

What you see here is an error that happened deep inside the Avastar program. The program simply could not do what the programmer wanted it to do, so Avastar made a full stop and sent a report to the error console. This report is also named Traceback.<\/em><\/p>\n

\n
\n

But you do not have to be worried. This Traceback is not for you, it is for the developers. All you have to do is report this issue to us by opening a new ticket on our support website<\/a>. And please take this seriously! This sort of error should never happen, so …<\/p>\n<\/div>\n

\n

Open a Support Ticket<\/span><\/a>\n<\/div>\n<\/div>\n

 <\/p>\n

We really want to know about Tracebacks. Always!<\/h3>\n