Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pjcast]

It supports 7 (8?) devices though, not just 4.
And mine does not use (or even support I think) that stack, mine is, one sec... a "Broadcom Corporation Version 16389.67/14" and it works perfect with the Wiimote.  WiinRemote is definitally fun (I have the buttons setup well for controlling the sound system, from anywhere in the house ).  This thing makes just a dang nice remote for the PC.

I agree that it as a remote for the PC is sweet

So, did you compile OIS with Wiimote support and did it work?

[OvermindDL1]

Not yet, been rather busy with non-personal programming projects, but should get some time soon.

[pjcast]

Just want to mention, I've implemented NunChuck support for the wiimote.

You now get 1 more orientation vector3 control with the NunChuck attached, as well as 2 joystick axes (x and y), and two more buttons... Have fun

[KungFooMasta]

Sweet!  I will be trying this out tomorrow, can't wait!

KungFooMasta

[KungFooMasta]

Ok, so I couldn't wait until tomorrow.  :twisted:

Wiimote+Nunchuck works great, as seen in the console demo app!

Can't wait to incorporate this into my game!  

KungFooMasta

[pjcast]

Nice

[mohij]

Hi everybody,
it seems that there is support for the wii controllers in OIS, but just for information I found a very nice page with up to date information on drivers for the wii controllers on all platforms:
http://www.wiili.org/index.php/Wiimote/Drivers

Perhaps one or the other library can still be used.

Greetings,
mohij

[KungFooMasta]

I am using the Wiimote in my app to move my player.  The analogue communication seems slightly delayed, which is very noticeable when the nunchuck analogue is used to control the mouse cursor, but when the analogue is used to control the character on the map, the delay is not really noticed.

I'm not sure how quick the Wiimot+nunchuck response is, so I don't know if the delay is caused from the device or the drivers.  Maybe I need to poll the device more often?

KungFooMasta

[pjcast]

You really shouldn't try to use the wiimote to move a mouse - especially if you don't have IR with it. It is going to feel lag-ish. One thing you can try to do to get more responsiveness is to turn down the sensitivity value to something very small (look at JoyStick class methods). Though, you will get lots of small movements even when the controller is laying still on a table if you turn it down too low.

[KungFooMasta]

The analogue stick?  I would think it remains not moving unless your thumb is over it pushing it in some direction.

Well it's not so bad, I don't plan on having too many screens with a mouse, it is a game after all.  :wink:

When I get a small demo out (not anytime soon) I will send it your way, and you can see the wiimote behavior yourself!  

KungFooMasta

[pjcast]

Ah, I thought you were using the orientation stuff  :oops:

I've used regular analog joysticks for my system mouse before, and it was quite awkward, but didn't notice a whole lot of lag. Maybe you need to be calling capture quicker, or maybe the wiimote thread sleepage needs to be reduced a bit to allow for quicker updates.

[KungFooMasta]

Ok, I will look into making the polling happen more often.  If possible I'd like to see what 1.5 or even 2 times faster would be like.

In comparison to the RumblePad2, the RumblePad2 acts immediately, and I couldn't notice any kind of delay.  Of course, my RumblePad2 is not wireless, and I"m no expert on wireless communications, so that could cause some delay.

If you have any pointers on where to adjust the capture calling that would quicken the search.  :mrgreen:

KungFooMasta

[OvermindDL1]

It's not really the fact that it is wireless, but the fact it is being polled.  Polling always has some delay and misses some data, but with something like the accellerometer that makes sense, but it does not make sense for anything else on the thing, but that is what can be worked with.