Luomu's Forum Posts

  • I agree about some points and disagree about some... but I hope you reported all those zillion bugs to the tracker or else they will be never fixed

    It would be nice to read more project "post mortems" here.

  • [quote:2c8bs6rx]with V1.02b i can now connect very well and i get all data (IR, roll,etc) but if i use your last pluging V1.03 i get now somes problem:

    i can connect very well but ,only buttons,battery and status work well but no rool and no acceleration data ???

    get the exact opposite result. I hope I can help the Wiiyourself guy to fix it.

    Just use 1.02b now if it works for you. There are no feature differences between 1.02-1.03.

  • I noticed a bug in Wiiyourself RC3 and final versions; when connected only buttons work. To workaround this, connect needs to be called twice or the application built in debug mode. I didn't feel that was a good solution so I downgraded back to RC2. It works better for me.

    Also I maybe managed to salvage wiimote.cap, at least it does not crash any more.

    Wiimote-1.03.zip

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I built the plugin with the last Wiiyourself release and tested it works with Construct 99.85:

    Wiimote-1.02b.zip

    I noticed the test .cap has broken at some point -- it connects and reads values ok but I can't click on the object or construct crashes. I can't easily replace the object with a new one (joys of Construct development) so the test app is unreliable for now.

    I also made this simple connection test app: SimpleTest.zip Connect your remote to the BT adapter, run this and press C to connect. It includes .cap and .exe.

    If that fails, you said the official Wiiyourself demo.exe works. I built the same demo, so if this one does not work it's very puzzling: Non-construct Demo.zip

  • I'll build a new version of the plugin with Wiiyourself 1.15 Final today and check that it works with latest Construct (I'm running 99.84, need to check .85 too).

    If it works with Wiiyourself demo.exe then it should work here too so I don't know what could be wrong... what is your operating system? I have been only testing with Windows 7.

  • <img src="http://paahdin.com/projects/bulletml/images/rtypical.png">

    I'm doing a plugin for BulletML, a scriptable system for those crazy (and sane) bullet patterns you see in arcade shoot-em ups.

    Above sprites by Irem obviously

  • Interesting, I wouldn't have ever figured that out on my own.

  • How would I implement a For each... -style condition in my object? SVN does not have examples on this, such as Array::For each element.

    Is it just a matter of (pseudoish code):

    long ExtObject::cForEachThing(LPVAL params)
{
    if(things.size() == 0)
        return false; //no things, no for each

    currentThing++;

    //reset counter if at end
    if(currentThing == things.end());
        currentThing = things.begin();

    return true;
}
[/code:vo7952n6]
and then an expression to retrieve data from currentThing. Doesn't this just get called once per frame, when I want to go through each object on every frame?

  • So, I went ahead and created a page: https://sourceforge.net/apps/mediawiki/ ... ty_Plugins

    Good? Bad? Change it! Each plugin should have a short description.

  • New version 1.02

    Updated to Wiiyourself API 1.15RC2. New feature in this version is Balance board support. Theoretical support, since I don't have one to test with.

    With BB use the plugin as with a remote. Optionally you can check with the "Is balance board" condition if BB is present. To pair BB with your bluetooth adapter, press the button inside the battery compartment.

    New ACEs, all BB related:

    == Actions ==

    Reset weight calibration (recalibrate BB at rest)

    == Conditions ==

    Is balance board (checks if this remote is actually a BB)

    == Expressions ==

    Total weight (in KG)

    Top left weight

    Top right weight

    Bottom left weight

    Bottom right weight

  • Give some feedback then! Right now I'm not very happy how rough IR pointing is and accelerometer values could be smoother (but smoothing them can also make it feel unresponsive). I'll release an update this weekend.

  • Can I get privileges for Luomu82 please

  • I just updated my old Wiimote plugin so might be time to add it to the list: http://www.scirra.com/forum/viewtopic.php?f=7&t=4847

  • Updated this for 99.82: Wiimote-1.01.zip

    This version adds Nunchuk support. Updated ACE list:

    == Actions ==

    Connect (connect to the first available remote)

    Disconnect

    Set report level (buttons only/+accelerometer/+infrared, higher settings use more power)

    Set rumble (on/off)

    Set LEDs (1/0 for each led)

    Set joystick deadzone (0.0 - 1.0, default 0.03, 1.0 would filter out everything )

    == Conditions ==

    Connected

    Connection lost

    Button pressed

    Button down

    Button released

    Nunchuk connected

    == Expressions ==

    Pitch (In degrees -180 to 180)

    Roll (In degrees, -90 to 90, 0 is level, remote can't detect upside-down)

    Orientation X

    Orientation Y

    Orientation Z

    Acceleration X

    Acceleration Y

    Acceleration Z

    Battery level (percentage)

    IR X (interpolated 0-1.0 from all leds)

    IR Y (same as above)

    IR Z (Estimated led size, very rough)

    Raw IR X (led number 1-4)

    Raw IR Y (led number 1-4)

    IR Report level

    LED status (Sensor bar led groups seen, bar has 2 but remote can track 4)

    Update age (in milliseconds, if age is too much orientation data might be

    unreliable)

    Joystick X

    Joystick Y

    Nunchuk pitch

    Nunchuk roll

    Nunchuk acceleration X

    Nunchuk acceleration Y

    Nunchuk acceleration Z

    Nunchuk Orientation X

    Nunchuk Orientation Y

    Nunchuk Orientation Z

    Nunchuk Update age

    Nunchuk Deadzone X

    Nunchuck Deadzone Y

  • Great plugin, I'm hoping you could submit it to Ashley and co. so it has a better chance of staying compatible with future Construct versions.