WiiLi.org

abstrakraft · Joined: 27 Dec 2006 Posts: 107

I assumed you were being funny as well - no offense taken.
_________________
"I seldom let practicality get in the way of my fascination with shiny things and blinky lights."
- some guy
http://abstrakraft.org/cwiid

Brian · Joined: 17 Jan 2007 Posts: 7

yea your right, it was linking the old libwiimote because i didnt install it, i wanted to test it first because i was expecting it to break my plugin (which it did) not a big deal though, only takes like a minute to make a new one.

Brian · Joined: 17 Jan 2007 Posts: 7

ok.. i cant get my plugin to work anymore... i dont see why not, i just copied the bits of code into acc.c like i did with the old version, then i changed all the f_* references to a_*, i didnt see anything else that would affect it. so it compiles, then i can load it no problem, it says "Ready" but im not getting any input from my wiimote; no mouse movement, buttons or anything, ill look into a bit further and see if i can find a problem, basically this is just from a copy and paste, so i might have missed something that you changed.

EDIT: Looks like it wasnt my problem... i just tried compiling the included acc.c with no changes and the same thing happens, no errors compiling or running, but no input. any changes from 0.3.50 to 0.4.00 that could have caused this? ill have to switch back to the old version if i want to use my plugins. in case your wondering i had two plugins atm: One that converts the angle of the wiimote into absolute mouse movement for the sole purpose of playing neverball, and an IR plugin that only looks for one input LED, rather than trying to find others which elimates jumpy movement and such when im using my custom usb IR adapter with my laptop.

abstrakraft · Joined: 27 Dec 2006 Posts: 107

upgrade to 0.4.01 - there was a race condition in 0.4.00 that resulted in no messages returned to the clients. There were no changes to the api from 0.4.00, so the same code should work.
Changing f_* to a_* is internal to the plugin, so it isn't strictly necessary. I was just being a picky physicist, as those values are accelerations, not forces.
_________________
"I seldom let practicality get in the way of my fascination with shiny things and blinky lights."
- some guy
http://abstrakraft.org/cwiid

Swatch · Joined: 29 Jan 2007 Posts: 6

Hello all, Swatch here.

I'm working with CWiid to implement it into a CFD Engineering Visualization software. I'm having an interesting problem however...

Currently I'm using 0.4.01

After connecting, my wiimote_callback function is not getting called when I press any buttons on the wiimote. I installed the wmgui program and it too is not recognizing the buttons, however it will recognize accel data and extension data (haven't tried IR, but it seems to work well). Also rumble and LED are able to be activated.

At first I thought it was my code, but since wmgui shows the same problem, as well as it worked with previous versions, I think there may be something internal to the wiimote driver going on.

abstrakraft · Joined: 27 Dec 2006 Posts: 107

Interesting.... I agree, it does sound like a problem in libwiimote.
You're getting messages of some type, so the event system isn't deadlocked, and wmgui _always_ enables the button reporting flag. Not sure what else could be wrong.
Can you post your system information? (kernel, distribution, processor,etc.)
_________________
"I seldom let practicality get in the way of my fascination with shiny things and blinky lights."
- some guy
http://abstrakraft.org/cwiid

Swatch · Joined: 29 Jan 2007 Posts: 6

Kernal: 2.6
Distro: kSUSE 10.2
Processor: Core 2 Duo w/ 7 gigs of ram
BT Adapter: Kensington USB Adapter 2.0
BT Stack: bluez

I'm really confused as to why it seems wiimote_callback isn't getting called after a button press. Do you know of anything that could have happened to the wiimote to corrupt the interface?