Emulator Issues #8833
closedRevision 4.0-6204 breaks Metroid Prime depth effects in D3D
0%
Description
Game Name?
Metroid Prime
Game ID?
GM8E01
What's the problem? Describe what went wrong in few words.
When using revision 4.0-6204 onwards (including 5.0-rc1) certain depth effects are broken in Metroid Prime when using D3D (OpenGL still renders them correctly, however).
What did you expect to happen instead?
For the effects to work in D3D!
What steps will reproduce the problem?
- Start Metroid Prime in 4.0-6204 or higher using the D3D backend
- Go to a large room, so that the broken effect is able to be easily observed
Which versions of Dolphin did you test on?
4.0-6204 and higher
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Yes, 4.0-6192
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Windows 8.1
Intel i5 4670K
Nvidia GTX 770
8GB RAM
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Screenshots:
4.0-6192: http://i.imgur.com/sTC3VtJ.png
4.0-6204: http://i.imgur.com/NqsTXsM.png
Updated by pauldacheez over 9 years ago
- Status changed from New to Accepted
- Regression set to Yes
- Priority set to High
- Category set to gfx
- Milestone set to Current
The same change also broke scanning on D3D in the other two Prime games, so this isn't surprising in the slightest.
https://github.com/dolphin-emu/dolphin/commit/ca7fe09f1adda29b8ac76ffa492b2d1e96649e6b
Updated by JMC4789 about 9 years ago
Issue 8863 has been merged into this issue.
Updated by Armada about 9 years ago
Please test this build: http://dl.dolphin-emu.org/prs/pr-2855-dolphin-latest-x64.7z
Updated by mempf.com about 9 years ago
Here is what the same room looks like with the pr-2855 test build.
http://i.imgur.com/cvOMj0P.jpg
It looks much better than before but not perfect. The effect looks worse with AF filtering above x1 or higher than native render resolution.
Updated by Armada about 9 years ago
- Status changed from Accepted to Fix pending
- Milestone deleted (
Current)
This issue is caused by bad drivers, but PR 2855 will likely be merged for cosmetic reasons anyway.
Updated by ZephyrSurfer almost 9 years ago
PR 2855 was merged some time ago.
It was a revert of what caused this issue.