Project

General

Profile

Actions

Emulator Issues #11215

closed

Metroid Prime Trilogy (1 and 2, 3 is not effected) visual glitch

Added by okinan almost 6 years ago. Updated over 5 years ago.

Status:
Invalid
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 Trilogy

Game ID?
R3ME01 (0001000052334d45)

MD5 Hash?
4f1499bbcf71de8992c4428c918e29ec

What's the problem? Describe what went wrong.
Attempt to play Metroid Prime (1) or Metroid Prime 2: Echoes and you will see that once it starts rendering the actual game world (not the menu) there will be an inverted color square taking up 1/4 of the screen on the upper left. As far as I can tell there are no other problems, but this makes the game not very fun to play.
You will also notice that once it starts loading the game, a pink screen will appear and then go.

What steps will reproduce the problem?
Attempt to play Metroid Prime (1) or Metroid Prime 2: Echoes on Metroid Prime Trilogy. Enable Vulkan. (On AMD?)

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
5.0-8074

Is the issue present in the latest stable version?
No.

If the issue isn't present in the latest stable version, which is the first broken version?
I can't say, but I do know it has nothing to do with the uber shaders or asynchronous shaders. I couldn't replicate on OpenGL, but it would crash instead.

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
Screenshot
(Too big to upload here)
Fifolog: https://my.mixtape.moe/nrgcjt.dff

What are your PC specifications?
OS: NixOS 18.09.git.3daa0db (Jellyfish) x86_64
Kernel: 4.14.48
Uptime: 5 hours, 16 mins
Packages: 1885
Shell: zsh 5.5.1
Resolution: 1920x1200, 1920x1080
DE: KDE
WM: KWin
Theme: Breeze Dark [KDE], Breeze-Dark [GTK2/3]
Icons: Breeze-dark [KDE], Breeze-dark [GTK2]
Terminal: konsole
CPU: AMD Ryzen 7 1700X (16) @ 3.800GHz
GPU: AMD RX 560
Memory: 3364MiB / 15981MiB

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Not that I can think of. I have everything in a pretty vanilla state and have already tested to see if anything changed this issue.
It's probably just a typo or something silly in the code.


Files

R3ME01-1.png (2.83 MB) R3ME01-1.png okinan, 06/09/2018 11:56 PM
Actions #1

Updated by okinan almost 6 years ago

I found something critical to maybe solving this issue.
If you use the scan visor, the problem goes away, but comes right back once you back into normal combat visor on Metroid Prime 2: Echoes.
I have not tested this with Prime 1 or with other visors.

Actions #4

Updated by JMC4789 almost 6 years ago

  • Status changed from New to Questionable

That's the EFB Copy region of the game. It may be one of our fallbacks failing or a driver issue, but I can't confirm for sure.

Actions #5

Updated by okinan almost 6 years ago

JMC4789 wrote:

That's the EFB Copy region of the game. It may be one of our fallbacks failing or a driver issue, but I can't confirm for sure.

Is there any information I can give you, or any settings I can attempt?

glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.19.0 / 4.14.48, LLVM 6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.3
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.0.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

glxinfo | grep direct
direct rendering: Yes
GL_ARB_depth_clamp, GL_ARB_derivative_control, GL_ARB_direct_state_access,
GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect,
GL_ARB_indirect_parameters, GL_ARB_instanced_arrays,
GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect,

Please see the two files in this directory for information on how dolphin-emu is packaged on NixOS: https://github.com/NixOS/nixpkgs/tree/master/pkgs/misc/emulators/dolphin-emu

Actions #6

Updated by okinan almost 6 years ago

Could this have anything to do with it?

WARNING: radv is not a conformant vulkan implementation, testing use only.
WARNING: radv is not a conformant vulkan implementation, testing use only.
WARNING: radv is not a conformant vulkan implementation, testing use only.
WARNING: radv is not a conformant vulkan implementation, testing use only.
mesa: for the -simplifycfg-sink-common option: may only occur zero or one times!

Actions #7

Updated by Techjar almost 6 years ago

Can you please upload the fifolog somewhere else? The link you provided is broken.

Actions #8

Updated by okinan almost 6 years ago

Here, I'll just use Google Drive.
Also whenever switching DOLs (menu to prime 1/2), the wiimote will shut off and has to be pressed again to turn on, as well as the magenta screen.
https://drive.google.com/open?id=1a3mH_LxWQSgKCINs6JNqyaKiHegH6gDP

Actions #9

Updated by okinan over 5 years ago

Looks like it was an issue with mesa/libdrm on my side.
We can probably close this, not a dolphin issue, since the same dolphin commit wasn't working before, but is now after the upgrade.

Actions #10

Updated by JosJuice over 5 years ago

  • Status changed from Questionable to Invalid
Actions

Also available in: Atom PDF