The Legend of Zelda: Skyward Sword: Difference between revisions

m
Text replacement - "Wiimote" to "Wii Remote"
m (Text replacement - "(\d+) VPS" to "$1VPS")
m (Text replacement - "Wiimote" to "Wii Remote")
Line 20: Line 20:
Skyward Sword '''''requires''''' the Wii MotionPlus add-on. Dolphin is currently not capable of emulating the Wii MotionPlus; the only way for official Dolphin builds to play this game is to use a real, physical Wii remote with Wii MotionPlus. See {{issue|3446}}.
Skyward Sword '''''requires''''' the Wii MotionPlus add-on. Dolphin is currently not capable of emulating the Wii MotionPlus; the only way for official Dolphin builds to play this game is to use a real, physical Wii remote with Wii MotionPlus. See {{issue|3446}}.


*Recent Wii Remote Plus models do not pair with Dolphin when using the MS bluetooth stack, the default bluetooth stack on Windows. To pair these Wiimote Pluses with Dolphin under Windows requires the Toshiba Bluetooth Stack. See the [[Wii Remote Plus (RVL-CNT-01-TR) Connection Guide]] for instructions.
*Recent Wii Remote Plus models do not pair with Dolphin when using the MS bluetooth stack, the default bluetooth stack on Windows. To pair these Wii Remote Pluses with Dolphin under Windows requires the Toshiba Bluetooth Stack. See the [[Wii Remote Plus (RVL-CNT-01-TR) Connection Guide]] for instructions.


=== Wii Remote Calibration ===
=== Wii Remote Calibration ===
The Wiimote will easily lose calibration during swordplay and other rapid movements. There is no true fix for this, but pressing Down on the Wiimote's Dpad will quickly calibrate it (preferably in a menu, but calling Fi will fix it as well). The [[Wii Remote Plus (RVL-CNT-01-TR) Connection Guide|Toshiba Stack]] and the [https://dolphin-emu.org/blog/2014/08/23/dolphinbar-review/ DolphinBar] are capable of correcting for this error faster thanks to superior bluetooth, but they still get out of sync during heavy movement. Loading a save state while using the Wiimote's accelerometer/IR functions (e.g. saving a state while flying with the Beetle and loading it) will also cause this. See {{issue|5751}}.
The Wii Remote will easily lose calibration during swordplay and other rapid movements. There is no true fix for this, but pressing Down on the Wii Remote's Dpad will quickly calibrate it (preferably in a menu, but calling Fi will fix it as well). The [[Wii Remote Plus (RVL-CNT-01-TR) Connection Guide|Toshiba Stack]] and the [https://dolphin-emu.org/blog/2014/08/23/dolphinbar-review/ DolphinBar] are capable of correcting for this error faster thanks to superior bluetooth, but they still get out of sync during heavy movement. Loading a save state while using the Wii Remote's accelerometer/IR functions (e.g. saving a state while flying with the Beetle and loading it) will also cause this. See {{issue|5751}}.


