Difference between revisions of "How to Report VTube Errors"
(→Error Window) |
(→Show Bug Report) |
||
| (36 intermediate revisions by one user not shown) | |||
| Line 7: | Line 7: | ||
</td> | </td> | ||
<td width=300> | <td width=300> | ||
| − | [[image: | + | [[image:vtube-step_logo_2.png|300px]] |
</td> | </td> | ||
</tr> | </tr> | ||
| Line 14: | Line 14: | ||
VTube has a sophisticated error reporting system that can help us track problems that you encounter when VTube is running. | VTube has a sophisticated error reporting system that can help us track problems that you encounter when VTube is running. | ||
| − | =Error | + | =Error Windows= |
<table width=900> | <table width=900> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td width=300> | <td width=300> | ||
| − | + | ==Non-Critical Error== | |
| − | + | If the error is not critical, then you will be given a choice of<br><br> | |
| − | If the error is not | + | # "continue application" |
| − | # " | + | |
# "restart application" | # "restart application" | ||
# "close application" | # "close application" | ||
| + | |||
| + | <br><br> | ||
| + | <br> | ||
| + | <br> | ||
</td> | </td> | ||
<td> | <td> | ||
| − | [[image:vtube error window non-critical.png| | + | [[image:vtube error window non-critical.png|500px]] |
</td> | </td> | ||
</tr> | </tr> | ||
| Line 32: | Line 35: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td width=300> | <td width=300> | ||
| + | ==Critical Error== | ||
When the error is critical, then VTube cannot continue. The window will look like this:<br><br> | When the error is critical, then VTube cannot continue. The window will look like this:<br><br> | ||
In this case, you will not be given the choice to continue. Your choices are only: | In this case, you will not be given the choice to continue. Your choices are only: | ||
| Line 40: | Line 44: | ||
</td> | </td> | ||
<td> | <td> | ||
| − | [[image:vtube error window critical.png| | + | [[image:vtube error window critical.png|500px]] |
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| + | <br><br> | ||
| + | <br><br> | ||
| + | =Show Bug Report= | ||
| + | <table width=900> | ||
| + | |||
| + | <tr valign="top"> | ||
| + | <td width=300> | ||
| + | |||
| + | 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. | ||
| + | |||
| + | </td> | ||
| + | <td> | ||
| + | [[image:vtube error window non-critical show bug report circled.png|500px]]<br><br> | ||
| + | </td> | ||
| + | </tr> | ||
| + | |||
| + | <tr valign="top"> | ||
| + | <td width=300> | ||
| + | ==General Menu== | ||
| + | When you click on Show Bug Report, the General menu will display first like this.<br><br> | ||
| + | <b>If you want to share this bug event with us, then take a picture of this menu and send it to [email protected].</b> | ||
| + | </td> | ||
| + | <td> | ||
| + | [[image:vtube error general bug report.png|500px]] | ||
| + | </td> | ||
| + | </tr> | ||
| + | |||
| + | |||
| + | <tr valign="top"> | ||
| + | <td width=300> | ||
| + | |||
| + | ==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> | ||
| + | <b>If you want to share this bug event with us, then take a picture of this menu and send it to [email protected].</b> | ||
| + | </td> | ||
| + | <td> | ||
| + | [[image:vtube error call stacks.png|500px]] | ||
| + | </td> | ||
| + | </tr> | ||
| + | |||
| + | </table> | ||
| + | |||
| + | =Log File= | ||
| + | <table width=900> | ||
| + | <tr valign="top"> | ||
| + | <td width=300> | ||
| + | |||
| + | If an error occurs, VTube will also attempt to save a log file named: "vtube_bugreport.log" in "C:\Users\Public\Documents\VTube\config\logs".<br><br> | ||
| + | |||
| + | <b>You can attach this log file to an email and send it to [email protected].</b><br><br> | ||
| + | |||
| + | ==Log Files Do Not Always Save== | ||
| + | If the error is critical (that is, the program is not allowed to continue), <b>then this log file may not be saved as the program closes. In general, it is safer to take a picture of the General and Call Stacks menus to save and send us the error information.</b> | ||
| + | </td> | ||
| + | <td> | ||
| + | [[image:vtube bug report file.png|500px]]<br><br> | ||
| + | </td> | ||
| + | </tr> | ||
| + | |||
| + | </table> | ||
| − | |||
==Other Pages== | ==Other Pages== | ||
Latest revision as of 16:59, 16 March 2017
|
|
|
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 ErrorIf the error is not critical, then you will be given a choice of
|
|
Critical ErrorWhen the error is critical, then VTube cannot continue. The window will look like this:
|
|
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 MenuWhen you click on Show Bug Report, the General menu will display first like this. |
|
Call Stacks MenuThe next tab menu over is the Call Stacks menu. It helps us follow what leads up to the error event. |
|
Log File
|
If an error occurs, VTube will also attempt to save a log file named: "vtube_bugreport.log" in "C:\Users\Public\Documents\VTube\config\logs". You can attach this log file to an email and send it to [email protected]. Log Files Do Not Always SaveIf the error is critical (that is, the program is not allowed to continue), then this log file may not be saved as the program closes. In general, it is safer to take a picture of the General and Call Stacks menus to save and send us the error information. |
|
Other Pages
- Back to the VTube-STEP page
- Back to the VTube-LASER page
