The Legend of Zelda: Skyward Sword: Difference between revisions

Jump to navigation Jump to search
Line 86: Line 86:
{{Test Entry|revision=7719|OS=Mac OS X 10.6.8|CPU=Intel Core 2 Duo @ 3.06 GHz|GPU=ATI Radeon HD 4670|result=25-30 FPS, OpenGL plugin 2x Native Internal Resolution,Anisotropic Filtering 16x, AA off. I kept skip EFB Access from CPU enabled for a performance boost, without it enabled all areas dropped about 5 fps. This of course hinders aiming for the slingshot and bow and arrow, so I disabled it for a select few areas. Overall fully playable with all other suggested settings.|tester=gowsenberry}}
{{Test Entry|revision=7719|OS=Mac OS X 10.6.8|CPU=Intel Core 2 Duo @ 3.06 GHz|GPU=ATI Radeon HD 4670|result=25-30 FPS, OpenGL plugin 2x Native Internal Resolution,Anisotropic Filtering 16x, AA off. I kept skip EFB Access from CPU enabled for a performance boost, without it enabled all areas dropped about 5 fps. This of course hinders aiming for the slingshot and bow and arrow, so I disabled it for a select few areas. Overall fully playable with all other suggested settings.|tester=gowsenberry}}
{{testing/entry|revision=7719|OS=Windows 7 x64|CPU=Intel Core i5 2500k @ 3.3GHz|GPU=nVidia GeForce GTX 570|result=I'm using D3D11, 1920*1080, 4x Internal Resolution, no AA, 16x AF, with "Skip EFB Access to CPU" unchecked. The game works perfectly with a solid 30 fps all the time and no issues. Little detail : to obtain a perfect control of WiiMotion+ with my internal Bluetooth device (included on my motherboard P7P68 Pro REV 3.1) and fix the slowness of the pointer, I had to turn my PC tower to have the device in front of me. Since this change, the accuracy is like on Wii.|tester=iPoulpe}}
{{testing/entry|revision=7719|OS=Windows 7 x64|CPU=Intel Core i5 2500k @ 3.3GHz|GPU=nVidia GeForce GTX 570|result=I'm using D3D11, 1920*1080, 4x Internal Resolution, no AA, 16x AF, with "Skip EFB Access to CPU" unchecked. The game works perfectly with a solid 30 fps all the time and no issues. Little detail : to obtain a perfect control of WiiMotion+ with my internal Bluetooth device (included on my motherboard P7P68 Pro REV 3.1) and fix the slowness of the pointer, I had to turn my PC tower to have the device in front of me. Since this change, the accuracy is like on Wii.|tester=iPoulpe}}
{{testing/entry|revision=r7719|OS=Windows 7 x64|CPU=AMD Phenom II X4 955(Black Edition) 3.4Ghz|GPU=nVidia GeForce 560 GTX|result=30FPS all times. Works great! 1080P, D3D11, Internal Resolution 3x(1920x1584), No AA, 16x Anisotropic Filtering, Force Texture Filtering, unchecked Skip EFB Access from CPU, EFB copies disabled.|tester=SmeagleSmeagle}}
{{testing/entry|revision=r7719|OS=Windows 7 x64|CPU=AMD Phenom II X4 955(Black Edition) @ 3.4GHz|GPU=nVidia GeForce 560 GTX|result=30FPS all times. Works great! 1080P, D3D11, Internal Resolution 3x(1920x1584), No AA, 16x Anisotropic Filtering, Force Texture Filtering, unchecked Skip EFB Access from CPU, EFB copies disabled.|tester=SmeagleSmeagle}}
{{testing/entry|revision=r7719|OS=Windows 7 x64|CPU=Intel Core i7-2700k @4.3 GHz|GPU=nVidia GTX 560 Ti|result=Perfect, played through at 1080p from start to finish with 30 fps. Settings: DX11 renderer, 1920*1080, No AA, 16x Anisotropy, Internal Resolution: Auto (Window Size)|tester=Empyrien}}
{{testing/entry|revision=r7719|OS=Windows 7 x64|CPU=Intel Core i7-2700k @ 4.3 GHz|GPU=nVidia GTX 560 Ti|result=Perfect, played through at 1080p from start to finish with 30 fps. Settings: DX11 renderer, 1920*1080, No AA, 16x Anisotropy, Internal Resolution: Auto (Window Size)|tester=Empyrien}}
{{testing/entry|revision=3.0-208|OS=Windows 7 x64|CPU=Intel Core i7 950 @ 3.07GHz|GPU=nVidia GeForce 460|result=1920*1080, No AA, 16x Anisotropy, 3x native int. res, EFB to Texture.
{{testing/entry|revision=3.0-208|OS=Windows 7 x64|CPU=Intel Core i7 950 @ 3.07GHz|GPU=nVidia GeForce 460|result=1920*1080, No AA, 16x Anisotropy, 3x native int. res, EFB to Texture.
D3D11: Works well except when there are timestones in the loaded area, where Link will render behind objects and the terrain if it is within a certain distance of the camera.
D3D11: Works well except when there are timestones in the loaded area, where Link will render behind objects and the terrain if it is within a certain distance of the camera.