| IllegalPaladin said: I think the controller lag depended on the TV. One TV seemed to play it without much issue, but another had a pretty horrible lag. However, that TV also had a setting called "Game Mode" which fixed the lag for me. Still, things were improved further when they released that patch. |
Many seem to forget about that, or they just don't know it. When I hooked my Wii to my TV, I calibrated a screen mode specifically for it. I use the Game picture mode for both my PS3 and 360, but since the Wii is plugged to my TV using component cables instead of HDMI and has a resolution of 480p, the Game picture mode wouldn't give justice to the visuals. So I ended up calibrating the Standard picture mode for it.
When I started playing, I noticed there was some very noticeable lag when I would aim in Metroid: Other M. The reticule would appear kind of slow and laggy. My brain would adjust to the lag and it would end up not being much of an issue, but I tried switching to the Game picture mode, which removes the input lag. Indeed, the reticule was now extremely precise and fast, without any lag.
So I found a compromise for using the Game picture mode without messing with the picture settings that are optimal for my 2 HD consoles. I just switch the Dynamic Contrast option ON when I'm using the Wii, switching it back off when I'm on the other consoles.
I often suspect that many of the reports about the motion controllers you see online are ones that don't realize that a lot of the lag they notice is nothing but input lag coming from the TVs themselves and not the actual motion devices.
Note: My TV is the Sharp LC32LE700UN.
