06-09-2015, 06:47 AM
(This post was last modified: 12-22-2020, 06:08 AM by Blyss Sarania.)
Since a lot of people don't know this (I even didn't until recently!) I thought I would write up a brief post to refer to when one of the devs needs a GS dump.
First: What is a GS dump?
Basically it is what it sounds like. It is a dump of the core output that goes to the Graphics Synthesizer. Basically it allows someone else to "replay" what is "recorded' in the dump.
Second: Why is this useful?
A GS dump is useful for a few reasons. First and foremost, it allows a developer who does not possess the game in question to still tackle and fix graphics bugs with it. It allows replaying of a specific scene of any game without needing the game itself at all. They are useful for recording bugs and then providing the output to devs to work on. Even if the dev DOES own the game, a GS dump is still useful because it allows them to instantly replay the bug in question instead of having to play the game and find the issue.
Third: What types of bugs are GS dumps useful in solving?
Pretty much any graphics related bug. There is the off chance that a graphics bug is actually a core problem, but that isn't too likely.
Fourth: Anything else?
It's important to note that the dump is independent of your GSdx settings. Since the dump is actually the output of core itself, it doesn't matter if you have 3x scaling, native, software mode, anisotropic filtering or all that. The dump will be the same because it is generated before any of that comes in to play. So one GS dump is fine regardless.
Okay, now that we've got the explanation out of the way, here is how you make one.
The first thing you want to do is boot your game in PCSX2 and get to whatever part has the bug. Then to generate the dump you press SHIFT + F8 for a single frame or CTRL + SHIFT + F8 for multiple frames. If you use the multi frame option, the important thing to note is that how long you hold down the key combination determines how long the GS dump is. If you press for 4 seconds, you get a 4 second dump. What you want to do is hold the keys long enough to capture the entirety of the graphics bug. However, a single frame dump is enough 99% of the time. If you are wondering whether you need single or multi frame, just go with a single frame until told otherwise. Multi frame dumps get very big very quickly and are only needed in special circumstances.
Okay, now you've got your GS dump, what do you do with it?
In the "snaps" folder of PCSX2 you will find two files with the name being like "gsdx_20150408134014" and the extensions being .gs and .png. The PNG is an image file snapshot of what you recorded. The .gs is the GS dump itself. First you should rename these files to something meaningful. This is important! An example might be "FFX text bug.*" for the text issue in FFX. The .* is the original extension, leave those as is. Make sure to include the game name in the file name so the devs can keep their stuff sorted nicely. Then take both of these files and compress them(e.g. with 7zip, WinRAR or whatever you like). Then upload them to a file sharing service like Dropbox.
Now you are ready to rock. If someone simply asked you to provide one, give them the link and that's it. Otherwise if you are reporting an issue for the first time, go to the GSdx thread. Make a new post there and link your GS dump along with providing a nice description of the issue. Don't expect things to be fixed instantly, but the more GS dumps and information the devs have, the more progress can be made!
That's pretty much it!
First: What is a GS dump?
Basically it is what it sounds like. It is a dump of the core output that goes to the Graphics Synthesizer. Basically it allows someone else to "replay" what is "recorded' in the dump.
Second: Why is this useful?
A GS dump is useful for a few reasons. First and foremost, it allows a developer who does not possess the game in question to still tackle and fix graphics bugs with it. It allows replaying of a specific scene of any game without needing the game itself at all. They are useful for recording bugs and then providing the output to devs to work on. Even if the dev DOES own the game, a GS dump is still useful because it allows them to instantly replay the bug in question instead of having to play the game and find the issue.
Third: What types of bugs are GS dumps useful in solving?
Pretty much any graphics related bug. There is the off chance that a graphics bug is actually a core problem, but that isn't too likely.
Fourth: Anything else?
It's important to note that the dump is independent of your GSdx settings. Since the dump is actually the output of core itself, it doesn't matter if you have 3x scaling, native, software mode, anisotropic filtering or all that. The dump will be the same because it is generated before any of that comes in to play. So one GS dump is fine regardless.
Okay, now that we've got the explanation out of the way, here is how you make one.
The first thing you want to do is boot your game in PCSX2 and get to whatever part has the bug. Then to generate the dump you press SHIFT + F8 for a single frame or CTRL + SHIFT + F8 for multiple frames. If you use the multi frame option, the important thing to note is that how long you hold down the key combination determines how long the GS dump is. If you press for 4 seconds, you get a 4 second dump. What you want to do is hold the keys long enough to capture the entirety of the graphics bug. However, a single frame dump is enough 99% of the time. If you are wondering whether you need single or multi frame, just go with a single frame until told otherwise. Multi frame dumps get very big very quickly and are only needed in special circumstances.
Okay, now you've got your GS dump, what do you do with it?
In the "snaps" folder of PCSX2 you will find two files with the name being like "gsdx_20150408134014" and the extensions being .gs and .png. The PNG is an image file snapshot of what you recorded. The .gs is the GS dump itself. First you should rename these files to something meaningful. This is important! An example might be "FFX text bug.*" for the text issue in FFX. The .* is the original extension, leave those as is. Make sure to include the game name in the file name so the devs can keep their stuff sorted nicely. Then take both of these files and compress them(e.g. with 7zip, WinRAR or whatever you like). Then upload them to a file sharing service like Dropbox.
Now you are ready to rock. If someone simply asked you to provide one, give them the link and that's it. Otherwise if you are reporting an issue for the first time, go to the GSdx thread. Make a new post there and link your GS dump along with providing a nice description of the issue. Don't expect things to be fixed instantly, but the more GS dumps and information the devs have, the more progress can be made!
That's pretty much it!
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD