Paper Mario: The Thousand-Year Door: Difference between revisions

Jump to navigation Jump to search

Paper Mario: The Thousand-Year Door (view source)

Revision as of 19:19, 16 July 2019

4,783 bytes added ,  16 July 2019
→‎Emulation Information: sync with recent edit on [Super Paper Mario]
(→‎Emulation Information: sync with recent edit on [Super Paper Mario])
(82 intermediate revisions by 26 users not shown)
Line 1: Line 1:
{{Infobox VG
{{Infobox VG
|image       = [[File:PaperMarioTheThousand-YearDoor.jpg|300px]]
|image     = [[File:PaperMarioTheThousand-YearDoor.jpg|300px]]
|developer   = Intelligent Systems
|developer = Intelligent Systems
|publisher    = Nintendo
|publisher = Nintendo
|released     = {{vgrelease|JP=July 22, 2004|NA=October 11, 2004|EU=November 12, 2004|AUS=November 18, 2004}}
|series   = Paper Mario
|series      = ''Paper Mario''
|released = {{vgrelease|JP=July 22, 2004|NA=October 11, 2004|EU=November 12, 2004|AUS=November 18, 2004}}
|genre       = Role-playing
|genre     = Role-playing
|modes       = Single-player
|modes     = Single-player
|input       = GameCube Controller
|input     = GameCube Controller
|forumlink   = http://forums.dolphin-emu.org/Thread-gc-paper-mario-the-thousand-year-door
|forumlink = http://forums.dolphin-emu.org/Thread-gc-paper-mario-the-thousand-year-door
}}
}}


'''''Paper Mario: The Thousand-Year Door''''', released in Japan as ''Paper Mario RPG'', is a console role-playing game developed by Intelligent Systems and published by Nintendo for the [[Nintendo GameCube]]. ''The Thousand-Year Door'' is the fourth Mario RPG and the second in the ''Paper Mario'' series.
'''''Paper Mario: The Thousand-Year Door''''', released in Japan as '''''Paper Mario RPG''''', is a console role-playing game developed by Intelligent Systems and published by Nintendo for the [[Nintendo GameCube]]. ''The Thousand-Year Door'' is the fourth Mario RPG and the second in the ''Paper Mario'' series.


== Emulation Information ==
== Emulation Information ==
=== Requires Bounding Box ===
=== Bounding Box Slowdown on NVIDIA Cards ===
A large portion of this game requires bounding box emulation. Without bounding box emulation, there will be graphical errors, crashes, and other issues throughout the game.  It is not recommended to ever disable bounding box emulation while playing this game.
NVIDIA cards are abnormally slow during Bounding Box effects even at very low internal resolutions when using D3D11. They get dramatically slower as the internal resolution increase, even though comparable AMD graphics cards suffer no slowdown at all.  This is due to Dolphin hitting a slow path on those graphics cards. It is recommended that supported NVIDIA users use other video backends when playing games that require Bounding Box emulation to avoid that.


{{Image|TTYD-DisabledBB.png|Disabled Bounding Box (Tube Mode)}}
=== When Using Older Graphics Cards ===
{{Image|TTYD-EnabledBB.png|Enabled Bounding Box (Tube Mode)|br}}
This game uses a feature known as "Bounding Box", which Dolphin typically uses Shader Storage Buffer Objects (SSBO) to emulate. This requires a NVIDIA GeForce 400 series or newer, a AMD/ATI Radeon HD 5000 series or newer, or a Intel Broadwell Integrated GPU (Intel HD 5300+) or newer and an operating system that supports OpenGL 4.3, D3D11, GLES 3.1, or Vulkan. On macOS, MoltenVK can be used to attain Vulkan support on the latest builds. If Bounding Box is not emulated correctly, the game will show severe graphical glitches and won't be playable to finish.


=== Glitched Transitions ===
{{Image|TTYD-DisabledBB.png|Broken Bounding Box}}
Most transition effects will show only garbage. Disable '''EFB Copies to Texture Only''' to prevent that.<br>
{{Image|TTYD-EnabledBB.png|Working Bounding Box|br}}
Note: In some cases the game will actually crash if you have ''EFB Copies to Texture Only'' enabled.
{{image|Paper Mario TTYD - Cabin Transition EFB2Tex.gif|Transition /w '''EFB Copies to Texture Only'''}}
{{image|Paper Mario TTYD - Cabin Transition EFB2RAM.gif|Proper emulation|br}}


