Emulator

Did you perhaps open your graphic settings window after running the game? That overrides the default settings for the game, it needs efb to ram for the scan visor to work properly.

It could be anti-aliasing causing it.

Yeah, anything that changes how the game looks could cause this. So disable AA, AF, force filtering, per pixel lightning etc. and try again.

I did not open the graphic settings while playing the game.

I have the following enhancements enabled:

forced texture filtering
Scaled EFB copy

The visor works on OpenGL but its slow as hell

Also The latest iteration does not have EFB to RAM only option.

All it says : Store EFB copies to Texture only.

Disabling this option says "Store EFB copies to RAM (and Texture)"

I have disabled this option

I WOULD LIKE TO CLEARLY STATE THE FACT THAT THE SCAN VISOR IN ECHOES AND CORRUPTION WORKS PERFECTLY FINE IN 4.0-6312 IN DIRECT3D !!! There Seems to be a problem after that i guess since 6535 does not work properly.

Someone Please look into the problem in the latest versions of the emulator regarding the scan visor problem in Direct 3D

The most interesting thing I can see in there is depth inversion for D3D. If toggling "Fast Depth Calculation" on/off has any effect, you can probably blame 4.0-6422. https://github.com/dolphin-emu/dolphin/commit/0b61a0dfc591cbbac7a450bb8b5a7166c9504e51

@pauldacheez

You are right !!! It is because of the version that brought about D3D Deapth Inversion as the issue only seems to occur after that change was brought in. I believe that the develpers should be notified of this issue before the next STABLE iteration is launched. I tested 15 different versions and tried to pinpoint the issue and managed to hit the nail on the head with the D3D deapth inversion. Versions before 6422 work perfectly fine running Metroid Prime Trilogy in 1080p.

Can confirm in my testing Dolphin 4.0-6422 broke the scan visor for many objects in MP2 and MP3.

Issue 8863 has been merged into this issue.

This is more a note for me than anyone else.

This is broken again in master.... In the 5.0 release everything works as expected, but when playing on master, the scan visor will scan seemingly random objects in a room. I'll start bisecting this to see where it breaks. I can get an upload of the problem sometime this week (assuming it's needed).

Krakn, that problem is already tracked as https://bugs.dolphin-emu.org/issues/10235

Hi everyone. I'm not a developer and I don't know how bug tracking works so I apologize if it's rude to post this here, but since this is the first search engine result people will see when trying to find the solution to this "bug," I want to share my solution here.
Rebind L and R as digital buttons instead of analogue triggers.
I experienced this issue while using a Dualshock 4 (PS4 controller) with the L and R shoulder buttons bound as analogue triggers. With this setup, the game would react to squeezing the L button, but it didn't seem to go past the threshold the game wanted to activate the actual scanning. Even if I lowered the threshold in controller settings this would still happen. I also experienced this problem in other games like Pikmin 2 where I couldn't go between menus because you need to "click" L or R all the way in to do so.
Once again I apologize if this is out of place but I don't want people to think Dolphin is broken when it's probably an issue with the DS4 or the DS4Windows program.

It's possible to get the problem of being unable to scan due to not mapping the buttons correctly, but this issue report is about a different reason for being unable to scan. Anyway, I would recommend mapping each button to both the analog and digital variant.