Bug Reporting

Places to ask about or report bugs

Mantis bug reporting system
FSSCP Forums
FSSCP Backup Forums

Basic Guidelines

1. Look before you leap - make sure there isn't a similar bug before you post a new one. If there is a similar bug, post info on your particular circumstance.

2. ALWAYS post what build you're using (If it's named something like "fs2_open_r", post where you got it from and what date it was posted).

3. ALWAYS post what command lines you're using (And which ones the bug happens with).

4. Don't just post the bug. Post any and all relevant info, and if you aren't sure if something might be relevant - post it anyway.

5. If at all possible, post contact info. Nothing is more convenient for a dev than having an ICQ number you can use to talk with a person having a problem. It can also speed things up a lot.

6. If you've got the time, run a debug build and post any errors you get with it (Not all builds have a debug build with them though).

7. Keep track of any bugs you post (in)! Nothing is more annoying than not being able to close a bug simply because you don't know if it's solved or not.

8. Make sure to include what mediaVPs you're using.

Posting error logs

Especially when using debug builds, Freespace 2 will generate files called "errorlog.txt" and "fs.log". Posting the first chunk of data from the corresponding entry in errorlog.txt can be a big help, as it may tell the dev exactly what went wrong where. (This chunk is recognizable, as it should have the date and time that the crash occured).

Additionally, posting the last five lines or so of "fs.log" can also be handy. Note that Notepad will not display it properly, so you'll have to open it up in Wordpad to view it properly.