=== Bounding Box Slowdown on NVIDIA Cards ===
Because Dolphin has gone through many variants of Bounding Box support throughout its history, it may be possible for older graphics cards to use less accurate versions of Bounding Box present in older builds.  On Android, {{revision|5.0-9322}} or newer is required for Bounding Box to function at all due to an unrelated bug. Please note that other driver issues can often cause issues with Bounding Box emulation, which can produce similar bugs to having no Bounding Box support whatsoever. In this case, updating drivers or using a different video backend may be your only recourse.
NVIDIA cards are abnormally slow during bounding box effects even at very low internal resolutions when using D3D11. They get dramatically slower as the internal resolutions increase, even though comparable AMD graphics cards suffer no slowdown at all.  This is due to Dolphin hitting a slow path on those graphics cards. It is recommended that supported NVIDIA users use D3D12 or OpenGL backends when playing games that require Bounding Box emulation to avoid that.


=== Problems When Using Older Graphics Cards ===
=== Riverside Station Sunset Effect ===
Bounding Box emulation requires GPU-specific features that are not present on older GPUs (older than 3rd quarter 2012). As such, graphics cards without Direct3D 11 or OpenGL 4.3 support are no longer supported. In essence, only computers with GPUs: NVIDIA GeForce 400 series and newer, AMD/ATI Radeon HD 5000 series and newer, and Broadwell integrated GPUs (Intel HD Graphics 5300+) are supported by Dolphin for games requiring certain bounding box implementations. Additionally, OS X cannot be used, because no GPU drivers for OS X support the required features as of July 2016.
The sunset effect in Riverside Station has a defect where non-static objects in front of it have a trail of ghosts coming off. This is not a bug in Dolphin, but a defect inherent to the way the effect is achieved, as it appears on console too. The defect is very hard to see on console (it's right above the rock in the image below) due to the low resolution and analog quality loss, but the higher internal resolution and custom HD textures allowed by Dolphin make it very obvious.


Using newer revisions with unsupported GPUs or drivers will lead to graphical glitches and softlocks. If game-breaking bugs are experienced, use revision {{revision|4.0-5124}} or lower as a workaround. For more information, refer to {{Issue|8405}}, {{Issue|8505}}, {{Issue|8270}}.
{{Image|PMTTYD-SunsetEffectEmulator.png|Defect as seen on Dolphin}}
{{Image|PMTTYD-SunsetEffectConsole.png|Defect as seen on console|br}}


== Problems ==
== Problems ==
{{Problems|{{#vardefineecho:problems|
=== PAL60 Reverting to 50Hz ===
If the PAL version of the game has been set to run at 60 Hz, it may change back to 50Hz under some circumstances. Turn off the dual core setting to avoid this issue.
=== <s>Merluvee Next Path</s> ===
When using the D3D backend, asking Merluvee to tell you the next path may freeze the game. This does not occur on OpenGL or Vulkan, so use them to avoid this issue.
Fixed in revision {{revision|5.0-9638}}.
}}}}


== Enhancements ==
== Enhancements ==
=== HD Texture Pack ===
There is a work-in-progress high definition texture modification for [https://forums.dolphin-emu.org/Thread-paper-mario-ttyd-hd-texture-pack-v0-9b-december-4-2016 The Thousand Year Door on the Dolphin forums].
=== 16:9 Aspect Ratio Fix ===
=== 16:9 Aspect Ratio Fix ===
The built-in Widescreen Hack causes clipping issues. The following Gecko codes work as a replacement, causing less issues. To avoid conflicts, make sure that Widescreen Hack is disabled while using these codes.
The built-in Widescreen Hack causes clipping issues. The following codes work as a replacement, causing fewer issues. To avoid conflicts, make sure that Widescreen Hack is disabled while using these codes.
 
==== AR Code Fix ====
This code does not speed up the game in the Shhwonk Fortress.
<pre>
NTSC-J:
044195F8 3FE38E39
</pre>
 
<pre>
NTSC-U:
0441F6D8 3FE38E39
</pre>
 
<pre>
PAL:
0442C158 3FE38E39
</pre>
 
===== Gecko Codes =====
==== Centered HUD ====
<pre>
NTSC-J:
C202ECEC 00000003
3DC08042 3DE03FD8
91EE95F8 4E800020
60000000 00000000
C200F354 00000003
3DE08081 3DC0402B
61CE12A2 91CF65BC
387D015C 00000000
C200F35C 00000003
3DE08081 3DC04063
61CEE8D3 91CF65BC
7FC3F378 00000000
04193838 4E800020
</pre>
 
<pre>
NTSC-U:
C202F310 00000003
3DC08042 3DE03FD8
91EEF6D8 4E800020
60000000 00000000
C200F500 00000003
3DE08082 3DC0402B
61CE12A2 91CFA1BC
387D015C 00000000
C200F508 00000003
3DE08082 3DC04063
61CEE8D3 91CFA1BC
7FC3F378 00000000
04199598 4E800020
</pre>
 
<pre>
PAL:
C202F3F8 00000003
3DC08043 3DE03FD8
91EEC158 4E800020
60000000 00000000
C200F6C4 00000003
3DE08086 3DC0402B
61CE12A2 91CFB0DC
387D015C 00000000
C200F6CC 00000003
3DE08086 3DC04063
61CEE8D3 91CFB0DC
7FC3F378 00000000
0419B274 4E800020
</pre>
 
==== Stretched HUD ====
This code also speeds up the emulator in the Shhwonk Fortress.
This code also speeds up the emulator in the Shhwonk Fortress.
<pre>
NTSC-J:
C202ECEC 00000003
3DC08042 3DE03FD8
91EE95F8 4E800020
60000000 00000000
04193838 4E800020
</pre>


==== NTSC-J ====
<pre>
<pre>04193838 4E800020
NTSC-U:
044195F8 3FE38E39</pre>
C202F310 00000003
 
==== NTSC-U ====
<pre>C202F310 00000003
3DC08042 3DE03FD8
3DC08042 3DE03FD8
91EEF6D8 4E800020
91EEF6D8 4E800020
60000000 00000000
60000000 00000000
04199598 4E800020</pre>
04199598 4E800020
</pre>


==== PAL ====
<pre>
<pre>0419B274 4E800020
PAL:
C202F268 00000003
C202F3F8 00000003
3DC08043 3DE03FD8
3DC08043 3DE03FD8
91EEC158 4E800020
91EEC158 4E800020
60000000 00000000</pre>
60000000 00000000
0419B274 4E800020
</pre>
 
==== Centered HUD, some letterboxing ====
This code also speeds up the emulator in the Shhwonk Fortress.
<pre>
NTSC-J:
04193838 4E800020
044195F8 3FE38E39
</pre>
 
<pre>
NTSC-U:
04199598 4E800020
0441F6D8 3FE38E39
</pre>
 
<pre>
PAL:
0419B274 4E800020
0442C158 3FE38E39
</pre>


== Configuration ==
== Configuration ==
<!--A full list of options is available at Template:Config/doc-->
{{Config
{{Config
|dualcore = Off
|dualcorenotes = Fixes 60Hz mode reverting to 50Hz in EU version
}}
}}


== Version Compatibility ==
== Version Compatibility ==
{{VersionCompatibility}}
{{VersionCompatibility}}
<!--Use this template for compatibility entries: {{VersionCompatibilityVersion|revision|****|notes}}-->
{{VersionCompatibilityVersion|5350|***|Random freezes, minor graphical glitches}}
{{VersionCompatibilityVersion|5350|***|Random freezes, minor graphical glitches}}
{{VersionCompatibilityVersion|3.0-188|****|Bounding box emulation added}}
{{VersionCompatibilityVersion|3.0-188|****|Bounding box emulation added}}
{{VersionCompatibilityVersion|4.0-707|****|Improved bounding box code but a few issues remain}}
{{VersionCompatibilityVersion|4.0-707|****|Improved bounding box code but a few issues remain}}
{{VersionCompatibilityVersion|4.0-3610|*****|Remaining bounding box issues completely fixed}}
{{VersionCompatibilityVersion|4.0-3610|*****|Remaining bounding box issues completely fixed}}
{{VersionCompatibilityVersion|5.0|****|Several issues. Probably since 5.0}}
{{VersionCompatibilityClose}}
{{VersionCompatibilityClose}}


Line 92: Line 206:
{{testing/entry|revision=3.0-801|OS=Windows 7|CPU=Intel Core 2 Quad Q9550|GPU=NVIDIA GeForce 560 Ti|result=Playable: full speed with minor drops, tons of audio glitches, LLE is too demanding for my system, enabling Accurate Vbeam Emulation seems to help with the sound. The music is also way too loud and makes it hard to hear some sound effects.|tester=}}
{{testing/entry|revision=3.0-801|OS=Windows 7|CPU=Intel Core 2 Quad Q9550|GPU=NVIDIA GeForce 560 Ti|result=Playable: full speed with minor drops, tons of audio glitches, LLE is too demanding for my system, enabling Accurate Vbeam Emulation seems to help with the sound. The music is also way too loud and makes it hard to hear some sound effects.|tester=}}
{{testing/entry|revision=3.0-863|OS=Windows 7|CPU=Intel Core i7-3770 @ 3.4GHz|GPU=NVIDIA GeForce GTX 670|result=Audio glitches with non-LLE, perfect with LLE. No slowdowns even at higher resolutions (720p). Water at Schwonk Fortress and Punies in the Great Tree still produce graphical errors. EFB to RAM reduces the graphical glitches of the punies to minor at best. Game is 100% playable in it's current state.|tester=}}
{{testing/entry|revision=3.0-863|OS=Windows 7|CPU=Intel Core i7-3770 @ 3.4GHz|GPU=NVIDIA GeForce GTX 670|result=Audio glitches with non-LLE, perfect with LLE. No slowdowns even at higher resolutions (720p). Water at Schwonk Fortress and Punies in the Great Tree still produce graphical errors. EFB to RAM reduces the graphical glitches of the punies to minor at best. Game is 100% playable in it's current state.|tester=}}
{{testing/entry|revision=3.0-936|OS=Windows 8|CPU=Intel Core i5-3570K @ 3.4GHz|GPU=NVIDIA GeForce GTX 560 Ti|result=Really smooth on Direct3D9, unlike many 3.5-x builds I tried which caused random slowdowns all over the place. Use LLE audio to fix various sound issues. To get LLE to work with this 3.0 build, I downloaded dsp_coef.bin and dsp_rom.bin from [http://code.google.com/p/dolphin-emu/source/browse/#git%2FData%2FSys%2FGC the Dolphin Source] and placed it in ./User/GC/. Dolphin will display a warning when launching a ROM saying sound will be garbled because of a wrong hash, but it will be perfectly fine so just press No and play. You can download 3.0-936 from the [https://dl.dolphin-emu.org/oldbuilds/ Dolphin Old Builds].|tester=dani}}
{{testing/entry|revision=3.0-936|OS=Windows 8|CPU=Intel Core i5-3570K @ 3.4GHz|GPU=NVIDIA GeForce GTX 560 Ti|result=Really smooth on Direct3D9, unlike many 3.5-x builds I tried which caused random slowdowns all over the place. Use LLE audio to fix various sound issues. To get LLE to work with this 3.0 build, I downloaded dsp_coef.bin and dsp_rom.bin from [https://github.com/dolphin-emu/dolphin/tree/master/Data/Sys/GC the Dolphin Source] and placed it in ./User/GC/. Dolphin will display a warning when launching a ROM saying sound will be garbled because of a wrong hash, but it will be perfectly fine so just press No and play. You can download 3.0-936 from the [https://dl.dolphin-emu.org/oldbuilds/ Dolphin Old Builds].|tester=dani}}
{{testing/entry|revision=3.5|OS=Windows Vista|CPU=Intel Pentium 4 @ 3.2GHz|GPU=Intel GMA 82945G|result=12~15FPS outside, 20~25FPS in battle due to low-end system. Random crashes. Also when the little things that come at you at the beginning after the first battle they appear as EFB static on all EFB hacks. I was actually surprised to see battles at more FPS. Performance guide settings.|tester=Wiigeek336}}
{{testing/entry|revision=3.5|OS=Windows Vista|CPU=Intel Pentium 4 @ 3.2GHz|GPU=Intel GMA 82945G|result=12~15FPS outside, 20~25FPS in battle due to low-end system. Random crashes. Also when the little things that come at you at the beginning after the first battle they appear as EFB static on all EFB hacks. I was actually surprised to see battles at more FPS. Performance guide settings.|tester=Wiigeek336}}
{{testing/entry|revision=3.5|OS=Windows 7|CPU=AMD FX-4130 @ 4.2GHz|GPU=NVIDIA GeForce GTX 550 Ti|result=Runs at a smooth 60FPS in everything but transitions, and in some cutscenes with big effects.|tester=}}
{{testing/entry|revision=3.5|OS=Windows 7|CPU=AMD FX-4130 @ 4.2GHz|GPU=NVIDIA GeForce GTX 550 Ti|result=Runs at a smooth 60FPS in everything but transitions, and in some cutscenes with big effects.|tester=}}
Line 100: Line 214:
{{testing/entry|revision=3.5-397|OS=Windows 7|CPU=Intel Core i7-3820QM @ 2.7GHz|GPU=AMD FirePro M2000|result=Playable, constant 60FPS with Direct3D9 at 1600x900 resolution.|tester=Shirsakbc}}
{{testing/entry|revision=3.5-397|OS=Windows 7|CPU=Intel Core i7-3820QM @ 2.7GHz|GPU=AMD FirePro M2000|result=Playable, constant 60FPS with Direct3D9 at 1600x900 resolution.|tester=Shirsakbc}}
{{testing/entry|revision=3.5-402|OS=Windows 7|CPU=Intel Core i7-3770 @ 3.4GHz|GPU=NVIDIA GeForce GTX 680|result=Fully Playable without any graphical or Sound issues on 1080p! Played with Widescreen Hack on Direct3D 9 Plugin and DSP LLE Recompiler with DSound.|tester=StarDave}}
{{testing/entry|revision=3.5-402|OS=Windows 7|CPU=Intel Core i7-3770 @ 3.4GHz|GPU=NVIDIA GeForce GTX 680|result=Fully Playable without any graphical or Sound issues on 1080p! Played with Widescreen Hack on Direct3D 9 Plugin and DSP LLE Recompiler with DSound.|tester=StarDave}}
{{testing/entry|revision=3.5-1159|OS=Windows 7|CPU=Intel Pentium G860|GPU=AMD Radeon HD 7770|result=Playable at mostly full speed at 1.5x native, D3D9; and using the new DSP HLE emulation.  Minor visual glitch with reflective water.  No apparent audio problems that existed with HLE in older builds.|tester=}}
{{testing/entry|revision=3.5-1558|OS=Windows 7|CPU=Intel Core 2 Quad Q9550 @ 3.4GHz|GPU=NVIDIA GeForce GTX 660 Ti|result=Playable: 60FPS with OpenGL (1920x1080, 9x SSAA); 60FPS with DirectX 9. Enabling Vsync on D3D9 seems to cut the framerate down to 35-40FPS, and DirectX 11 exhibits the same behavior regardless of Vsync setting (driver bug). HLE audio gets distorted after playing for around two hours and CPU is too slow for LLE. |tester=}}
{{testing/entry|revision=3.5-1558|OS=Windows 7|CPU=Intel Core 2 Quad Q9550 @ 3.4GHz|GPU=NVIDIA GeForce GTX 660 Ti|result=Playable: 60FPS with OpenGL (1920x1080, 9x SSAA); 60FPS with DirectX 9. Enabling Vsync on D3D9 seems to cut the framerate down to 35-40FPS, and DirectX 11 exhibits the same behavior regardless of Vsync setting (driver bug). HLE audio gets distorted after playing for around two hours and CPU is too slow for LLE. |tester=}}
{{testing/entry|revision=3.5-1558|OS=Mac OS X 10.8.4|CPU=Intel Core 2 Quad Q9550 @ 3.4GHz|GPU=NVIDIA GeForce GTX 660 Ti|result=Playable: 50-60FPS (1920x1080). HLE audio stutters since it's not constantly full speed.|tester=}}
{{testing/entry|revision=3.5-1558|OS=Mac OS X 10.8.4|CPU=Intel Core 2 Quad Q9550 @ 3.4GHz|GPU=NVIDIA GeForce GTX 660 Ti|result=Playable: 50-60FPS (1920x1080). HLE audio stutters since it's not constantly full speed.|tester=}}
{{testing/entry|revision=3.5-1558|OS=Windows 7|CPU=Intel Core i7-4650U|GPU=Intel HD Graphics 5000|result=Playable: 55-60FPS with DirectX 9 or 11 (1440x900, without AA); 35-60FPS with OpenGL. LLE audio works well. |tester=}}
{{testing/entry|revision=3.5-1558|OS=Windows 7|CPU=Intel Core i7-4650U|GPU=Intel HD Graphics 5000|result=Playable: 55-60FPS with DirectX 9 or 11 (1440x900, without AA); 35-60FPS with OpenGL. LLE audio works well. |tester=}}
{{testing/entry|revision=3.5-1558|OS=Mac OS X 10.8.4|CPU=Intel Core i7-4650U|GPU=Intel HD Graphics 5000|result=Not really playable; 30-45FPS. |tester=}}
{{testing/entry|revision=3.5-1558|OS=Mac OS X 10.8.4|CPU=Intel Core i7-4650U|GPU=Intel HD Graphics 5000|result=Not really playable; 30-45FPS. |tester=}}
{{testing/entry|revision=3.5-1159|OS=Windows 7|CPU=Intel Pentium G860|GPU=AMD Radeon HD 7770|result=Playable at mostly full speed at 1.5x native, D3D9; and using the new DSP HLE emulation.  Minor visual glitch with reflective water.  No apparent audio problems that existed with HLE in older builds.|tester=}}
{{testing/entry|revision=4.0.2|OS=Windows 7 x68|CPU=Intel Celeron G1610 @ 2.6GHz|GPU=Intel HD Graphics|result=Playable. Glitches even with BBox = true. 40FPS|tester=hivaoa}}
{{testing/entry|revision=4.0.2|OS=Windows 7 x68|CPU=Intel Celeron G1610 @ 2.6GHz|GPU=Intel HD Graphics|result=Playable. Glitches even with BBox = true. 40FPS|tester=hivaoa}}
{{testing/entry|revision=4.0-2109|OS=Windows 7|CPU=AMD FX-4300 @ 4GHz|GPU=AMD Radeon R7 260x|result=Very Playable. Constant 60FPS with all enhancements maxed. No problems using HLE.|tester=Period}}
{{testing/entry|revision=4.0-2109|OS=Windows 7|CPU=AMD FX-4300 @ 4GHz|GPU=AMD Radeon R7 260x|result=Very Playable. Constant 60FPS with all enhancements maxed. No problems using HLE.|tester=Period}}
Line 113: Line 227:
{{testing/entry|revision=4.0-6454|OS=Windows 8.1|CPU=AMD FX-8350 @ 4.04GHz|GPU=AMD Radeon HD 5870|result=Game nearly unplayable. Game runs at 60FPS @ 4x resolution, but lags down to 10 FPS on all backends/resolutions during transition scenes (Boat at the start flipping, going through pipes, ect.) Issue not present in {{revision|4.0-3610}}.|tester=Darklords}}
{{testing/entry|revision=4.0-6454|OS=Windows 8.1|CPU=AMD FX-8350 @ 4.04GHz|GPU=AMD Radeon HD 5870|result=Game nearly unplayable. Game runs at 60FPS @ 4x resolution, but lags down to 10 FPS on all backends/resolutions during transition scenes (Boat at the start flipping, going through pipes, ect.) Issue not present in {{revision|4.0-3610}}.|tester=Darklords}}
{{testing/entry|revision=4.0-8070|OS=Windows 8.1|CPU=Intel Core i5-3210M @ 2.5GHz|GPU=NVIDIA GeForce 610M|result=Direct3D has a few minor graphical glitches. OpenGL no issues.|tester=wildgoosespeeder}}
{{testing/entry|revision=4.0-8070|OS=Windows 8.1|CPU=Intel Core i5-3210M @ 2.5GHz|GPU=NVIDIA GeForce 610M|result=Direct3D has a few minor graphical glitches. OpenGL no issues.|tester=wildgoosespeeder}}
{{testing/entry|revision=4.0-9129|OS=Windows 10|CPU=Intel Core i3-2120 @ 3.3GHz|GPU=NVIDIA GeForce GTX 750 Ti|result=Game runs at a solid 60 FPS up to 2x native resolution using Direct3D11 and the other recommended configuration settings. Drops to 30-35 FPS occur when paper effects are being rendered, excluding Mario and Partners.|tester=SfaFreak}}
{{testing/entry|revision=4.0-9144|OS=Windows 7|CPU=Intel Core 2 Quad @ 2.5GHz|GPU=NVIDIA GeForce GT610|result=Game runs very smoothly as 50 FPS. Have experienced almost no lag. Only frame drops come from paper transitions (e.g. Bridge in Petal Meadows)|tester=BlazingDiancie}}
{{testing/entry|revision=4.0-9144|OS=Windows 7|CPU=Intel Core 2 Quad @ 2.5GHz|GPU=NVIDIA GeForce GT610|result=Game runs very smoothly as 50 FPS. Have experienced almost no lag. Only frame drops come from paper transitions (e.g. Bridge in Petal Meadows)|tester=BlazingDiancie}}
{{testing/entry|revision=4.0-9129|OS=Windows 10|CPU=Intel Core i3-2120 @ 3.3GHz|GPU=NVIDIA GeForce GTX 750 Ti|result=Game runs at a solid 60 FPS up to 2x native resolution using Direct3D11 and the other recommended configuration settings. Drops to 30-35 FPS occur when paper effects are being rendered, excluding Mario and Partners.|tester=SfaFreak}}
{{testing/entry|revision=4.0-9211|OS=Windows 10|CPU=Intel Core i5-4570|GPU=NVIDIA GeForce GTX 960|result=Using D3D11 with other recommended settings, game ran perfectly with no glitches and a only a few brief fps drops.|tester=Jesse}}
{{testing/entry|revision=4.0-9211|OS=Windows 10|CPU=Intel Core i5-4570|GPU=NVIDIA GeForce GTX 960|result=Using D3D11 with other recommended settings, game ran perfectly with no glitches and a only a few brief fps drops.|tester=Jesse}}
{{testing/entry|revision=4.0-9399|OS=Windows 10|CPU=Intel Core i3-3110M @ 2.4GHz|GPU=Intel HD Graphics 4000|result=Using the default graphics backend OpenGL with other recommended settings, FPS drops from 60 to 30 the exact moment that Goombella and Lord Crump finish their initial "conversation" which caused everything (walking, hammering, jumping, etc) to appear to be in slow motion. Using the graphics backend Direct3D 11 with other recommended settings, no problems thus far, although the laptop is making me sweat.|tester=mythofechelon}}
{{testing/entry|revision=4.0-9399|OS=Windows 10|CPU=Intel Core i3-3110M @ 2.4GHz|GPU=Intel HD Graphics 4000|result=Using the default graphics backend OpenGL with other recommended settings, FPS drops from 60 to 30 the exact moment that Goombella and Lord Crump finish their initial "conversation" which caused everything (walking, hammering, jumping, etc) to appear to be in slow motion. Using the graphics backend Direct3D 11 with other recommended settings, no problems thus far, although the laptop is making me sweat.|tester=mythofechelon}}
{{testing/entry|revision=5.0-266|OS=Windows 10|CPU=Intel Core i7-5820K @ 3.60 GHz|GPU=NVIDIA GeForce GTX 960|result=Ran perfectly at 4K60FPS. Encountered a few crashes randomly in fights and buying items.|tester=Brimaster2000}}
{{testing/entry|revision=5.0-266|OS=Windows 10|CPU=Intel Core i7-5820K @ 3.6GHz|GPU=NVIDIA GeForce GTX 960|result=Ran perfectly at 4K 60FPS. Encountered a few crashes randomly in fights and buying items.|tester=Brimaster2000}}
{{testing/entry|revision=5.0-310|OS=Fedora 24 (Linux 4.6.6-300)|CPU=Intel Core i5-3570K @ 4GHz|GPU=NVIDIA GeForce GTX 780 Ti|result=Ran very well at 1440p 60FPS with 4x MSAA and 16x AF. Camera on the rotating stairs in Hooktail's Castle doesn't transition upwards properly for me. Try pausing and unpausing if that happens.|tester=Favorablestream}}
{{testing/entry|revision=5.0-321|OS=Windows 10|CPU=Intel Core i7-3930K @ 3.8GHz|GPU=NVIDIA GeForce GTX 780|result=Runs perfectly at 1080p with 4x MSAA, using widescreen gecko code and HD texture pack. However, contrary to the information above, I get the bounding box slowdown when using OpenGL and have to use D3D11 to avoid it. Sound effects during battle randomly don't play, regardless of audio emulator engine.|tester=Techjar}}
{{testing/entry|revision=5.0-666|OS=Windows 10|CPU=Intel Core i7-3930K @ 3.8GHz|GPU=NVIDIA GeForce GTX 780|result=Game does not boot with widescreen gecko code enabled, otherwise identical to above result.|tester=Techjar}}
{{testing/entry|revision=5.0-8935|OS=Windows 10|CPU=AMD Ryzen 5 2400G @ 3.6GHz|GPU=AMD Radeon RX Vega 11|result=Configuration: Dual core ON, 720p, 2xMSAA, 2x AF, LLE audio, game rom region JPN. Mostly 60FPS with D3D11 or Vulkan, OGL is slow. LLE audio works well, but some battle SEs like "Great!!" are dropped. All backends suffers a significant slowdown with BBox with my GPU being at a default energy-saving 400MHz clock. This can happen in many transitions, like the bridge appearing animation in Petal Meadows, which achieved an astonishing 8FPS. Turning Mario into Paper Mode or having Vivian hide you make it slower at any time. "Overclocking" GPU to the stock speed solves this and makes the game perfectly playable.|tester=amiboss}}
{{testing/end}}
{{testing/end}}


== Gameplay Videos ==
== Gameplay Videos ==
<!--A full list of options is available at Template:VideoGallery/doc-->
{{VideoGallery
{{VideoGallery
|vid1=A-9Cqk6Lf1Y|cap1=Dolphin Emulator 4.0 - Paper Mario: The Thousand Year Door (1080p HD) - Nintendo GameCube
|vid1=GqQU7lnFfRY|cap1=Paper Mario The Thousand Year Door on PC - Dolphin emulator
|vid2=GqQU7lnFfRY|cap2=Paper Mario The Thousand Year Door on PC - Dolphin emulator
|vid2=A-9Cqk6Lf1Y|cap2=Dolphin Emulator 4.0 - Paper Mario: The Thousand Year Door (1080p HD) - Nintendo GameCube
|vid3=cbMVLcQWnjA|cap3=Paper Mario: The Thousand-Year Door on NVIDIA SHIELD Android TV - Dolphin Emulator (Nintendo GameCube)
|vid3=cbMVLcQWnjA|cap3=Paper Mario: The Thousand-Year Door on NVIDIA SHIELD Android TV - Dolphin Emulator (Nintendo GameCube)
|vid4=aDrsega879A|cap4=(60 FPS) Dolphin 5.0 - Paper Mario: The Thousand year Door (1080p HD) - Nintendo GameCube
|vid5=lzJWiMD1kA4|cap5=(1440p60) Paper Mario: The Thousand-Year Door Gameplay Dolphin 5.0
|vid6=tZt-HkK2lDc|cap6=Dolphin Emulator 5.0-3441 Paper Mario: The Thousand-Year Door (4K/2160p/60fps UHD Texture Pack) GCN
|vid7=nrkB7fXSSGE|cap7=Paper Mario: The Thousand-Year Door - Gameplay Nintendo Gamecube HD 1080p (Dolphin Emulator)
}}
}}
{{Navigation/Paper Mario}}
{{Navigation/Paper Mario}}


[[Category:GameCube games]]
[[Category:GameCube games]]
[[Category:5.0 cleanup]]
Retrieved from "https://wiki.dolphin-emu.org/index.php?title=Special:MobileDiff/126400...168075"

Navigation menu