Submitting a Bug Report

Bug Reports

We use GitHub Issues to tack bugs and development progress. For most client-side bugs (that's stuff you encounter while playing the game), you can submit a new issue here.

Try to include as much information as possible. Screenshots are always appreciated where they're relevant, and the more information you can provide, the faster something will be fixed. Be sure to check known issues before submitting a new bug report, and feel free to add comments with more information to existing issues if you have it.

Submitting Useful Crash Information

Freelancer can be notoriously unstable if we get things wrong and figuring out how and why the game crashed can be difficult, particularly if we don't have debug data on what went wrong. If you're submitting a bug report for a crash, please try to include the following information:

• Your FLSpew.txt file after the crash has occurred. This can be found at C:\Users\User\AppData\Local\Freelancer\FLSpew.txt. The file regenerates every time the game is started, so this is only useful if you grab it before you start the game again after the crash.
• The crash offset. This can be found in the Windows event viewer. Detailed information on how to fetch the crash offset information can be found here.
• If you can, steps on how to reproduce the crash. If not, the circumstances under which it occurred (where you were, what you were doing at the time, etc)