PCSX2 Documentation/How to Create Useful and Valid Issues: Difference between revisions
PCSX2 Documentation/How to Create Useful and Valid Issues (view source)
Revision as of 23:15, 8 January 2015
, 8 January 2015no edit summary
(Created page with "Since Github has a very nice issues feature with labeling and tracking, we really want to use it in our advantage to keep track of PCSX2 issues and as a nice knowledge base....") |
No edit summary |
||
| Line 3: | Line 3: | ||
Unfortunately, most people just want their games fixed and simply post some image of the problem or some vague description, which are both completely useless to the developers. | Unfortunately, most people just want their games fixed and simply post some image of the problem or some vague description, which are both completely useless to the developers. | ||
You must make sure that | You must make sure that '''all speed hacks are off''' and always check that your testing system is stable (for example not overheating, no unstable overclock etc) | ||
Here are some links so you can easily find older versions to test: | Here are some links so you can easily find older versions to test: | ||
| Line 12: | Line 12: | ||
So here are 2 example issues for you, so you can copy/paste this template and use it on your own issue. One is for a core problem and another for a graphics problem. | So here are 2 example issues for you, so you can copy/paste this template and use it on your own issue. One is for a core problem and another for a graphics problem. | ||
---- | |||
Core issue: | Core issue: | ||
| Line 42: | Line 42: | ||
---- | |||
Graphics issue: | Graphics issue: | ||