Emulator Issues #9958
closed
Software Renderer: Adventures of Lolo corrupted graphics
0%
Description
Game Name?
Adventures of Lolo
Game ID? (right click the game in the game list, properties, info tab)
FBUE01
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
065d1169f75eadca567ab781c022f409
What's the problem? Describe what went wrong.
See attached FIFO logs. Incorrect graphics in both DX11 and SW. The other backends do not appear to have this problem.
What steps will reproduce the problem?
Start the game and watch the introduction
Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?
5.0-1473
What are your PC specifications? (CPU, GPU, Operating System, more)
Win 10 Pro x64
Intel Core i7-4702MQ CPU @2.20GHz
GeForce GT 750M
2x 8GB Hynix 1600MHz
GeForce Game Ready Driver 376.19
Files
Updated by JMC4789 over 7 years ago
If I remember correctly, the SW renderer should only be missing graphics in debug mode for unknown reasons.
The D3D portion of this bug is a driver bug and invalid. It's not Dolphin's responsibility.
Updated by ryanebola16 over 7 years ago
Debug mode and non-debug mode produced the same results. Just checking, if the 3D3 portion is a driver bug it should only effect DX11 and not DX12 right? DX12 does not have this problem.
It sounds like SW will need to be looked into further though.
Updated by JMC4789 over 7 years ago
D3D12 will hit the bug occasionally too.
SW needs to be looked into.
Updated by ryanebola16 over 7 years ago
Alright. Also, how did you determine that the D3D issue was a known driver bug? This information could be helpful for avoiding duplicate reports from me in the future.
Updated by Stenzek over 7 years ago
It only happens on nvidia, and not every time. Sometimes if you flush the GPU, it stops it from occurring (at a performance loss, of course), but even then occasionally it still does. Even reducing the test case to a single draw still caused the bug to happen. I wasn't interested enough in the D3D11 backend to bother spending any more time on it.
Updated by ryanebola16 over 7 years ago
Sorry, but I haven't done FIFO analysis before. I'm assuming that a single draw refers to an object range of 0-1? The DX11 FIFO log showed "Stream size doesn't match actual data length" in a few places. Does that mean "Stream size doesn't match actual data length" is the known nvidia bug?
Updated by Stenzek over 7 years ago
I was looking at the individual draw call level, not at the fifolog object level. Nothing I tried changing made any difference, so I'm not saying with 100% certainty that there isn't a bug on Dolphin's side, but it's not worth looking into considering it doesn't happen on any other vendor or backend (and D3D11 is the slowest backend).
Updated by ryanebola16 about 5 years ago
I can't reproduce the D3D issues in 5.0-1473 or 5.0-9618 anymore. Problem doesn't exist with:
Win 10 Pro x64
Intel Core i7-4702MQ CPU @2.20GHz
GeForce GT 750M
2x 8GB Hynix 1600MHz
GeForce Game Ready Driver 418.91
I still reproduced the software renderer issues though. Please update the title to "Software Renderer: Adventures of Lolo corrupted graphics"
Updated by ryanebola16 over 4 years ago
Please update the title to "Software Renderer: Adventures of Lolo corrupted graphics"
Updated by JosJuice over 4 years ago
- Subject changed from DX11 and SW: Adventures of Lolo corrupted graphics to Software Renderer: Adventures of Lolo corrupted graphics
Updated by ZephyrSurfer about 3 years ago
This was fixed recently in Software Renderer, however the fifologs provided here seems to have the issues baked in. If I create a fifolog on the version that solved the issue and bring it back to a revision that should be broken you will find that it is not broken on playing back the fifolog file.
Fixed in 5.0-13717 -> https://dolphin-emu.org/download/dev/a0be1c93ea838461cd88049a9af86b5c81b5b435/
Updated by JosJuice about 3 years ago
- Status changed from New to Fixed
- Fixed in set to 5.0-13717