The Legend of Zelda: Skyward Sword: Difference between revisions

Jump to navigation Jump to search
m
→‎Testing: use full CPU name
m (→‎Testing: use full CPU name)
(One intermediate revision by one other user not shown)
Line 14: Line 14:


Skyward Sword heavily integrates the use of the Wii MotionPlus; swordplay, for instance, is integrated with the controller to a point where the player has one-to-one motion control over Link's sword and its attack directions. In contrast to earlier installments, battles do not focus solely on timing attacks, but also on their target, such as the direction in which enemies are hit. This also allows for the sword to be integrated into puzzles to a greater extent than in previous titles.
Skyward Sword heavily integrates the use of the Wii MotionPlus; swordplay, for instance, is integrated with the controller to a point where the player has one-to-one motion control over Link's sword and its attack directions. In contrast to earlier installments, battles do not focus solely on timing attacks, but also on their target, such as the direction in which enemies are hit. This also allows for the sword to be integrated into puzzles to a greater extent than in previous titles.
== Emulation Information ==
=== Wii Remote Calibration ===
During sword strikes or other rapid successive movements, the Wii Remote may lose calibration. This can happen even on console, and to help alleviate this the game has a built in automatic calibration whenever it sees the sensor bar, as well as a built in manual calibration feature: press Down on the Wii Remote's Dpad while pointing at the sensor bar will calibrate it anywhere instantly (preferably in a menu, but calling Fi will fix it as well). Use these features any time the motion controls become desynced.
Unfortunately Emulated Bluetooth exhibits this behavior worse than console, making it desync more regularly. [[Bluetooth Passthrough]] however behaves the same as console, and is recommended if you are having trouble with this issue.


== Problems ==
== Problems ==
Line 21: Line 28:
{{Image|Legend of Zelda-Skyward Sword Map broken.jpg|Dolphin map}}
{{Image|Legend of Zelda-Skyward Sword Map broken.jpg|Dolphin map}}
{{Image|Legend of Zelda-Skyward Sword Map on console.jpg|Proper map|br}}
{{Image|Legend of Zelda-Skyward Sword Map on console.jpg|Proper map|br}}
=== Wii Remote Calibration ===
During sword strikes or other rapid successive movements, the Wii Remote may lose calibration. This can happen even on console, and to help alleviate this the game has a built in automatic calibration whenever it sees the sensor bar, as well as a built in manual calibration feature: press Down on the Wii Remote's Dpad while pointing at the sensor bar will calibrate it anywhere instantly (preferably in a menu, but calling Fi will fix it as well). Use these features any time the motion controls become desynced.
Unfortunately Emulated Bluetooth exhibits this behavior worse than console, making it desync more regularly. [[Bluetooth Passthrough]] however behaves the same as console, and is recommended if you are having trouble with this issue.


{{Problems/Wii MotionPlus Required}}
{{Problems/Wii MotionPlus Required}}
Line 126: Line 128:
{{testing/entry|revision=5.0-1066|OS=Windows 7|CPU=Intel Pentium G620 @ 2.6GHz|GPU=Intel HD Graphics|result=Perfecto, 30 FPS estables con una resolucion de 800x600, Sinc-V. Baja un poco los FPS en areas abiertas, pero por lo general va a 30 fijo.|tester=Sky & Wave}}
{{testing/entry|revision=5.0-1066|OS=Windows 7|CPU=Intel Pentium G620 @ 2.6GHz|GPU=Intel HD Graphics|result=Perfecto, 30 FPS estables con una resolucion de 800x600, Sinc-V. Baja un poco los FPS en areas abiertas, pero por lo general va a 30 fijo.|tester=Sky & Wave}}
{{testing/entry|revision=5.0-1328|OS=Windows 10|CPU=AMD Phenom II x6 1090t @ 3.2GHz|GPU=AMD R9 280|result=Running at 3x internal resolution, 2xSMAA and 16xAF. Runs great; a few minor stutters. |tester=Sam3}}
{{testing/entry|revision=5.0-1328|OS=Windows 10|CPU=AMD Phenom II x6 1090t @ 3.2GHz|GPU=AMD R9 280|result=Running at 3x internal resolution, 2xSMAA and 16xAF. Runs great; a few minor stutters. |tester=Sam3}}
{{testing/entry|revision=5.0-2245|OS=Windows 10|CPU=Intel i5-6600K @ 4.2GHz|GPU=NVIDIA GeForce GTX 1070|result=30FPS at 3x internal resolution, 8xSSAA and 16xAF. Minor stutters when new stuff and sounds getting loaded, even on SSDs.|tester=WallK}}
{{testing/entry|revision=5.0-2245|OS=Windows 10|CPU=Intel Core i5-6600K @ 4.2GHz|GPU=NVIDIA GeForce GTX 1070|result=30FPS at 3x internal resolution, 8xSSAA and 16xAF. Minor stutters when new stuff and sounds getting loaded, even on SSDs.|tester=WallK}}
{{testing/entry|revision=5.0-2245|OS=Windows 10|CPU=AMD FX-8320e @ 4GHz|GPU=AMD Radeon HD 7870|result=30FPS at 3x internal resolution, 8xSSAA and 16xAF. Hitches as new stuff is cached, to be expected.|tester=Tosslehoff}}
{{testing/entry|revision=5.0-2245|OS=Windows 10|CPU=AMD FX-8320e @ 4GHz|GPU=AMD Radeon HD 7870|result=30FPS at 3x internal resolution, 8xSSAA and 16xAF. Hitches as new stuff is cached, to be expected.|tester=Tosslehoff}}
{{testing/end}}
{{testing/end}}
2,226

edits

Navigation menu