The Legend of Zelda: Four Swords Adventures: Difference between revisions

From Dolphin Emulator Wiki
Jump to navigation Jump to search
m (→‎Testing: General maintenance with AutoWikiBrowser in Bot mode)
 
(118 intermediate revisions by 31 users not shown)
Line 1: Line 1:
{{Infobox VG
{{Infobox VG
|image         = [[File:TheLegendOfZeldaFourSwordsAdventures.jpg|300px]]
|image     = [[File:TheLegendOfZeldaFourSwordsAdventures.jpg|300px]]
|developer     = Nintendo EAD
|developer = Nintendo EAD
|publisher     = Nintendo
|publisher = Nintendo
|released     = {{vgrelease new|JP|March 18, 2004|NA|June 7, 2004|EU|January 7, 2005|AU|April 7, 2005}}
|series    = The Legend of Zelda
|series        = ''The Legend of Zelda''
|released = {{vgrelease|JP=March 18, 2004|NA=June 7, 2004|EU=January 7, 2005|AUS=April 7, 2005}}
|genre         = Action-adventure
|genre     = Action-adventure
|modes         = Single-player, Multiplayer
|modes     = Single-player, Multiplayer (4), Co-op (4)
|input         = GameCube Controller, GameBoy Advance
|input     = GameCube Controller, Game Boy Advance
|size          = 247 MiB
|forumlink = https://forums.dolphin-emu.org/Thread-gc-the-legend-of-zelda-four-swords-adventures--25936
|forumlink     = http://forums.dolphin-emu.org/Thread-gc-the-legend-of-zelda-four-swords-adventures--25936
}}
}}


'''''The Legend of Zelda: Four Swords Adventures''''' is a video game in Nintendo's ''The Legend of Zelda'' series. It was released for the Nintendo GameCube in Japan on March 18, 2004; in North America on June 7, 2004; in Europe on January 7, 2005; and in Australia on April 7, 2005. The Game Boy Advance hand held game console can be used as a controller when using the Nintendo GameCube Game Boy Advance Cable bundled with the game in North America.
'''''The Legend of Zelda: Four Swords Adventures''''', a four-player Zelda connectivity adventure, combines gameplay on both the GameCube and Game Boy Advance for a mix of competitive and cooperative multiplayer fun. By hooking up GBAs to the GameCube, the action will move from the television screen (when players are on the overworld map), to the GBA screen (when entering houses and caves). Players work together to brave 24 challenges in eight levels in Hyrule Adventure (1-4 players, multiplayer only with GBAs) or compete in 10 frantic multiplayer versus battles (2-4 players, GBAs required). Takes place in similar environments as the SNES classic Link to the Past, but features updated character sprites, new special effects, and overall improved graphics. The Japanese version included an additional mode, known as Navi Trackers.


