Finding and reading log files

Summary

This section has a list of log files by framework. If you've arrived here from one of the troubleshooting channels on Discord, the file you're supposed to find is most likely in this list.

If you aren't looking for a particular log file, please proceed to the next section.

A list of framework logfiles

Finding the log files

If you don't want to download and run script files from the internet, you can go here and complete the steps by hand. Otherwise:

1. Go to DocPresto's github repository and click the download button:

1. This will download a .bat script (it should be called findAllErrors.bat or similar)

2. Move it to your Cyberpunk game folder

3. Double-click it

4. The script will show you two options.

   1. Option 1 (recommended): Delete all old log files

      1. Type 1 and press Enter. The script will delete all old log files for you.

      2. Wait until the game has started (the script will do that as well)

      3. Do whatever you need to do to make your problem appear

      4. Start the script again

   2. Option 2: Scan log files

      1. The script will scan your cyberpunk directory and open a .txt file with anything it finds, separated by file.

      2. You can now look at #making-sense-of-them to understand the individual error messages, or go back to the discord channel where people told you to grab this script.

Alternatively: By hand

Browse to your Cyberpunk game folder and use the windows search to search for *.log.

The list of results should look like this:

With a few exceptions, log files have the name of their mod. If they don't, check what folder they're in.

There's too many of them!

If you're drowning in log files and have no idea how to filter them, you can delete or remove them. Don't worry, they will be re-created on next launch.

Now, restart your game and do whatever you did to make the error appear. Then, search the Cyberpunk directory for *.log again.

Finding the relevant log file

1. Sort the files by size (if you just deleted them) or by date modified (if you didn't)

2. Open each of the files in a text editor (such as Notepad, it's installed with Windows). The relevant information will be at the very bottom.

3. You are looking for lines with error or warning. If you want to see what they look like, scroll down to the next section.

   1. If the log file doesn't have any, ignore it. Close it and proceed to the next file.

   2. You found errors: Congratulations, you've found at least silver. Check here for how to proceed.

   3. You found warnings: These might indicate that you're on to something, but don't let them panic you. If the mod is doing what it should, just ignore them. You can start troubleshooting already, or keep looking for errors.

Making sense of them

Error

Errors look like this:

[2023-04-15 12:04:18.956] [error] |Something| Some Explanation
[2023-04-14 20:28:18 UTC+01:00] [1234] [ErrorSource]  DoSomething(): Error ! Some Explanation: Some Details

An error in the log files almost always means that something exploded in a way that nobody has planned for.

• If the file is directly in bin\x64\plugins\cyber_engine_tweaks, that means CET is broken and you need to troubleshoot it.

• If the file is in a subfolder of bin\x64\plugins\cyber_engine_tweaks, you have found a broken mod, but CET mods won't break the game. In this case, treat it like a warning.

• If the log is anywhere else, you have found something to troubleshoot.

Warning

If your warning isn't listed below, use your own best judgement.

Field with this name is already defined

[WARN - Thu, 13 Apr 2023 21:54:13 +0200] At Path\to\Cyberpunk 2077\r6\scripts\something.reds:1234:1:
@addField(inkScrollArea)
^^^
field with this name is already defined in the class, this will have no effect

This might indicate that a Redscript mod is loaded twice. Search the Cyberpunk root folder the mod name and make sure that you have no duplicates. If you're uncertain about this, try the bisect method on your r6 folder.