Changes between Version 5 and Version 6 of ReportingErrors


Ignore:
Timestamp:
May 26, 2012, 1:18:06 AM (12 years ago)
Author:
historic_bruno
Comment:

update to point to new GameDataPaths page

Legend:

Unmodified
Added
Removed
Modified

  • ReportingErrors

    v5 v6  
    55
    66There are currently two ways to file a bug report:
    7  * The preferred method is to [http://trac.wildfiregames.com/register register] here on Trac and create a [http://trac.wildfiregames.com/newticket new ticket]. You will be notified of replies or status changes on the ticket. Attach any files that might be useful (logs, crash dumps, etc.) To avoid duplicate reports, search Trac or the [http://trac.wildfiregames.com/report/3 ticket report].
     7 * The preferred method is to [http://trac.wildfiregames.com/register register] here on Trac and create a [http://trac.wildfiregames.com/newticket new ticket]. You will be notified of replies or status changes on the ticket. Attach any files that might be useful (logs, crash dumps, etc. - see GameDataPaths). '''To avoid duplicate reports, search Trac or the [http://trac.wildfiregames.com/report/3 ticket report].'''
    88 * Or you can create a [http://www.wildfiregames.com/forum/index.php?app=forums&module=post&section=post&do=new_post&f=378 new topic] in the Bug Reports forum.
    99
    … …  
    2020[[Image(Windows-Program-Error.png)]]
    2121
    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.
     22and generate crashlog files in the game logs location, see GameDataPaths. 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.
    2323
    2424Attach the crashlog files to your bug report. If you'd like to try debugging the error yourself, see DebuggingOnWindows.
    … …  
    6565[[Image(ErrorAndWarning.png)]]
    6666
    67 The game will continue after most errors, but they may trigger more errors. Errors are often caught by the developers but sometimes they sneak into the Alpha releases. To report the exact messages, open `interestinglog.html` in your web browser and copy the contents into your bug report. The location of the logs varies by OS:
    68  * Windows: `%localappdata%\0ad\logs\`
    69  * Linux: `~/.config/0ad/logs/`
    70  * OS X: `~/Library/Application\ Support/0ad/logs/`
     67The game will continue after most errors, but they may trigger more errors. Errors are often caught by the developers but sometimes they sneak into the Alpha releases. To report the exact messages, open `interestinglog.html` in your web browser and copy the contents into your bug report. The location of the logs varies by OS, see GameDataPaths.
    7168
    7269A screenshot of the message is less desirable as compression and scaling artifacts obscure the text, and you may not see all the errors. It's very useful if you can remember the steps to reproduce the error.