url=http://forum.wcsaga.org/viewtopic.php?f=14&t=25:2j05fndo]from wcsaga.org (german)[/url
1. Usage
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).
Screenshots
[attachment=0:2j05fndo]<!-- ia0 -->PicPick_2013-07-10_20_28_26.png<!-- ia0 -->[/attachment:2j05fndo]
[attachment=2:2j05fndo]<!-- ia2 -->PicPick_2013-06-21_22_02_03.png<!-- ia2 -->[/attachment:2j05fndo]
[attachment=1:2j05fndo]<!-- ia1 -->PicPick_2013-06-21_22_30_45.png<!-- ia1 -->[/attachment:2j05fndo]
2. Background & Functions (primarily interesting for supporters)
[spoiler:2j05fndo]
2.1 Background
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.
2.2 Functions
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
- The feature to add all WCS game profiles to the Support ZIP. (if enabled, not standard) color=orange]profiles[/color
- The feature to detect all installed .NET Framwork versions with their servicepacks. color=orange]dotnet.log[/color
- All actions from DBST will logged in a separate log file. color=orange]dbst.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.
[/spoiler:2j05fndo]
3. Download
Download from wcsaga.org forum thread
Changelog
[spoiler:2j05fndo]
1.1.2.5 2013/8/1
- 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.
1.1.2.0 2013/7/10
- 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.
1.1.1.1 2013/7/6
- 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.
1.1.1.0 2013/6/21
- 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: 1.0.2.7795, 1.1.0.7822.
- 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.
1.1.0.0 2013/6/14
- 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.
1.0.0.0 2013/4/2
[/spoiler:2j05fndo]