Problems (#1) - ir_ptr not working (#46) - Message List
Hey folks. I got cwiid compiled (tried from svn and 6.0 rc3).
Everything seems to be working ok except the ir_ptr config setting. When I use -c ir_ptr the pointer doesn't move at all. Buttons work fine though... Can't seem to figure it out.
When I run wmgui it detects the ir light sources, so I know that isn't the problem. Any suggestions?
How well does the acc (default) plugin work?dsmith08/30/07 04:41:32 (6 years ago)
acc works fine to move the mouse around, but it's not usable as a mouse really... it's just not accurate enough.anonymous08/30/07 11:24:52 (6 years ago)
Yeah, it's not quite up to sliced bread yet, but it works in the absence of a decent IR source. What I was getting at is that it does work, though. What new files are created in /dev/input when you run with the ir_ptr config?dsmith08/31/07 02:56:51 (6 years ago)
Thanks for your help. I am running Ubuntu 7.04 right now with the latest svn.
I actually have the Wii sensor bar in front of my tv, so there is a good IR source. When I use -c ir_ptr I noticed that the LEDs on the bottom of the wiimote light up (sometimes the first one and sometimes the second one depending on what buttons I hit)... I am assuming this is because it has found the IR light source because when I point the wiimote elsewhere they go off -- which is why I am so confused that it's not moving. Ok, sooo before running /dev/input has:
by-path event1 event3 event5 event7 mouse0 mouse2 ts1 uinput event0 event2 event4 event6 mice mouse1 ts0 ts2
and while running with -c ir_ptr:
by-path event1 event3 event5 event7 js0 mouse0 mouse2 ts0 ts2 uinput event0 event2 event4 event6 event8 mice mouse1 mouse3 ts1 ts3
...so it looks like js0, event8, mouse3, and ts3 are added.
But for some reason the mouse isn't moving AT ALL. I don't think I'm doing anything wrong because I haven't gotten any error messages... and everything seems to be working fine...
PS. I just rebooted and wminput had a problem finding libcwiid.so.1, so I had to "ln -s /usr/local/lib/libcwiid.so.1 /usr/lib/libcwiid.so.1" which made it work. Is this a bug or did I mess something up?
Thanks again.anonymous08/31/07 03:20:18 (6 years ago)
Ok, I'm an idiot, but in my defense the documentation for Cwiid isn't all in one place. The README doesn't say that you have to add sections to the xorg.conf file to make this work! And it worked fine in default mode without those sections... sigh. Sorry for being a pain in the ass!
Identifier "Wiimote" Driver "evdev" Option "Name" "Nintendo Wiimote"
and also this to the ServerLayout? section:
Now... I just have to figure out how to get it working with BOTH of my displays... it seems to want to only work on head one (nvidia twinview)... I'm sure if I google a bit I can find it.
Oh, and I sorted out that library problem too by adding /usr/local/lib to my /etc/ld.so.conf and then running ldconfig like the README says... ugh. *kicks self*anonymous08/31/07 03:38:52 (6 years ago)
If you want the library to be installed in the right path, do a "./configure --libdir=/usr/lib/" instead of just a plain old ./configure. That will install the libraries where ubuntu expects them to be.nickishappy08/31/07 05:33:37 (6 years ago)
Don't kick yourself too hard - documentation bugs are bugs, too, and sometimes the most insidious. I'll incorporate the results of your experience in wminput/README.
It's been awhile since I've mucked around in the (mostly undocumented) uinput system, but this kinda makes sense if you know that ir_ptr uses absolute coordinates, mice usually use relative coordinates (as acc does), and the input system tries to be smart and only deliver events to the objects that it thinks would implement them. By adding the evdev driver, you're effectively routing around the I-don't-think-this-is-a-mouse-event filter.dsmith08/31/07 11:51:54 (6 years ago)
Thanks! Any advice on getting it running on my secondary display?
I'm using an nVidia card and twinview (I have screen 0 and screen 1 set up). When I get it to the right edge of my display, where it should just pop over to the next it will go as far as the edge of my second display but refuses to go any further.
This is a bit of an issue since the only one I really want to use it on is Screen 1 :) My regular mouse goes over there fine, even when I move the mouse over and then try to move the cursor with Cwiid, it snaps back onto screen 0.
Thanks again!anonymous08/31/07 13:34:45 (6 years ago)