Project

General

Profile

Actions

Emulator Issues #12957

closed

Paper Mario TTYD Crashes when using Direct3D 12

Added by StacyAdam almost 2 years ago. Updated over 1 year 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-17762

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, Verify tab, Verify Integrity button)

db9a997a617ee03bbc32336d6945ec02

What's the problem? Describe what went wrong.

While using the backend Direct3D 12 sometimes during a battle while attacking or being attacked the game will crash with a map resource failed message.

What steps will reproduce the problem?

It doesn't happen with specific enemies or attacks. Any attack can seemingly trigger it, whether it's Mario's, his partners or an enemy. I have had it happen the first battle after I load a save or 20 battle later. It always occurs right as the attack lands.

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

Yes 5.0-16677

Is the issue present in the latest stable version?

Unknown, stable version not tested.

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.)

I tested 5.0-9878 and the bug was present there

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

N/A

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

CPU: Intel i7 11800h 2.3GHz
GPU: Nvidia GeForce RTX 3050
OS: Windows 11 Pro
RAM: 32GB

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


Files

20220620_202421.jpg (824 KB) 20220620_202421.jpg Crash message in 5.0-16677 StacyAdam, 06/22/2022 02:36 AM
Screenshot (1).png (3.01 MB) Screenshot (1).png Crash message in 5.0-9878 StacyAdam, 06/22/2022 02:41 AM
StackTrace.txt (3.43 KB) StackTrace.txt TellowKrinkle, 06/22/2022 03:43 AM
Actions #1

Updated by TellowKrinkle almost 2 years ago

I'm having a similar issue with all DX12-supporting versions of Dolphin crashing on the Wind Waker title screen. I originally blamed it on AMD shipping ancient-looking drivers for macs in bootcamp, but maybe that's not the issue. I've attached a stack trace, which doesn't say much other than that it dies waiting for a readback from the GPU (which may or may not be related to the actual cause). I can confirm that disabling EFB access stops it from crashing.

PC Specs:
CPU: Intel i9-9980HK
GPU: Radeon Pro 5600M (Driver revision 20.45.40.15, which was released in 2022 but is numbered like other AMD drivers from 2020)
OS: Windows 10 21H2 19044.1766

It does not happen on this computer:
CPU: Intel i7-4980HQ
GPU: GT 750M (Driver 425.31)
OS: Windows 10 21H2 19044.1766

Actions #2

Updated by Anonymous over 1 year ago

can't seem to reproduce, with
cpu: amd 3990x
gpu: gtx 1080 (driver DCH 512.15)
os: win 11 pro for workstations 21H2

wind waker title screen uses efb access to draw sunrays, so i'd expect it to happen immediately. maybe sharing more details dolphin gfx settings would be useful?

Actions #3

Updated by JMC4789 over 1 year ago

  • Status changed from New to Fixed
  • Fixed in set to 5.0-17762

A bunch of D3D12 issues were fixed by 5.0-17762 - please let me know if this is still broken.

Actions

Also available in: Atom PDF