People also need reminding that first, you need to cross check your information when posting about games working or not working: i.e. you need to look in the compatibility list to see what has already been reported for the game.
Additionally, you need to put a little more than the name of the game and what went wrong or didn't. You need to report which version of the emu you're using and which BIOS; perhaps configuration info if relevant, too. As well as the name of the game, you need to report the Game ID. If you have the original case, it should be on the spine; if you don't, look at the contents of the CD: there should be a file with the name S***.<numbers>; S*** is usually SLES, SCES, SCUS, SLUS or something like that. That's the Game ID. It may be in a folder, although this is not usual. If you only have an image, mount it with something like Daemon Tools and you can look at the contents. Add whether it's an NTSC or PAL version and, if appropriate, what country version it is. Remember that, if it's an image or a burned disk, the problem may have been with the ripping/burning process: apart from anything else, many Playstation games are copy protected.
If you're having problems with it, some information on your system may be relevant, particularly if it's fairly low end. What OS you're using is useful; as is the controller you're using. If you're reading from CD, it's useful to know whether you're using IOControl or ASPI, and what ASPI you're using if you are.
Have I covered everything? Probably not...
Lastly, try to make your report comprehensible and describe any problems clearly: i.e. where in the game they crop up, what happens (or doesn't) and, as far as you can say, as a result of what?
With me, there are some "beta testers", and atm, there is no problem to credit. When a guy tests a game, he tries to follow the game with each new release of an emulator. Or if he can't, another guy take his place. And I credit the new guy.
Post by smegforbrain on Jun 3, 2006 12:33:24 GMT -5
Yeah, for me, keeping the fields to a minimum is all about keeping a managable file size. So, I got rid of all the fields I felt safe in getting rid of, and won't add any unless there's a really, really good reason.
And getting rid of the BIOS field is still in the back of my mind - it would probably shave 40-50k off the file size. Much like settings, any relevant info to the BIOS could probably just be moved to the comments section.