=== Banding ===
=== Banding ===
Line 113: Line 113:
{{testing/entry|revision=3.0-397|OS=Windows 7 x64|CPU=AMD Phenom II X6 1100T @ 3.3GHz|GPU=AMD Radeon HD 6850|result=Game works fine, 30FPS almost every time, close to perfection with just a little of audio glitches, if u are out of range of a time shift orb link disappear or is "cut off" out of the screen in place with a time shift orb or a TS stone but the game is still playable.|tester=Aldaris}}
{{testing/entry|revision=3.0-397|OS=Windows 7 x64|CPU=AMD Phenom II X6 1100T @ 3.3GHz|GPU=AMD Radeon HD 6850|result=Game works fine, 30FPS almost every time, close to perfection with just a little of audio glitches, if u are out of range of a time shift orb link disappear or is "cut off" out of the screen in place with a time shift orb or a TS stone but the game is still playable.|tester=Aldaris}}
{{testing/entry|revision=3.0-397|OS=Windows 7 x64|CPU=AMD Phenom II X4 960T @ 3.8GHz|GPU=AMD Radeon HD 6870|result=Works great, 30FPS most all of the time since overclocking to 3.8GHz, turned off turboboost; also JITIL Experimental Recompiler (improved performance); Other Settings: 3x Native, AA: None, AF 4x, Unchecked Skip EFB Access from CPU, EFB Copies = Texture (I have not finished the game, but w/ AF, looks better than my real disc on real Wii).|tester=DiBBKa}}
{{testing/entry|revision=3.0-397|OS=Windows 7 x64|CPU=AMD Phenom II X4 960T @ 3.8GHz|GPU=AMD Radeon HD 6870|result=Works great, 30FPS most all of the time since overclocking to 3.8GHz, turned off turboboost; also JITIL Experimental Recompiler (improved performance); Other Settings: 3x Native, AA: None, AF 4x, Unchecked Skip EFB Access from CPU, EFB Copies = Texture (I have not finished the game, but w/ AF, looks better than my real disc on real Wii).|tester=DiBBKa}}
{{testing/entry|revision=3.0-458|OS=Windows 7 x64|CPU=Intel Core i7-2637M @ 1.7GHz|GPU=NVIDIA GeForce GT 540M|result=Played through the whole game now on my Alienware M11xR3. Game runs smooth with 25 - 30FPS except in large open areas where it can drop down to 15 - 20FPS. The game is totally playable this way. Settings: Direct3D11, 1366 x 768, V-sync, 1x Internal resolution, No AA, 2x filtering. Used a real Wiimote with Motion+.|tester=DomiStyle}}
{{testing/entry|revision=3.0-458|OS=Windows 7 x64|CPU=Intel Core i7-2637M @ 1.7GHz|GPU=NVIDIA GeForce GT 540M|result=Played through the whole game now on my Alienware M11xR3. Game runs smooth with 25 - 30FPS except in large open areas where it can drop down to 15 - 20FPS. The game is totally playable this way. Settings: Direct3D11, 1366 x 768, V-sync, 1x Internal resolution, No AA, 2x filtering. Used a real Wii Remote with Motion+.|tester=DomiStyle}}
{{testing/entry|revision=3.0-506|OS=Windows 7 x64|CPU=Intel Core i5-2500K @ 4.3GHz|GPU=AMD Radeon HD 5850 x2|result=Game had stuttering and slowdowns during battles using dsound and DX11 plugin. But after switching to xaudio2 (resolves stuttering) and OpenGL(resolves slowdown), game runs flawlessly at 30FPS all the time no matter the in game situation. No graphical or any glitches so far at 29hours into the game. Using real wii remote with following settings: JITIL experimental, 1080p at 3x internal resolution (setting to auto causes shadow glitch), OpenCL and OpenMP, vsync, 16xAF, 0AA.|tester=LaysBBQ}}
{{testing/entry|revision=3.0-506|OS=Windows 7 x64|CPU=Intel Core i5-2500K @ 4.3GHz|GPU=AMD Radeon HD 5850 x2|result=Game had stuttering and slowdowns during battles using dsound and DX11 plugin. But after switching to xaudio2 (resolves stuttering) and OpenGL(resolves slowdown), game runs flawlessly at 30FPS all the time no matter the in game situation. No graphical or any glitches so far at 29hours into the game. Using real wii remote with following settings: JITIL experimental, 1080p at 3x internal resolution (setting to auto causes shadow glitch), OpenCL and OpenMP, vsync, 16xAF, 0AA.|tester=LaysBBQ}}
{{testing/entry|revision=3.0-589|OS=Windows 7 x64|CPU=Intel Core i5-760 @ 3.66GHz|GPU=NVIDIA GeForce GTX 470|result=Runs at full speed in all situations with settings: 2560 x 1440 @ 4x internal resolution, AA none, AF 16x, skip EFB unchecked, OpenMP checked, DSP HLE, XAudio2; using a real wiimote plus and Toshiba stack.  DSP HLE sometimes results in audio glitches during cut scenes.  With DSP LLE (on own thread) enabled, speed regularly drops to 90%, resulting in audio stutter.|tester=tuna}}
{{testing/entry|revision=3.0-589|OS=Windows 7 x64|CPU=Intel Core i5-760 @ 3.66GHz|GPU=NVIDIA GeForce GTX 470|result=Runs at full speed in all situations with settings: 2560 x 1440 @ 4x internal resolution, AA none, AF 16x, skip EFB unchecked, OpenMP checked, DSP HLE, XAudio2; using a real wiimote plus and Toshiba stack.  DSP HLE sometimes results in audio glitches during cut scenes.  With DSP LLE (on own thread) enabled, speed regularly drops to 90%, resulting in audio stutter.|tester=tuna}}