Emulator Issues #12033
Scan Visor starts scan on something not focused
Metroid Prime 2: Echoes
Game ID? (right click the game in the game list, Properties, Info tab)
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
Base Game ISO: ce781ad1452311ca86667cf8dbd7d112
Menu Mod ISO: 6f7a0e2e7182248841a87b2809ce674e
What's the problem? Describe what went wrong.
When scanning an object, sometimes the game will start scanning something entirely different and not centered at all. This includes focusing on this object.
What steps will reproduce the problem?
Use attached save file. This save file requires a Menu Mod ISO (https://github.com/henriquegemignani/echoes-menu-mod-gui).
Start save file 3, which starts directly in Training Chamber. Screw Attack to the statue, fall down behind it and then try to scan the green Luminoth Lore to the left from as far possible. Samus will instead focus on the white door to the right, potentially with the statue between you and the door.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Bug can be found on:
* 5.0-11608 with DX11 and GC Controller Adapter
* 5.0-11608 with Vulkan and non-GC controller (different computer as well)
Is the issue present in the latest stable version?
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
See attached fifolog
What are your PC specifications? (CPU, GPU, Operating System, more)
Windows 10 x64 1909
AMD Ryzen 5 2600 Six Core Processor
32 GB RAM
NVIDIA GeForce GTX 970
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Sometime near 5.0-522 the bug got easier to reproduce, not needing to be as distant from the target.
If internal resolution is Native and Anti-Aliasing is None, the bug is gone.
If either of these is customized, the bug occurs.
(but internal resolution at 3x works?)