Skip to content

How to find a graphic issue with the GE debugger

Unknown W. Brackets edited this page Jan 28, 2016 · 5 revisions

A lot of graphical issues can be caught with the GE debugger. Finding them gives a good picture of what's wrong, which makes it a lot easier to try and fix the issue.

Some issues, like the screen showing entirely black, may not be graphical issues and only appear to be. This method only helps find issues that are rendering related. It also only works on Windows (or WINE), currently.

  1. Find the issue. Get where you can see it or create a savestate right before it happens.

  2. Open the GE Debugger. Go to Debug -> GE Debugger.

  3. Click "Step Frame" to stop at the start of the next frame.

  4. Click "Step Prim" until you see the area that is being drawn improperly highlighted in red. Make sure ONLY the wrong area is red - if the entire screen is red, it's keep hitting Step Prim.

  5. If that takes too long, you can click "Step Tex" or "Step Draw" to go faster. But, you eventually need to click "Step Prim" and have it highlight the area that has the problem. If you pass it with "Step Tex", you'll have to start over from "Step Frame".

  6. Copy (screenshot is fine, Ctrl-C also works) each of the tabs in the GE debugger. It's a good idea to resize the height tall as possible if doing screenshots. Especially important are Settings and Texture. A screenshot of the previews at the top is also helpful (the left one is the current texture.)

  7. Post these in a bug. You can drag and drop into GitHub issues to upload, or put them on some external site (https://gist.github.com/ is highly recommended), up to you.

  8. It's a good idea to click "Step Draw" to double check that what you found was actually drawn incorrectly (in case it is instead drawn on top of later, incorrectly - if it is, you need the log info from that.)

You can’t perform that action at this time.