Leaders in the development of virtual
3D environments for business

How To Create Debug Files

About Expo3D Errors

There are two kinds of errors that can occur while running Expo3D; those you can replicate, and those you cannot. If you are able to replicate an error, i.e. you can make it happen every time, simply document the actions taken and send that into Expo3D's support department and we'll work on it.

If you cannot replicate the error, or the actions taken are too complex, you can turn on Expo3D's internal debugging tools to create log files that can be sent to the support department for analysis.

A word of warning however. The internal debugging tools can affect the performance of Expo3D while activated, and can use up a lot of temporary disk space. For this reason, it is not suggested that you leave the debugging enabled unless you are actively trying to capture a problem.

Enabling Debug Mode

After you have logged into an Expo3D show, use the Window menu item and click on the Debug option to bring up the Debugger Settings form.

Debug Settings Form

The Debug Settings form allows you to control what kinds of functions are logged as well as whether logging is enabled or not.

The check box labeled "Enable Debug Mode" controls whether the log files are being updated or not, regardless of the state of any other check boxes. Even if all of the other check boxes are checked, Expo3D is not in debug mode until the Enable Debug Mode is checked. Once checked, the system immediately enters debug mode, even while this form is still open (in fact you do not need to close this form).

It is suggested that you do not run Expo3D in full screen mode so that this debug form remains at least partially viewable while it is activated.

Fill in the Form

For most situations, drag the debug form a bit to the left of the Expo3D window so that it will remain partially visible while you operate Expo3D.

Then click every checkbox except "Even Fast Ones" and "Enable Debug Mode".

Erase Old Logfiles

If the Erase Log button is not grayed out, then there is already a log file present. Click the Erase Log button to erase it.

Note that the Enable Debug Mode cannot be checked. If it is checked, you should not delete the log files. Always stop the debugging by unchecking the enable box before erasing the log files.

Enable Debug Mode

Now check the Enable Debug Mode box to actually start logging your actions.

Then click on the Expo3D title bar (leaving the debug form open) to go back to the main Expo3D window and start using it, trying to encounter the error.

Operating in Debug Mode

While you are operating Expo3D, the debug window should remain partially visible so you can have easy access to it.

Now walk around, talk to people, join presentations, do whatever you think is needed to caused the error. But every few minutes that the error has not occurred, click back to the debug form.

Every Few Minutes

As you use Expo3D in debug mode, whether you do anything or not, the log files continue to grow capturing all sorts program state information.

For this reason, every few minutes, you should click on the debug form and uncheck the Enable Debug Mode to turn off the logging. Then click the Erase Log button to erase the current logs (since they have not captured any errors). Finally re-enable the logging by re-checking the Enable Debug Mode and return to the main window for a few more minutes of operation.

Erase the log every few minutes until the error occurs.

Error Encountered

If you encountered an error and Expo3D did not totally crash then click on the debug form and stop the debug mode but do not erase the log files. Then quit the Expo3D program.

If an error totally crashed Expo3D, do not restart it until you perform the next steps.

Using Windows Explorer, go to C:\Program Files\Expo3D and find the 3 log files that should be present.

• debug.log
• debug2.log
• debug_soundlib.log

Email those 3 files to Expo3D Technical Support department (use this form to inquire about the proper email address to use), along with some explanation of what you were doing and the exact error that occured.

Hopefully, you will have captured enough information that our engineers will be able to determine what went wrong and be able to fix the problem.

Thank you so much for helping us make Expo3D even better!

Copyright © 2006 Expo3D Corp. All Rights Reserved.