***IMPORTANT*** If the below instructions are not met, your post may be deleted from these boards!
Greetings!
We understand that you may be experiencing issues with the game you purchased, and that you are eager to get it fixed. As much as we would like to help every single one of you personally, there are some guidelines that need to be met for us to be able to utilize a report and actually do something about the problem. Please remember that these rules are here as much for your own good as ours. The more structured we can keep these forums, the more time we can spend on actually helping you. Also stick to your own post. There is no need reporting the same issue in more than one place.
Please make sure to follow these instructions to the best of your abilities or you may find your post being removed!
1. Before doing anything else, search the forums to see if anyone already reported the issue (and maybe got a solution as well). Do this by clicking "Search Forum" in the top right of your screen and search for your error message or description of the problem (see point 2).
2. Use proper naming of your thread! A thread name should provide a brief description of the issue. If you can fit your platform and/or an error message in there it's even better.
Example of bad thread name: "HELP PLEASE!"
Example of a good thread name: "Windows 7 - Game crash when starting quest "x""
3. Provide proper information on what you were doing when the problem occurred. Quote any error messages you receive, attach crash logs and provide a screenshot if possible. Anything you can to explain what exactly is the problem.
4. Provide a specification of your system. See the bottom of this post how to obtain a dxdiag log.
5. Provide the crash log which can be found in (Windows)"..Steam\steamappscommon\Knights of Pen and Paper\knightspp_Data\output_log.txt",(Mac OS) " /Users/<username>/Library/Logs/Unity/player.log" or (Linux) /home/[username]/.config/unity3d. This log will be re-written every time you start the game, so it needs to be retrieved after a crash, before trying again.
Please use code tags when pasting logs into your post. See here for more info on how to use BB Code to tag your content.
Please read below and follow the instructions to the best of your abilities or you may find that your bug report is deleted.
The first and supreme rule of all bug-reporting is: If it can’t be reproduced, it can’t be resolved! (if your report does not contain this information it is of no use for us and will be deleted to not draw attention from issues where we can do something)
So what is most important to include in a bug report is the necessary steps to reproduce the problem. If your report does not contain this information, we will most likely have to scrap it. If you are unable to reproduce the problem it may not be an actual bug in its technical meaning.
We will also require a specification of the system where you got this bug. If you are on a windows machine the best way to provide this information is to attach a “dxdiag” log.
The crash log specified above is also useful!
Last but not least. Keep checking your post/thread! We may be asking you follow up questions or requesting additional information
Greetings!
We understand that you may be experiencing issues with the game you purchased, and that you are eager to get it fixed. As much as we would like to help every single one of you personally, there are some guidelines that need to be met for us to be able to utilize a report and actually do something about the problem. Please remember that these rules are here as much for your own good as ours. The more structured we can keep these forums, the more time we can spend on actually helping you. Also stick to your own post. There is no need reporting the same issue in more than one place.
Please make sure to follow these instructions to the best of your abilities or you may find your post being removed!
1. Before doing anything else, search the forums to see if anyone already reported the issue (and maybe got a solution as well). Do this by clicking "Search Forum" in the top right of your screen and search for your error message or description of the problem (see point 2).
2. Use proper naming of your thread! A thread name should provide a brief description of the issue. If you can fit your platform and/or an error message in there it's even better.
Example of bad thread name: "HELP PLEASE!"
Example of a good thread name: "Windows 7 - Game crash when starting quest "x""
3. Provide proper information on what you were doing when the problem occurred. Quote any error messages you receive, attach crash logs and provide a screenshot if possible. Anything you can to explain what exactly is the problem.
4. Provide a specification of your system. See the bottom of this post how to obtain a dxdiag log.
5. Provide the crash log which can be found in (Windows)"..Steam\steamappscommon\Knights of Pen and Paper\knightspp_Data\output_log.txt",(Mac OS) " /Users/<username>/Library/Logs/Unity/player.log" or (Linux) /home/[username]/.config/unity3d. This log will be re-written every time you start the game, so it needs to be retrieved after a crash, before trying again.
Please use code tags when pasting logs into your post. See here for more info on how to use BB Code to tag your content.
Please read below and follow the instructions to the best of your abilities or you may find that your bug report is deleted.
The first and supreme rule of all bug-reporting is: If it can’t be reproduced, it can’t be resolved! (if your report does not contain this information it is of no use for us and will be deleted to not draw attention from issues where we can do something)
So what is most important to include in a bug report is the necessary steps to reproduce the problem. If your report does not contain this information, we will most likely have to scrap it. If you are unable to reproduce the problem it may not be an actual bug in its technical meaning.
We will also require a specification of the system where you got this bug. If you are on a windows machine the best way to provide this information is to attach a “dxdiag” log.
The crash log specified above is also useful!
Code:
How to obtain a dxdiag log:
If you have Windows XP, you get the dxdiag like this:
* Click on your "Start" button.
* Select "Run".
* Type "dxdiag" (without the quotes).
* Click "OK".
* A box called "DirectX Diagnostic Tool" should open.
* At the bottom of this window, you will find a button called "Save
All Information".
* Click this button.
* A box will pop up prompting you to save a file called "dxdiag.txt"
* Save this file to your "Desktop".
* Now you should see a text file called "dxdiag.txt" sitting on your
Windows desktop.
If you have Windows Vista, 7 or 8, do like this:
* Click on your "Start" button.
* Write dxdiag in the search field.
* A box called "DirectX Diagnostic Tool" should open.
* At the bottom of this window, you will find a button called "Save
All Information".
* Click this button.
* A box will pop up prompting you to save a file called "dxdiag.txt"
* Save this file to your "Desktop".
* Now you should see a text file called "dxdiag.txt" sitting on your
Windows desktop.Last but not least. Keep checking your post/thread! We may be asking you follow up questions or requesting additional information
Last edited by a moderator: