Project

General

Profile

Actions

Emulator Issues #8163

closed

Metroid Prime 2: Scan Visor ignores many objects

Added by Nick.Pelone almost 10 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Metroid Prime 2: Echoes

Game ID?

G2ME01

What's the problem? Describe what went wrong in few words.

Following the game's intro, when gameplay begins, the scan visor is unusable on most items, (eg. Samus' ship). Some items work, but it is entirely hit or miss. Eventually, you will reach one of the "hologram" gates that you must scan in order for it to recede, it will not scan, and you will be unable to proceed.

What did you expect to happen instead?

Items should scan as normal, causing a small progress meter to fill up followed by a giving of details about the item scanned.

What steps will reproduce the problem?

  1. Start Metroid Prime 2: Echoes. Begin a new game, and go through the introduction sequence.
  2. Following this, you will exit Samus' spaceship, and begin first-person play.
  3. Enter the scan visor (use the Control Pad and hit left) and then try to scan Samus' ship by using the L-Trigger.
  4. It won't scan, and you just kinda strafe around.
  5. For an example of an item that will scan, look forward and scan the orb-looking thing in the spider web. It will scan.

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?

Dolphin 4.0-5323 (I build and maintain packages of Dolphin for newer Ubuntus and family, and can test a new code revision easily)

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?

I haven't ever tested this with an old revision.

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)

OS: Linux 3.18.3 (Linux Mint 17)
CPU: Intel Core i7 (4 cores @ 2.10 GHz)
GPU: NVIDIA Geforce GT 650M w/ 2GB VRAM, NVIDIA driver 346.35

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

As this was under Linux, please know this issue occurred under the OpenGL render. All settings are stock / coming from GameINI, save a change of Internal Resolution from 1x to 2x.

Actions

Also available in: Atom PDF