| Length: |
2:41 |
| Video: |
852x480 (16:9), 59.94 fps, DivX 6.8.5 |
| Audio: |
128 kbps MP3 |
| Total Bitrate: |
42.3 MB/min |
| Source: |
720p camcorder |
|
| NOTES: |
This demonstration compares the Wii Cursor's performance on my living room TV (my usual gaming setup) to my desktop PC (via the video capture device that provides much of my videos) using the aiming interface in The Conduit. By measuring the Wii Cursor's apparent delay in both setups (from physical action to actual on-screen movement), I figured out how late game actions were being displayed whenever I try to capture gameplay footage. This gives you an idea of the minor difficulty I put up with while attempting to record gameplay footage; slow games aren't problematic, while action-packed games tend to suffer.
In both setups, my Wii system is feeding 480p/60fps(max) video via analog YPrPb connections. My HDTV is a Samsung LED DLP rear projection set, and my dual-core PC uses a PCI capture card, displaying a fullscreen video overlay on an Asus LCD monitor. My camcorder is recording at 60fps to capture fine movements of the Wii Remote and of Metroid Prime 3.
Bringing the Wii Remote into view helps make the inherent cursor delay obvious. Too obvious, actually. It's not something to be alarmed with, since we all know Metroid Prime 3 feels just fine - the delay is almost negligible on TV sets that don't have screen lag issues. In practice, we're not trying to outrun the cursor in most games/situations (tho some games' cursors are frustratingly slow). It's just, when you make an effort to notice it, you'll easily see it.
The Conduit is well-known for its customization options affecting the first-person camera and the Wii Cursor's sensitivity. You can even recreate Metroid Prime 3's behavior (aside from the framerate). My personal Conduit settings are less sensitive than Metroid for added stability (reduce twitch), but sacrifices some response time (increase delay). The marginal delay is noticeable, but it still moves well and allows my wrist to relax a little more.
The approximate cursor delay for each setup is:
TV: 12 out of 59.94 frames/sec = 0.200 sec
PC: 17 out of 59.94 frames/sec = 0.284 sec
The delay introduced by my video capture device is:
17 - 12 = 5; 5 out of 59.94 frames/sec = 0.083 sec |
|
