Download WCS Debug-Build Support-Tool (short: DBST) ZIP and unzip it, then start WCS_Debug-Build_Support-Tool.exe and press <Start Debug Build and create Support ZIP>. After DBST ends, you will find the fs2_open_SupportTool.zip at your desktop and this file can directly attached to a posting in the forum.
Info: The WCS Debug-Build is included in DBST, there is no need for an additional download of the Debug-Build.
Privacy dxdiag.log and dotnet.log contains the computer name (network) and fs2_open.log contains the user profile name (Windows).
2. Background & Functions (primarily interesting for supporters)
The idea for this tool i had last year. I thought about how the handling for the debug build and the log can be simplified. And i wanted a simple way to give the supporter a system report for the most important windows and hardware values.
DBST have the following functions and reduces all needed steps to a minimum:
Copied the officially debug build into the correct WCS folder. If UAC is active, then a thread called "WCS_Debug-Build_Support-Tool_copy.exe" will be started to ask the user for permission to write in the WCS folder. DBST have a version check, so if the local debug build is older then the one in DBST, the local debug build will be replaced. Info: In the properties of the DBST EXE you can find the debug build version under "ProductVersion". This info will also shown in the DBST GUI.
Starts the debug build. You can use all commandline parameters from the official debug build in the commandline textbox. Info: You can test this very simple with the parameter -nosound as example.color=orange]fs2_open.log[/color
After the debug build ends, because of normal end or because of a CTD (Crash To Desktop), DBST creates automatically a system report with DXDIAG (if enabled, standard). In this log, the supporter can find the most important Windows and hardware values from the users computer. Info: This log includes information about the Windows version, processor, memory, graphic card type and graphic card driver version.color=orange]dxdiag.log[/color
The possibility to check the WCS installation for errors and add the result to the Support ZIP. (if enabled, not standard). Possible results for the separate files: [MD5 OK ] = File exists and is OK, [MD5 WRONG!] = File exists but is corrupt, [NOT FOUND!] = File is missing. color=orange]md5check.log[/color
At last point, DBST creates automatically a ZIP with all logs and the WCS profiles, depending on selection. The user can then find the Support ZIP (fs2_open_SupportTool.zip) on his Desktop very easily.
Fix: If DBST was started more than once, the second instance had deleted the temp files from first instance.
The check for single instance starts now at first position instead of last. This prevents unnecessary (double) warnings and error messages.
Version from the OpenAL DLL in System directory will determined and written in to dbst.log.
New: can detect now all installed .NET Framework versions with their servicepacks. For this DBST uses the ".NET Version Detector" from www.asoft.be
with kindly permission from Nick Asseloos. (Idea: laraan)
Some error messages will no longer prevent DBST start. Now simply the dependent features will deactivated so it's possible to create a support ZIP with some basic informations.
These error messages are now written in dbst.log with the prefix "ERROR:".
More informations like additionally version numbers added to dbst.log. Furthermore the actions from DBST are logged much more detailed than before.
One single line no longer contains multiple informations in dbst.log. One line, one information.
Added milliseconds to the timestamp in dbst.log and md5check.log.
Checks if WCS or Debug Build is running.
Checks if another instance of DBST is running.
Disables the option "include game profiles" if no profiles exists.
Bugfix: On a 64 bit Windows DBST can't detect the WCS path and doesn't start. (Report: Blair)
New: Now DBST have the feature to check the complete WCS installation with MD5 to find errors or missing files. The result will added to the Support ZIP. Supported versions: 184.108.40.20695, 220.127.116.1122.
New: All actions are now written into the new log file dbst.log and this will added also to the Support ZIP.
New: Informations about Debug Build versions on GUI and in log file.
Other little improvements.
Some improvements like a GUI, selectable options and other little things.
Also new is the option to add the players WCS profiles to the support ZIP.
This really looks interesting. Any tool to ease support and debugging for FSO-based game would be be welcomed by the larger community. I think you should present this tool at the Hard Light Productions forums, on the
FS2 Open Tools
board, as this can benefit any FSO game in addition to Wing Commander Saga.
Then i logged in at HLP IRC and no one was interested to help me! So sorry, my interest to join HLP is now... very low. And i found no other way to communicate with a HLP moderator. You need a forum account to tell a moderator, that you can't register a forum account!?
Hmm, looks like the admins are going to need you email and IP to find your account. If you send them to me via PM, I'll pass the information to the admins.
Which IP exactly? In Germany static IPs are very uncommon. Private internet users have normally dynamic IPs and have this IP for maximum 24 hours (standard).
Because of private circumstances i have atm no time to support other games. The next point is, Aginor have pointed 2 days ago at HLP to my EPW-Bug-Repair-thread here in wcsaga.com forum after i asked him to do so. So at the moment there is no need for me to write in HLP forum.
But... maybe it would be usefully for the future to have a HLP account, so i send you my data via PM.