Project

General

Profile

Actions

Emulator Issues #10838

closed

Higher Internal Resolution Causes Graphical Glitches in PMTTYD Jabbi Rooms

Added by Techjar about 6 years ago. Updated about 5 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:
5.0-9822

Description

Game Name?

Paper Mario: The Thousand-Year Door

Game ID? (right click the game in the game list, properties, info tab)

G8ME01

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

db9a997a617ee03bbc32336d6945ec02

What's the problem? Describe what went wrong.

When using any internal resolution above native, some strange graphical glitching will happen to the Puni EFB copies, seen here:

This glitching only affects a few specific frames of the idle animation, and always the same frames. I have tested turning various hacks/enhancements on and off, and have narrowed it down to just internal resolution. It affects both OpenGL and Vulkan (can't test D3D as I'm on Linux), though Vulkan seems to require more effort to cause it, as will be explained below. Software renderer is obviously unaffected as it doesn't support higher than native internal resolution.

What steps will reproduce the problem?

Download the attached GCI save file, and load the creatively named save file "Balls". Head right from the save block and take the pipe to the catwalk above, then head into the doorway on the right. This is the Jabbi room, the glitch should be immediately apparent here, unless you're using Vulkan. For Vulkan, it's a bit more involved; head to the left on the catwalk (you'll need to take out the Piders hanging from above to get the Punies past), and enter the doorway once you reach it. This is the 100 Jabbi room, which should make the issue immediately apparent on Vulkan as well as OpenGL.

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

Most definitely, though I specifically tested on 5.0-6229.

Is the issue present in the latest stable version?

Yes.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

N/A

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

Not useful here, since the issue will always appear in a fifolog due to the glitch being baked into the GPU commands.

What are your PC specifications? (CPU, GPU, Operating System, more)

Arch Linux (Antergos)
Intel Core i7-7700K @ 4.5 GHz
NVIDIA GeForce GTX 1080 w/ driver 387.34

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

I included some savestates just outside each doorway for convenience, but you'll of course need 5.0-6229 to load them. The issue will happen or not each time you enter the Jabbi room, depending on whether or not you're above native internal resolution. Get them here because the size is >5MB: https://qimg.techjargaming.com/f/ZaWI9mVI.7z


Files

pmttyd_bug_save.gci (136 KB) pmttyd_bug_save.gci Techjar, 01/28/2018 06:52 AM
Actions #1

Updated by JMC4789 almost 6 years ago

  • Status changed from New to Accepted

I can at least confirm this even though there's been no progress to move it out of the new queue.

Actions #2

Updated by Techjar about 5 years ago

No progress has been made on this, but I can confirm it still happens on the latest master, which is 5.0-9779 at the time of writing this.

Actions #3

Updated by Stenzek about 5 years ago

  • Status changed from Accepted to Fix pending
Actions #4

Updated by Stenzek about 5 years ago

  • Status changed from Fix pending to Fixed
  • Fixed in set to 5.0-9822
Actions

Also available in: Atom PDF