Reporting a bug

1. Update to the latest release and check it still happens.
2. Look it up: search the last lines of logs/mkw.log in Troubleshooting and in issues (open and closed). If it is there, add your log to that issue.
3. Open a bug report with:
   • what happens, with the exact error text;
   • the release (or commit) and your game version (1.0.0 or 1.8.0);
   • OS, CPU, GPU and driver version: F1 → Advanced → Copy system info copies them;
   • the steps, and the settings you changed;
   • the log file attached (drag it into the comment): logs/mkw.log, or logs/setup.log if the setup failed. The whole file, not a screenshot or the last lines. Earlier runs are mkw.1.log … mkw.4.log. Where it is.
   • for a picture problem, a screenshot.

If the game freezes, wait about 30 seconds before closing it so the log records the hang. Mention any mods, or try without them first. The start screen also offers Report it after a run that ended in an unknown error.

Slow scenes go to the performance form: the F10 overlay in full mode, frame times typical and worst over 20 seconds, after a first run so the caches are warm, without frame generation.

Questions that are not bugs go to Discussions → Q&A.

What the bot does

A bot reads every new issue:

• no log and no reply: labelled needs-logs, closed after 7 days without one;
• a known error (its log line is in Troubleshooting): closed as a duplicate of the issue that tracks it; your reply reopens it if yours is different;
• reported on an old release: asked to try the latest, closed after 7 days without an answer;
• a log with mods on, or from a modified build: asked for a run without them;
• asking for the game, its files or keys: closed.

A closed issue reopens when its author says it still happens, with a log.