Recent comments
Recent pages
 |
WiiMote Control Patch, 20080111 public beta This is a public beta of our updated WiiMote control patch. Since there isn't one for Leopard yet, I figure this will at least help you get started before it gets to production. This patch adds support for the nunchuk, and partial support for the Classic Controller. It also adds raw IR output support. All of these options are available under the inspector panel. Some of the classic controller buttons don't work or report bogus values. This is due to the underlying framework in use; I'm looking into this. It's not stable, but I've made considerable efforts to make it stable. Please supply me with crash reports, as well as any other noticed odd behaviour. Normally I'm not a fan of public betas, but we'll see how this one goes :) Beta testers: This is identical to the 20070105 version, so you don't need to upgrade.
|
its working for me, picking
its working for me, picking up a wiimote for almost the first time. even got two tealights going.
the field of view on the IR tracking ain't so great, but thats a wiimote thing i guess!
will post more as i try and integrate into an installation that needs to be together for march.
toby
ir output fixed; ir calibration thoughts
been working with the ir x+y. chris has tweaked the behaviour a little so the values hold when the sensor bar goes out of view, which is working for me.
the ir part doesn't always initialise, which is something that ideally could do with some love... framework at fault by the sounds of it.
i don't see any way of calibrating the ir output, so i'm about to make a calibration patch that i'll put up here that can be integrated if desired.
toby
Not sure if calibration is necessary (though the circle-like output area is a bit lame, IMO. correcting that could be really helpful). If you find a reasonable method for doing this, and think it would be helpful across the board, let me know and I'll try to wrap it up in the patch itself.
Regarding getting IR reliably... hehe :) I'd love to burn more time on it, though that's not too likely in the very near future.
The framework code has fun comments like this:
Unfortunately, as we know, it's still not 100% quite yet.. looking into this.
yep, better ways to spend time
the needs some love comment wasn't a directive =]
i wonder whether its possible to reinitialise just that part and expose that as a 'disconnect' style input. or whether there's any way for the framework / plugin to know the IR didn't initialise, at worst has the IR changed in five seconds after it initialised.
random thoughts, as they come®
I like the re-init idea... I'll have to think about that some more. It's totally possible.
I've considered the 5-second time out thing for some other aspects (a few betas ago, when it was really unstable, I was considering this for some weird disconnect bugs that are mostly resolved now anyway). Can't really think of any downsides, so I may play with that for the next release, if it works out.
Thanks for the ideas :)
bare bones calibrator attached
bare bones.
toggle calibration flag on, waggle your wiimote around, toggle calibration flag off. it will scale the detected reach of the wiimote to the comp size. critically, it should remember the calibration when the comp is saved and loaded back in.
lots you could do down this line, pairing through a structure with a calibration display render patch.
initialisation failed
i'm getting occasional checkerboard viewer when loading the patch containing the wiimote. if its the same issue as spooky was suffering from, could that quick fix be rolled in? installation d-day approaches =]
toby
WiiMoteControl 20080301 beta - hope this helps :)