Difference between revisions of "How to Report VTube Errors"

From ATTWiki
Jump to: navigation, search
(Call Stacks Menu)
(Call Stacks Menu)
Line 77: Line 77:
 
==Call Stacks Menu==
 
==Call Stacks Menu==
 
The next tab menu over is the Call Stacks menu. It helps us follow what leads up to the error event.<br><br>
 
The next tab menu over is the Call Stacks menu. It helps us follow what leads up to the error event.<br><br>
In this menu, we look for in what section the error occurs.<br><br>
+
In this menu, we look for in what section of code the error occurs.<br><br>
 
In this case, we can see that the problem started when the user pressed the InduceError button in the main window of VTube. (I created a button to create an error.)
 
In this case, we can see that the problem started when the user pressed the InduceError button in the main window of VTube. (I created a button to create an error.)
 
</td>
 
</td>

Revision as of 16:25, 16 March 2017

Vtube-laser logo 1.96.png

Vtl screen hd scanner without logo.png

VTube has a sophisticated error reporting system that can help us track problems that you encounter when VTube is running.

Contents

Error Windows

Non-Critical Error

If the error is not critical, then you will be given a choice of

  1. "continuing application"
  2. "restart application"
  3. "close application"





Vtube error window non-critical.png

Critical Error

When the error is critical, then VTube cannot continue. The window will look like this:

In this case, you will not be given the choice to continue. Your choices are only:

  1. "restart application"
  2. "close application"

Vtube error window critical.png


Show Bug Report

If press "Show Bug Report", then you will see detailed data that explains the error and also the state of the software and computer when the error occurs.

General Menu Exception Values

When you click on Show Bug Report, the General menu will display first like this.

The Exception values the most important values in the General menu. We always want to know what these values are set to. The give us a general idea of why the error was generated.

These values are always at the bottom of the General menu like shown in this screen image.





Vtube error window non-critical show bug report circled.png

Vtube error general bug report.png

Call Stacks Menu

The next tab menu over is the Call Stacks menu. It helps us follow what leads up to the error event.

In this menu, we look for in what section of code the error occurs.

In this case, we can see that the problem started when the user pressed the InduceError button in the main window of VTube. (I created a button to create an error.)

Vtube error call stacks trace button press.png

Other Pages