Changes between Version 2 and Version 3 of ReportingErrors

Timestamp:

Mar 19, 2012, 7:07:03 PM (12 years ago)

Author:

historic_bruno

Comment:

--

ReportingErrors

@@ -22 +22 @@
 and generate crashlog files in `%appdata%\0ad\logs\`. The crash dump contains a call stack, which is the state of the program at the time it crashed, this is the most useful info for troubleshooting. There is also a text file with errors that were logged and basic info on the user's system (OS, driver versions, CPU, etc.) Only the most recent crashlog is saved, so it's best to report the crash as soon as it occurs.
 
-Create a [http://trac.wildfiregames.com/newticket new Trac ticket] and attach the crashlog files. If you'd like to try debugging the error yourself, see DebuggingOnWindows.
+Attach the crashlog files to your ticket. If you'd like to try debugging the error yourself, see DebuggingOnWindows.
 
 If the game crashes early (before the main menu is displayed), it may not be able to create crashlog files or error logs. In this case it's useful to read the debug output from the game's startup which is normally not visible, using Microsoft's free [http://technet.microsoft.com/en-us/sysinternals/bb896647 DebugView] utility.