Emulator Issues #8247
closedD3D: Anti-aliasing breaks Scan Visor in MP2
0%
Description
[READ THIS: https://forums.dolphin-emu.org/showthread.php?pid=276132 <<<
Your answers are there!]
[Leave the questions as they are and answer them in the next line]
[Remove lines written inside brackets [], but nothing else]
Game Name?
Metroid Prime 2 Echoes
Game ID?
G2ME01
What's the problem? Describe what went wrong in few words.
With the Direct3D backend, enabling Dolphin's internal anti-aliasing in Metroid Prime 2 causes the Scan Visor to only work on some scannable objects; others simply don't register. This does not affect OpenGL.
What did you expect to happen instead?
I expect the Scan Visor to work regardless of AA settings.
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
- Set D3D as the video backend
- Enable AA from within Dolphin, at any level
- Start MP2 and attempt to utilize the Scan Visor.
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-5184, 4.0-5427, 4.0-5429, 4.0-5460, 4.0-5561
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Any version prior to 4.0-5429 does not exhibit this buggy(?) behavior.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
OS: Windows 8.1 x64
CPU: Intel Core i7-4770k @4.4Ghz
GPU: Nvidia GeForce GTX 970, driver version 347.52
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
[Upload big files to a hosting service and post links here!]
Here is a GCI. Save file 3 starts you at Samus's spaceship; merely switch to the Scan Visor and attempt to scan any of the nearby pillars to reproduce the issue.
https://drive.google.com/file/d/0By1uH7c4LapPdm5XSHRzUlRoRjg/view?usp=sharing
[Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images and pastie.org for logs. Monitor the
email address that was used to create this issue.]
Updated by magumagu9 almost 10 years ago
I'm pretty sure the problem here is that FramebufferManager::GetResolvedEFBDepthTexture isn't working as advertised; these are exactly the same symptoms we saw when I broke depth copies on D3D. See https://github.com/dolphin-emu/dolphin/pull/2023 .
Not sure why exactly it isn't working.
Updated by Armada almost 10 years ago
The problem is likely that GetResolvedDeptbTexture is incorrectly using DXGI_FORMAT_R8G8B8_UNORM instead of DXGI_FORMAT_R24G8_TYPELESS.
Updated by Armada almost 10 years ago
Please test this build: http://dl.dolphin-emu.org/prs/pr-2082-dolphin-latest-x64.7z
Updated by autofire372 almost 10 years ago
Unfortunately, that build does not fix this issue.
Updated by Armada almost 10 years ago
- Status changed from New to Accepted
Please try the new build, it has been updated.
Updated by leosmendes almost 10 years ago
I'm using version 4.0 5843 and the problem still persists also in prime medroid game "mp1"
Updated by leosmendes almost 10 years ago
to shoot with "charge bean" accumulated is formed a square blurred on the screen too ... (MP1)
Updated by JMC4789 almost 9 years ago
- Status changed from Accepted to Fix pending
- Milestone set to Current
Should be Milestone current, and it's fixed in PR 3652, https://github.com/dolphin-emu/dolphin/pull/3652
Updated by JosJuice almost 9 years ago
- Regression changed from No to Yes
According to the issue description, no. "Any version prior to 4.0-5429 does not exhibit this buggy(?) behavior."
Updated by autofire372 almost 9 years ago
Fog wrote:
What's holding this PR back?
The 5.0 feature freeze.
Updated by JosJuice almost 9 years ago
Also fixed in https://github.com/dolphin-emu/dolphin/pull/3745