== Gameboy Player ==
== Emulation Information ==
Gameboy connection support can be supported via joybus emulation. Such requires VBA-M (r947 or newer) and a dump of GBA BIOS ([http://www.pocketheaven.com/ph/wiki/GBA_BIOS see here] an excellent dump guide). To connect GBA:
=== Game Boy Advance ↔ GameCube Connectivity ===
#Launch Dolphin (only {{revision|6059}} or newer will work with DSP HLE plug-in, otherwise one must use the DSP LLE plug-in
This title supports GameBoy Advance connection, which can be used via joybus emulation. As of {{revision|5.0-14690}} Dolphin now has mGBA built in for GBA connectivity features. Simply set a GBA (Integrated) to the controllers you wish to connect and ensure you have a GBA BIOS configured in the Options → Configuration → GameCube and everything else with connecting will be handled automatically.
#Start Legend of Zelda: Four Swords Adventures and choose multi-player
#In connection screen, go to Config => GameCube and change the ports to GBA
#Launch VBA-M, go to Options => Emulator and uncheck "Pause When Inactive". Then, go to Options => Link => Joybus options, mark "Enable Joybus Connection" and use default settings (127.0.0.1)
#When enabling joybus, Dolphin will freeze (don't panic, its OK!). Now load the GBA Bios in VBA-M, after the splash screen Dolphin will recognize the joybus link and game will detect it as a standard GBA.


To connect other GBAs, just repeat last instruction. Remember to unblock Dolphin and VBA-M in your firewall (some firewalls may block joybus link), otherwise Dolphin will stuck in connection screen. If you are in doubt, refer to [http://www.youtube.com/watch?v=Mpx_ZQp6Fxc this video] for more details.
If you wish to use standalone GBA emulators for connectivity, you still can through the GBA (TCP) setting. mGBA 0.9.0 or newer and the latest VBA-M SVNs should be supported. Please follow each emulator's instructions for Joybus connectivity in order to connect to Dolphin.
 
=== <s>Navi Tracker Audio Issues</s> ===
VBA-M does not correctly handle the audio from the Navi Trackers mode. This is not a fault of Dolphin, as connecting with mGBA 0.9.0 or newer does not have this problem.
 
This is not a Dolphin bug, and Dolphin now has mGBA built in, which does not have this bug. Fixed by {{revision|5.0-14690}}.


== Problems ==
== Problems ==
=== Z-Order/Transparency Issues ===
{{Problems|{{#vardefineecho:problems|
Some sprites, primarily trees, are not ordered/transparent appropriately and layer on top of the player sprites. Refer {{issue|3426}}.
 
{{image|Four Swords- Layering Issue.png|Layering Issue|br}}
=== <s>Multiple GBAs</s> ===
HLE audio can only support 1 GBA as of the New-Zelda-HLE rewrite. Use DSP-LLE (with a DSP ripped from a Wii/GC) in order to play with multiple players. Fixed by {{revision|5.0-3723}}
 
=== <s>HLE Navi's Trackers Hang (JP version)</s> ===
When using HLE audio emulation the game will hang when trying to use Navi's Trackers mode /w a GBA. Navi Trackers requires DSP-LLE (with a DSP ripped from console) in order to function properly. Fixed by {{revision|5.0-3723}}


=== Odd Glitches ===
}}}}
Odd rendering glitches sometimes occur.
{{image|Four Swords-Oddity.png|Odd rendering glitches|br}}


=== Crashes ===
== Enhancements ==
Game can crash, stop, and/or freeze while going to another area after getting the fire rod on the other side of the river. Other crashes may occur, refer {{issue|5490}}
=== HD Textures ===
[https://forums.dolphin-emu.org/Thread-the-legend-of-zelda-four-swords-adventures-hd?pid=514882#pid514882|The Legend of Zelda: Four Swords Adventures HD]


=== Moon Gate Crash ===
=== 16:9 Widescreen Gecko Code ===
The game crashes when entering a Moon Gate, or operates very slowly under some versions. Can be resolved by enabling, Skip CPU EFB Access.
The Built-in Widescreen Hack does nothing in this game. The following Gecko codes work as a replacement.


=== Can't Hold Button ===
Note that these codes are dependent on unique Dolphin behavior and instantly crash the game on real hardware.
In the game, there are events that require holding a button such as pulling a switch. It may not be possible to hold it for long enough because the button press is disrupted among frames. This problem can be avoided by disabling "idle skipping" in the configuration or by using VBA-M as the controller


=== Sound ===
==== NA ====
Sometimes one soundtrack will loop or hang causing all other sounds to be muted.
<pre>$16:9 Widescreen
C205FCD0 00000002
C22D2400 C0030000
EC110032 00000000
C205FCF4 00000002
C22D2400 C003000C
EC110032 00000000
04543FC0 3F400000
C213B47C 00000004
3C803F80 908D2400
4E800421 3C003F40
60000000 900D2400
60000000 00000000
C22ACA78 00000002
3C603F80 906D2400
806D8F50 00000000
C22ACA80 00000003
3C003F40 60000000
900D2400 801F0018
60000000 00000000
C213D834 00000002
3C603F80 906D2400
806D8F50 00000000
C213D83C 00000003
3C603F40 60630000
906D2400 38610008
60000000 00000000
C213D8D8 00000003
3C603F40 60630000
906D2400 38600000
60000000 00000000
C213D8D0 00000002
3C603F80 906D2400
806D8F50 00000000
0448E0C0 0000FF96
0448E0C4 FF9601BE
0448E0C8 01BE0000
C243A94C 00000003
3C80C2D5 9081FFE8
C001FFE8 C03B00EC
EC21002A 00000000
C245231C 00000002
3D803F80 918D2400
806D8F50 00000000
C2452328 00000002
3C603F40 906D2400
808D8F50 00000000
C213D600 00000002
3C603F80 906D2400
806D8F50 00000000
C213D608 00000002
3C603F40 906D2400
38610008 00000000
</pre>


=== Pixel Shader from Byte Code ===
==== EU ====
With {{revision|3.0-191}} and likely other revisions, restarting the game after play has started will generate the warning "CreatePixelShaderFromByteCode failed at Src\D3DShader.cpp 151".
<pre>$16:9 Widescreen
F6000001 80008180
ED8B5024 ED4B0024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C2627000
ED5302B2 ED8B5024
60000000 00000000
E0000000 80008000
F6000001 80008180
ED494024 ED090024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C1E27000
ED0F0232 ED494024
60000000 00000000
E0000000 80008000
</pre>


===<s>Resizing the Window (DX9)</s>===
==== JP ====
*Switching between full-screen and windowed mode, or even just resizing the window in DirectX9 will make some textures, especially Link, invisible. This does not happen on OpenGL/DX11 plug-in.
<pre>
**This issue seems to have been fixed in {{revision|3.0-243}}.
F6000001 80008180
ED8B5024 ED4B0024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C2627000
ED5302B2 ED8B5024
60000000 00000000
E0000000 80008000
F6000001 80008180
ED494024 ED090024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C1E27000
ED0F0232 ED494024
60000000 00000000
E0000000 80008000
</pre>
 
=== Translation ===
There is an in-progress translation for [https://forums.dolphin-emu.org/Thread-tetrastrackers-navi-tracker-translation-wip Navi Trackers].


== Configuration ==
== Configuration ==
{{Config
{{Config
|idleskipping              = Off
|idleskippingnotes        = Corrects issues with holding buttons
|gfxbackend                = OpenGL or Direct3D 11
|gfxbackendnotes          = The Direct3D9 plug-in has invisible texture problems post window resizing
|skipcpuefbaccess   = On
|skipcpuefbaccessnotes   = Corrects hang/crash/slow performance at Moon Gates
|accuratetexturecache      = Position 4
|accuratetexturecachenotes = Prevents texture errors and all Link sprites being black.
}}
}}


== Version Compatibility ==
== Version Compatibility ==
{{VersionCompatibility}}
{{VersionCompatibility}}
{{VersionCompatibilityVersion|4598|****}}
{{VersionCompatibilityVersion|4598|****|}}
{{VersionCompatibilityVersion|6887|***}}
{{VersionCompatibilityVersion|6887|***|}}
{{VersionCompatibilityVersion|3.0-243|***|DirectX 9 window resizing issues resolved}}
{{VersionCompatibilityVersion|4.0-1192|****|Graphical issues resolved}}
{{VersionCompatibilityVersion|4.0-5899|****|GBA Link issues resolved. Tetra's Trackers now functional. Note:  Tetra's Trackers has issues on the GBA side of emulation.}}
{{VersionCompatibilityVersion|4.0-7286|****|HLE audio issues resolved}}
{{VersionCompatibilityVersion|5.0-3723|*****|HLE GBA Connection Issues Resolved}}
{{VersionCompatibilityClose}}
{{VersionCompatibilityClose}}


Line 73: Line 161:
{{testing/start}}
{{testing/start}}
<!--Use this template for test entries: {{testing/entry|revision=|OS=|CPU=|GPU=|result=|tester=}}-->
<!--Use this template for test entries: {{testing/entry|revision=|OS=|CPU=|GPU=|result=|tester=}}-->
{{testing/entry|revision=4598|OS=Windows Vista x86|CPU=Intel Core 2 Duo E4500 @ 2.2GHz|GPU=Intel GMA 945|result=Fully playable: 50-80 FPS with default settings and DX9 plug-in|tester=}}
{{testing/entry|revision=4598|OS=Windows Vista|CPU=Intel Core 2 Duo E4500 @ 2.2 GHz|GPU=Intel GMA 945|result=Fully playable: 50-80FPS with default settings and DX9 plug-in|tester=}}
{{testing/entry|revision=6315|OS=|CPU=Intel Core i7-720|GPU=ATI Radeon HD 5730|result=Fully playable, even with multiplayer (GBA Link with Dolphin and VBA-M)|tester=}}
{{testing/entry|revision=6315|OS=Windows|CPU=Intel Core i7-720|GPU=ATI Radeon HD 5730|result=Fully playable, even with multiplayer (GBA Link with Dolphin and VBA-M)|tester=}}
{{testing/entry|revision=6887|OS=Windows Vista x86|CPU=Intel Core 2 Duo T8100 @ 2.2GHz|GPU=ATI Mobility Radeon HD 3470|result=Playable: Could play until the Moon Gate crash. 50-60 FPS with DX9 plug-in and OpenCL enabled.|tester=}}
{{testing/entry|revision=6887|OS=Windows Vista|CPU=Intel Core 2 Duo T8100 @ 2.2 GHz|GPU=ATI Mobility Radeon HD 3470|result=Playable: Could play until the Moon Gate crash. 50-60FPS with DX9 plug-in and OpenCL enabled.|tester=}}
{{testing/entry|revision=7303|OS=Windows 7 x64|CPU=AMD Phenom II X3 N850 @ 2.2GHz|GPU=ATI Mobility Radeon HD 4250|result=Slow: 10-30 FPS with DX11|tester=}}
{{testing/entry|revision=7303|OS=Windows 7|CPU=AMD Phenom II X3 N850 @ 2.2 GHz|GPU=ATI Mobility Radeon HD 4250|result=Slow: 10-30FPS with DX11|tester=Autofire}}
{{testing/entry|revision=7440|OS=Windows XP x86|CPU=Intel Core 2 Duo @ 2.93GHz|GPU=nVidia GeForce GTX 260|result=Playable: Some massive slowdowns and the known glitches. First Moon Gate worked fine, second crashed the game.|tester=Proto}}
{{testing/entry|revision=7440|OS=Windows XP|CPU=Intel Core 2 Duo @ 2.93 GHz|GPU=NVIDIA GeForce GTX 260|result=Playable: Some massive slowdowns and the known glitches. First Moon Gate worked fine, second crashed the game.|tester=Proto}}
{{testing/entry|revision=7714|OS=Windows 7 x64|CPU=Intel Core i3-370M @ 2.4GHz|GPU=ATI Radeon HD 6370M|result=Fully playable: No slowdowns, no known glitches.|tester=}}
{{testing/entry|revision=7714|OS=Windows 7|CPU=Intel Core i3-370M @ 2.4 GHz|GPU=ATI Radeon HD 6370M|result=Fully playable: No slowdowns, no known glitches.|tester=}}
{{testing/entry|revision=3.0-436|OS=Windows XP x64|CPU=Intel Core 2 Duo E4500|GPU=ATI Radeon HD 2600 XT|result=Runs okay, 25-35 FPS.|tester=}}
{{testing/entry|revision=3.0-377|OS=Windows 7|CPU=Intel Core i7-2600K|GPU=ATI Radeon HD 6850|result=Work great, but the game can freeze/slowdown on when you enter a moongate. Fixed the problem with "Skip EFB access from CPU". |tester=}}
{{testing/entry|revision=3.0-681|OS=Linux Ubuntu 12.04 x86_64|CPU=AMD Athlon 64 X2 @ 3.2GHz|GPU=nVidia GeForce GTS 450|result=Work great, but the game can freeze ({{issue|5490}}).|tester=RyDroid}}
{{testing/entry|revision=3.0-436|OS=Windows XP|CPU=Intel Core 2 Duo E4500|GPU=ATI Radeon HD 2600 XT|result=Runs okay, 25-35FPS.|tester=}}
{{testing/entry|revision=3.0-377|OS=Windows 7 x64|CPU=Intel Core i7-2600K|GPU=ATI Radeon HD 6850|result=Work great, but the game can freeze/slowdown on when you enter a moongate. Fixed the problem with "Skip EFB access from CPU". |tester=}}
{{testing/entry|revision=3.0-681|OS=Ubuntu 12.04|CPU=AMD Athlon 64 X2 @ 3.2 GHz|GPU=NVIDIA GeForce GTS 450|result=Work great, but the game can freeze ({{issue|5490}}).|tester=RyDroid}}
{{testing/entry|revision=|OS=Android|CPU=Qualcomm Snapdragon 600 @ 1.9 GHz|GPU=Qualcomm Adreno 320|result=[https://www.youtube.com/watch?v=KoQRMSfQcWI Zelda Four Swords with Android Dolphin Emulator on S4 i9500]|tester=bitnbytes01}}
{{testing/entry|revision=3.5-1769|OS=Windows 7|CPU=Intel Core i5-650 @ 3.2 GHz|GPU=ATI Radeon HD 5570|result=Runs great till Level 2-2. Transparency issues and similar minor graphical bugs are still there, but the game runs mostly at full speed. There is only some lag when the screen becomes busy. No audio problems discovered. No crashes, even not at moon gates. When entering those gates, there is an extreme lag, but no crash or freeze. This can be easily fixed by enabling "Skip CPU EFB Access". No error messages on reboot. No control issues. Enabled EFB copy to texture, anything else were standard settings. But when playing Level 2-3, the sound can stuck and the "can't hold button" bug is again there. Didn´t test the game further. Multiplayer untested.|tester=DARK}}
{{testing/entry|revision=4.0.2|OS=Windows 7|CPU=Intel Core i5-3570K @ 3.4 GHz|GPU=AMD Radeon HD 7870|result=I spent a few days configuring until I finally got it to work. DSP LLE always caused a crash during VBA-M connection, so using HLE worked. If I left "Enable GBA Linking" on, one of the VBA-M's would crash after a few minutes, so disabling that made things better. I found turning off "turbo mode" and setting the VBA-M's throttles low (25%) helped achieve steady framerates for dolphin and the VBA's. Lastly, since I was using HLE for audio, I would get occasional sound hangs, so I changed dolphin's audio backend to DSound. Everything runs great, except I still have the z-order issue with the trees.|tester=ziggybozbo}}
{{testing/entry|revision=4.0-4811|OS=Windows 10|CPU=AMD 8350|GPU=NVIDIA GeForce GTX 970|result=I tried a million things, but finally got it to run ONLY on this version of Dolphin with VisualBoyAdvance-M (SVN1206)! Dolphin needs ports 1-4 to be set to GBA for 4 players. Each VBA instance needs to have its input set to the appropriate option for each port. I needed Enable GBA Linking DISABLED or else it would crash, then connect using the Joybus Options menu. You also need to have speed throttled to 100%, or else Dolphin will lag. You need to have Bios Files set in the VBA-M settings, and then launch the bios file. Once launched, it should connect. Be sure to do them in the order of their inputs. For some reason I couldn't get any other combination of these two emulators to work.|tester=Coty}}
{{testing/entry|revision=5.0|OS=Windows 10|CPU=AMD FX 6350@3.9 GHz|GPU=NVIDIA GeForce GTX 660|result=OpenGL, HLE, 3xNative, 8xMSAA, 16xAF Stable until you attempt the massive headache that is multiplayer. Audio completely cuts out when connecting to VBA-M besides audio from the Gameboy. VBA-M crashes on LLE. There is some minor slowdown that can affect gameplay.|tester=GAMMA}}
{{testing/entry|revision=5.0-14690|OS=Windows 10|CPU=Core i7-6700K|GPU=NVIDIA GTX 1070|result=Played on netplay with friends using the new GBA (Integrated). 60 FPS, no issues and was a blast. The future is now, baby.|tester=JMC47}}
{{testing/end}}
{{testing/end}}


== Gameplay Videos ==
== Gameplay Videos ==
{{YouTube|1H_xciSlFww|Zelda Four Swords on Dolphin|br}}
{{VideoGallery
|vid1=NilonV4s_V4|cap1=Dolphin Emulator 4.0.2 - The Legend of Zelda: Four Swords Adventures (1080p HD) - Nintendo GameCube
|vid2=1H_xciSlFww|cap2=Zelda Four Swords on Dolphin
|vid3=Med-OlKcVfw|cap3=Tutorial - Zelda : Four Swords MULTIPLAYER on Dolphin Emulator
|vid4=KoQRMSfQcWI|cap4=Zelda Four Swords with Android Dolphin Emulator on S4 i9500
|vid5=s9R-hqy49qQ|cap5=The Legend of Zelda: Four Swords Adventures on NVIDIA SHIELD Android TV - Dolphin Emulator (Nintendo GameCube)
|vid6=ObwDJnhoAXQ|cap6=The Legend of Zelda: Four Swords Adventures [PAL] [Gamecube] [Español] Dolphin 5.0 [1080p HD]
}}


{{Navigation Zelda}}
{{Navigation/Zelda}}


[[Category:GameCube games]]
[[Category:GameCube games|Legend of Zelda, The: Four Swords Adventures]]
[[Category:Action-adventure games]]
[[Category:Zelda ucode games]]

Latest revision as of 06:53, 7 March 2024

The Legend of Zelda: Four Swords Adventures
TheLegendOfZeldaFourSwordsAdventures.jpg
Developer(s) Nintendo EAD
Publisher(s) Nintendo
Series The Legend of Zelda
Platform(s) GameCube
Release date(s) JP March 18, 2004
NA June 7, 2004
EU January 7, 2005
AUS April 7, 2005
Genre(s) Action-adventure
Mode(s) Single-player, Multiplayer (4), Co-op (4)
Input methods GameCube Controller, Game Boy Advance
Compatibility 5Stars5.pngEdit rating: The Legend of Zelda: Four Swords Adventures
Perfect
GameIDs
See also...

Dolphin Forum thread
Open Issues
Search Google
Search Wikipedia

The Legend of Zelda: Four Swords Adventures, a four-player Zelda connectivity adventure, combines gameplay on both the GameCube and Game Boy Advance for a mix of competitive and cooperative multiplayer fun. By hooking up GBAs to the GameCube, the action will move from the television screen (when players are on the overworld map), to the GBA screen (when entering houses and caves). Players work together to brave 24 challenges in eight levels in Hyrule Adventure (1-4 players, multiplayer only with GBAs) or compete in 10 frantic multiplayer versus battles (2-4 players, GBAs required). Takes place in similar environments as the SNES classic Link to the Past, but features updated character sprites, new special effects, and overall improved graphics. The Japanese version included an additional mode, known as Navi Trackers.

Emulation Information

Game Boy Advance ↔ GameCube Connectivity

This title supports GameBoy Advance connection, which can be used via joybus emulation. As of 5.0-14690 Dolphin now has mGBA built in for GBA connectivity features. Simply set a GBA (Integrated) to the controllers you wish to connect and ensure you have a GBA BIOS configured in the Options → Configuration → GameCube and everything else with connecting will be handled automatically.

If you wish to use standalone GBA emulators for connectivity, you still can through the GBA (TCP) setting. mGBA 0.9.0 or newer and the latest VBA-M SVNs should be supported. Please follow each emulator's instructions for Joybus connectivity in order to connect to Dolphin.

Navi Tracker Audio Issues

VBA-M does not correctly handle the audio from the Navi Trackers mode. This is not a fault of Dolphin, as connecting with mGBA 0.9.0 or newer does not have this problem.

This is not a Dolphin bug, and Dolphin now has mGBA built in, which does not have this bug. Fixed by 5.0-14690.

Problems

Multiple GBAs

HLE audio can only support 1 GBA as of the New-Zelda-HLE rewrite. Use DSP-LLE (with a DSP ripped from a Wii/GC) in order to play with multiple players. Fixed by 5.0-3723

HLE Navi's Trackers Hang (JP version)

When using HLE audio emulation the game will hang when trying to use Navi's Trackers mode /w a GBA. Navi Trackers requires DSP-LLE (with a DSP ripped from console) in order to function properly. Fixed by 5.0-3723

Enhancements

HD Textures

Legend of Zelda: Four Swords Adventures HD

16:9 Widescreen Gecko Code

The Built-in Widescreen Hack does nothing in this game. The following Gecko codes work as a replacement.

Note that these codes are dependent on unique Dolphin behavior and instantly crash the game on real hardware.

NA

$16:9 Widescreen
C205FCD0 00000002
C22D2400 C0030000
EC110032 00000000
C205FCF4 00000002
C22D2400 C003000C
EC110032 00000000
04543FC0 3F400000
C213B47C 00000004
3C803F80 908D2400
4E800421 3C003F40
60000000 900D2400
60000000 00000000
C22ACA78 00000002
3C603F80 906D2400
806D8F50 00000000
C22ACA80 00000003
3C003F40 60000000
900D2400 801F0018
60000000 00000000
C213D834 00000002
3C603F80 906D2400
806D8F50 00000000
C213D83C 00000003
3C603F40 60630000
906D2400 38610008
60000000 00000000
C213D8D8 00000003
3C603F40 60630000
906D2400 38600000
60000000 00000000
C213D8D0 00000002
3C603F80 906D2400
806D8F50 00000000
0448E0C0 0000FF96
0448E0C4 FF9601BE
0448E0C8 01BE0000
C243A94C 00000003
3C80C2D5 9081FFE8
C001FFE8 C03B00EC
EC21002A 00000000
C245231C 00000002
3D803F80 918D2400
806D8F50 00000000
C2452328 00000002
3C603F40 906D2400
808D8F50 00000000
C213D600 00000002
3C603F80 906D2400
806D8F50 00000000
C213D608 00000002
3C603F40 906D2400
38610008 00000000

EU

$16:9 Widescreen
F6000001 80008180
ED8B5024 ED4B0024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C2627000
ED5302B2 ED8B5024
60000000 00000000
E0000000 80008000
F6000001 80008180
ED494024 ED090024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C1E27000
ED0F0232 ED494024
60000000 00000000
E0000000 80008000

JP

F6000001 80008180
ED8B5024 ED4B0024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C2627000
ED5302B2 ED8B5024
60000000 00000000
E0000000 80008000
F6000001 80008180
ED494024 ED090024
D2000000 00000004
3DC03FAA 61CEAAAB
91C27000 C1E27000
ED0F0232 ED494024
60000000 00000000
E0000000 80008000

Translation

There is an in-progress translation for Navi Trackers.

Configuration

This title does not need non-default settings to run properly.

Version Compatibility

The graph below charts the compatibility with The Legend of Zelda: Four Swords Adventures since Dolphin's 2.0 release, listing revisions only where a compatibility change occurred.

Δ
5.0-21264 (current)
Δ
Δ
Δ
Δ
Δ
2.0 (r5384)
Compatibility can be assumed to align with the indicated revisions. However, compatibility may extend to prior revisions or compatibility gaps may exist within ranges indicated as compatible due to limited testing. Please update as appropriate.

Testing

This title has been tested on the environments listed below:

Test Entries
Revision OS CPU GPU Result Tester
r4598 Windows Vista Intel Core 2 Duo E4500 @ 2.2 GHz Intel GMA 945 Fully playable: 50-80FPS with default settings and DX9 plug-in
r6315 Windows Intel Core i7-720 ATI Radeon HD 5730 Fully playable, even with multiplayer (GBA Link with Dolphin and VBA-M)
r6887 Windows Vista Intel Core 2 Duo T8100 @ 2.2 GHz ATI Mobility Radeon HD 3470 Playable: Could play until the Moon Gate crash. 50-60FPS with DX9 plug-in and OpenCL enabled.
r7303 Windows 7 AMD Phenom II X3 N850 @ 2.2 GHz ATI Mobility Radeon HD 4250 Slow: 10-30FPS with DX11 Autofire
r7440 Windows XP Intel Core 2 Duo @ 2.93 GHz NVIDIA GeForce GTX 260 Playable: Some massive slowdowns and the known glitches. First Moon Gate worked fine, second crashed the game. Proto
r7714 Windows 7 Intel Core i3-370M @ 2.4 GHz ATI Radeon HD 6370M Fully playable: No slowdowns, no known glitches.
3.0-377 Windows 7 Intel Core i7-2600K ATI Radeon HD 6850 Work great, but the game can freeze/slowdown on when you enter a moongate. Fixed the problem with "Skip EFB access from CPU".
3.0-436 Windows XP Intel Core 2 Duo E4500 ATI Radeon HD 2600 XT Runs okay, 25-35FPS.
3.0-681 Ubuntu 12.04 AMD Athlon 64 X2 @ 3.2 GHz NVIDIA GeForce GTS 450 Work great, but the game can freeze (issue 5490). RyDroid
Unknown Revision Android Qualcomm Snapdragon 600 @ 1.9 GHz Qualcomm Adreno 320 Zelda Four Swords with Android Dolphin Emulator on S4 i9500 bitnbytes01
3.5-1769 Windows 7 Intel Core i5-650 @ 3.2 GHz ATI Radeon HD 5570 Runs great till Level 2-2. Transparency issues and similar minor graphical bugs are still there, but the game runs mostly at full speed. There is only some lag when the screen becomes busy. No audio problems discovered. No crashes, even not at moon gates. When entering those gates, there is an extreme lag, but no crash or freeze. This can be easily fixed by enabling "Skip CPU EFB Access". No error messages on reboot. No control issues. Enabled EFB copy to texture, anything else were standard settings. But when playing Level 2-3, the sound can stuck and the "can't hold button" bug is again there. Didn´t test the game further. Multiplayer untested. DARK
4.0.2 Windows 7 Intel Core i5-3570K @ 3.4 GHz AMD Radeon HD 7870 I spent a few days configuring until I finally got it to work. DSP LLE always caused a crash during VBA-M connection, so using HLE worked. If I left "Enable GBA Linking" on, one of the VBA-M's would crash after a few minutes, so disabling that made things better. I found turning off "turbo mode" and setting the VBA-M's throttles low (25%) helped achieve steady framerates for dolphin and the VBA's. Lastly, since I was using HLE for audio, I would get occasional sound hangs, so I changed dolphin's audio backend to DSound. Everything runs great, except I still have the z-order issue with the trees. ziggybozbo
4.0-4811 Windows 10 AMD 8350 NVIDIA GeForce GTX 970 I tried a million things, but finally got it to run ONLY on this version of Dolphin with VisualBoyAdvance-M (SVN1206)! Dolphin needs ports 1-4 to be set to GBA for 4 players. Each VBA instance needs to have its input set to the appropriate option for each port. I needed Enable GBA Linking DISABLED or else it would crash, then connect using the Joybus Options menu. You also need to have speed throttled to 100%, or else Dolphin will lag. You need to have Bios Files set in the VBA-M settings, and then launch the bios file. Once launched, it should connect. Be sure to do them in the order of their inputs. For some reason I couldn't get any other combination of these two emulators to work. Coty
5.0 Windows 10 AMD FX 6350@3.9 GHz NVIDIA GeForce GTX 660 OpenGL, HLE, 3xNative, 8xMSAA, 16xAF Stable until you attempt the massive headache that is multiplayer. Audio completely cuts out when connecting to VBA-M besides audio from the Gameboy. VBA-M crashes on LLE. There is some minor slowdown that can affect gameplay. GAMMA
5.0-14690 Windows 10 Core i7-6700K NVIDIA GTX 1070 Played on netplay with friends using the new GBA (Integrated). 60 FPS, no issues and was a blast. The future is now, baby. JMC47

Gameplay Videos