Update title capitalization and styling.
parent
a9c1c8bb02
commit
6db4f9fabc
|
@ -1,5 +1,4 @@
|
|||
## Introduction
|
||||
---
|
||||
|
||||
FifoPlayer is a powerful developer tool for debugging graphics related issues. It can be used to record an emulated scene during emulation and to playback it arbitrarily often later on.
|
||||
Furthermore, it allows for close inspection of each FIFO command sent to the GPU during emulation.
|
||||
|
@ -8,9 +7,7 @@ Users can just record a FIFO log and give it to devs, who can analyze the render
|
|||
Also, having an automatically formatted FIFO command list very much eases the task of figuring out how a specific game's graphics are rendered and where it goes wrong in Dolphin.
|
||||
FifoPlayer can restrict the render output to the objects of interest, effectively cleaning up any irritating "unrelated" objects.
|
||||
|
||||
|
||||
### How to record a FIFO log
|
||||
---
|
||||
## How to Record a FIFO Log
|
||||
|
||||
All of the FifoPlayer functionality requires a FIFO log to be recorded. This basically intercepts all commands sent to the GPU during the recording and stores them in a `.dff` file to allow easy playback and inspection.
|
||||
|
||||
|
@ -23,9 +20,7 @@ All of the FifoPlayer functionality requires a FIFO log to be recorded. This bas
|
|||
- Scenes involving texture preloading can only be recorded properly since revision 3.5-173 ([198d60c5](https://github.com/dolphin-emu/dolphin/commit/198d60c5)).
|
||||
- When sharing FIFO logs with others, you should always post a screenshot of the recorded scene since FIFO logs aren't guaranteed to play back equally on all systems.
|
||||
|
||||
|
||||
### How to play back a FIFO log
|
||||
---
|
||||
## How to Play Back a FIFO Log
|
||||
|
||||
Developers will want to use this to see if they can reproduce issues locally. But it's also useful for users to verify that their recorded FIFO log actually works.
|
||||
|
||||
|
@ -38,9 +33,7 @@ Developers will want to use this to see if they can reproduce issues locally. Bu
|
|||
- WARNING: Dual Core mode is currently broken when using FifoPlayer. As a workaround, disable DC and set framelimit to a fixed value, e.g. 30.
|
||||
- tl;dr: Disable Dual Core, Disable XFBs, set framelimit to 30.
|
||||
|
||||
|
||||
### How to analyze a FIFO log
|
||||
---
|
||||
## How to Analyze a FIFO Log
|
||||
|
||||
This is purely a developer tool because it requires strong knowledge of what GPU registers are and how they are used in the GPU FIFO.
|
||||
|
||||
|
@ -48,4 +41,4 @@ This is purely a developer tool because it requires strong knowledge of what GPU
|
|||
- You should see three columns there: The leftmost one will show you a list of rendered frames. The mid column lists all objects within the selected frame. The right column shows all FIFO commands called for that object. When selecting one of the FIFO commands, a more or less descriptive explanation will be shown at the bottom of the dialog.
|
||||
- Note that the FIFO command list is a tad unintuitive: The first command should generally be a vertex draw command (e.g. 0x80) which is the one which actually draws the command, while the FIFO commands after that refer to any state changes after that (i.e. they actually apply to the next object).
|
||||
- There's also a search function that allows you to search within the currently shown command list (i.e. not across different objects/frames). It's a bit buggy at the moment, so it takes some time to get used to.
|
||||
- The currently selected FIFO command can be copied to clipboard by pressing CTRL+C
|
||||
- The currently selected FIFO command can be copied to clipboard by pressing CTRL+C
|
Loading…
Reference in New Issue