For idea submission see ---> Ideas / Feature Requests / Other Thoughts
---------------------------------------------------------------
Provide as many details about your issue as you can, please, such as:
- a video or screenshots of the issue along with its location on the map,
- a shot of the journal tab or skills,
- the affected quest name,
- information on how often something happens and whether it happens after a reboot etc.
- information on whether the game has been updated throughout the existence of the affected save file, as there might be potential save incompatibility when the game version changes
- the version of the game you are running - unless you can't start it at all, the number is visible in the bottom-right corner of the main in-game menu
- information or screenshots of your settings in the video options menu
For Xbox consoles users:
Tell us your GAMERTAG, please.
For Windows® PC platform users:
Right-click the game in your Steam Library - go to Properties and enter these two commands, please:
/verbose
(adds more informative logs)
and
/fulldump
(makes dumps)
Like so:
This will create more informative logs and dump files that help our team effectively recognize a given issue.
(Once the issue has been resolved, you can delete the above parameters.)
In addition to that, see if you can find the Build ID of your game in the Updates tab under Steam Properties of the game:
When it comes to the Epic Games Launcher, go to your Profile, select Settings and scroll down until you find the Dying Light 2 Stay Human entry. Click it, please:
You can now enable additional launching options that can be entered below, with the "-" symbol before them, like so:
Now, send us your message with the Build ID and a DirectX Diagnostic file generated on your system and a few Crash Log files along with any dumps attached to them, please.
DxDiag stands for DirectX Diagnostic tool, which collects information about your computer hardware, operating system and installed drivers.
Whenever you meet a crash, low performance or some graphical issues - this information is important for troubleshooting.
The file does not contain any personal information, so it's fine to make it publicly available.
Here are the steps for you to follow in order to generate the file:
- Open the Windows desktop.
- Press Win+R on your keyboard (the Windows key and the R key together) to open the Run window.
- In the "Open:" field of the Run window, type in dxdiag.
- Click OK or the Enter key to open the DirectX Diagnostic Tool.
- If prompted to check if your drivers are digitally signed, select Yes.
- In the DirectX Diagnostic Tool window, click the Save All Information option.
- In the "Save As" window, information should be saved as a text (.txt) file.
- Choose a directory where the file will be saved and press the "Save" option.
- It's usually more convenient to use an accessible directory, such as your Desktop.
- Now you can send us your dxdiag.txt file in a ticket form.
Crash Log files, on the other hand, are created when you launch the game.
Even though their name suggests crashing, they also help us identify issues completely unrelated to crashes or freezes, which is why we would like you to send them to us.
Make sure these are the "right" logs for the issue you're about to describe, please, as the game creates a log each time you launch it.
Some of them create dump files and those are typically made when the issue is, in fact, related to a crash. So unless your game crashes, there's no need to search for them. You might find no .dmp files at all on your end and that's totally normal.
To find the .log files and their .dmp files, go to:
- %userprofile%\Documents\dying light 2\out\logs
- %userprofile%\Documents\dying light 2\out\dumps
Our attachment limit is 20MB, so if the files are too large, you can pack them into a .zip or .7zip format.
Note that our team normally replies to your messages within 2 working days, though it may take longer depending on the volume of e-mails we receive.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article