Guitar Hero World Tour Drums Wii Glovepie

[MonkeyJamboree]

my apologies. i realize that the tilt and rumble is all in the remote. i was merely stating the point that the specific code posted earlier did not work at all for me, including wii remote button presses (likely due to not having any kind of mapping for those, or something similar).
as for the rock band instruments, indeed they are USB devices. never meant to suggest otherwise
again, if there's anything i can help with, just let me know. i'll try to stay out of the way until i have something more useful to say or if i'm needed

EDIT: agh, forgot, i AM using GlovePIE 0.29, since the download was disabled for 0.30 on the site. should i do a google for the new version, or just wait?

[death_au]

death_au, that script doesn't help me at all. Can you please fix it so it does the initialisation code ONCE rather than trying to do it 60 times a second. And you can't have wait commands in the main body. They really have to be inside IF statements. Your code will run at 2 FPS, even when using a GH3 controller, which is not enough for a rhythm game. Does that initialisation code work when only done once at the start of the script? I need to know what code to use in the next version of GlovePIE to initialise things.

I thought I did...?
Oh, I see what I did there. I did it in my quick and dirty script for the drums but forgot to do it in guitar. Silly me. Here's the updated script:

Code: Select all

/*
// FoFiX GH Wiitar script 2.0
// Version 2.1 by Death_au
// Now supports the GH:WT guitar
// Now initializes the WT guitar only once
*/

//GH4 guitar wakeup code:

if(!var.init)
WiimotePoke(1, 0x4A400F0, 0x55) // Decrypt
wait 100ms
WiimotePoke(1, 0x4A400FB, 0) // Unknown
//wait 100ms
//WiimoteDumpBytes(1, 0x4A400F0, 16) // view type
//wait 100ms
//WiimotePoke(1, 0x4A400F0, 0xAA) // Encrypt again
//wait 100ms
//WiimoteDumpBytes(1, 0x4A40020, 32) // view calibration
wait 100ms
WiimotePoke(1, 0x4A40040, 0)
wait 100ms
WiimoteSend(1, 0x17, 0x04, 0xA4, 0x00, 0xF0, 0, 16) // get type
var.init = true
end if

var.found = "";
if WiiGuitar.Exists then var.found += "Guitar@Wiimote";

if var.found == "" then {
   var.found = "No Guitar found - ";
}

var.found += (" - Battery: " + WiiMote.Battery) + "% - ";

// Debug
var.dummy = Wiimote.RawForceX
if WiiGuitar.Green then var.G = "Green" else var.G = ""
if WiiGuitar.Red then var.R = "Red" else var.R = ""
if WiiGuitar.Yellow then var.Y = "Yellow" else var.Y = ""
if WiiGuitar.Blue then var.B = "Blue" else var.B = ""
if WiiGuitar.Orange then var.O = "Orange" else var.O= ""
if WiiGuitar.Minus then var.Minus = "-" else var.Minus = ""
if WiiGuitar.Plus then var.Plus = "+" else var.Plus = ""
if WiiGuitar.StrumUp then var.Strum = "StrumUp" elseif WiiGuitar.StrumDown then var.Strum = "StrumDown" else var.Strum = ""
debug = var.found+"Frets: "+var.G+var.R+var.Y+var.B+var.O+var.Minus+var.Plus+"; Strum: "+var.Strum+"; Whammy:"+Wiimote.Classic.R+var.RF+"; Tilt=" + Wiimote.RawForceZ+"; Joystick: X = "+Wiimote.Classic.Joy1X+", Y = "+Wiimote.Classic.Joy1Y;
//debug = var.wakeup+";" +wiimote.ExpString

/*---BUTTON MAPPING to Keyboard and PPJoy--*/
//Configuration:
//
//Green - F1
//Red - F2
//Yellow - F3
//Blue - F4
//Orange - F5
//Strum Up - enter
//Strum Down - Right Shift
//Minus - Page Down
//Plus - Escape
//Tilt - Page Down
//Whammy - Page Up OR PPJoy Analog 0 change in script below
//NOTE: Joystick doesn't work yet on the GH:WT guitar
//Joystick Up - Up
//Joystick Down - Down
//Joystick Right - Right
//Joystick Left - Left



// Guitar Joystick
Key.Left = (-1.2 < WiiGuitar.JoyX < -0.5) // Joystick moving Left = minus X axis
Key.Right = (0.5 < WiiGuitar.JoyX < 1.2)  // Joystick moving Right = positive X axis
Key.Up = (-1.2 < WiiGuitar.JoyY < -0.5)   // Joystick moving Up = negative Y axis
Key.Down = (0.5 < WiiGuitar.JoyY < 1.2)   // Joystick moving Down = positive Y axis


// Fret Buttons
Key.F1 = WiiGuitar.Green       //Green
Key.F2 = WiiGuitar.Red         //Red
Key.F3 = WiiGuitar.Yellow      //Yellow
Key.F4 = WiiGuitar.Blue        //Blue
Key.F5 = WiiGuitar.Orange      //Orange


// Plus and Minus Buttons
Key.Escape = WiiGuitar.Plus    //Menu / Pause


// Strum Bar
Key.Enter = WiiGuitar.StrumUp
Key.RightShift = WiiGuitar.StrumDown

//Whammy/Killswitch
Key.PageUp = WiiGuitar.Minus
Key.PageUp = (0.75 < WiiGuitar.WhammyBar < 0.9)
//ppjoy.Analog0 = WiiGuitar.WhammyBar
//debug = ppjoy.Analog0

// Star Power
//debug = Wiimote.RawForceZ
if(18 < Wiimote.RawForceZ < 100)
      Key.PageDown = true;
      Wiimote.Rumble = true;
else
      Key.PageDown = false;
      Wiimote.Rumble = false;
endif

//END OF FILE

Apologies, but I haven't had a chance to test it, since I'm at work. But the initialization code above did work in the drums script I posted earlier. Also, you can initialize the instrument once (as long as you don't re-encrypt) and then stop the script and run another script without re initializing until you disconnect the instrument from the wiimote / power down the wiimote.
Does that make things a bit clearer?

[wuxingwarrior3]

It seems that when using the GHWT wii drum set in FOF, I can hit notes that are fairly close together but I fail out of any sort of drum roll (>sixteenth notes). I don't know if it's a problem with the code, FOF, or my skills (i'm guessing it's one of the former). Any ideas?

[curtiswwe]

EDIT: agh, forgot, i AM using GlovePIE 0.29, since the download was disabled for 0.30 on the site. should i do a google for the new version, or just wait?

I found this link, but I don't know whether CarlKenner will approve, but this is is: http://carl.kenner.googlepages.com/GlovePIE030.zip

[MaXimum_Impact]

I am now uploading a video of me playing Give It All on my World Tour Drum Kit. Thanks for all the help guys. I'll tell you when the video is up.

[MonkeyJamboree]

awesome, the new code works pretty well with the GHWT guitar on GlovePIE 0.30, with the exception of strumming up not moving up in the menus and instead being "enter" i think, and the analog/joystick doesn't work at all (as has been stated). - X and Y always stay at 0.00. Also, the indicator light initially keeps blinking until you hit stop and start again, then it turns off entirely, so you don't know if the wiimote is on anymore.
random: is there any way to use strum up as both up and strum up in game, and strum down as, well, down and strum down, and only use Green for entering menus and accepting, similar to GH and RB?

EDIT: forgot to mention, I'm using all of this on 64-bit vista, and I haven't really noticed much lag at all, except an occasional note skip. great work guys!

[Starsghost]

First, I just want to say thanks to all those who keep putting in effort to keep open source software up and running.
Second.....I may be a huge noob, but, trying to get the GHWT guitar working, and using the latest script, I keep getting no guitar found showing up in the box in the top right, and I have tried both .29 and .30.......the wiimote is hooked up to the guitar when I get the bluetooth connection paired, and the lights keep flashing until I run the script, then stop it. Then the lights die and I get nothing until I hit the sync button. But yeah, I still get no guitar found....

Any ideas what I should be checking?

[wuxingwarrior3]

First, I just want to say thanks to all those who keep putting in effort to keep open source software up and running.
Second.....I may be a huge noob, but, trying to get the GHWT guitar working, and using the latest script, I keep getting no guitar found showing up in the box in the top right, and I have tried both .29 and .30.......the wiimote is hooked up to the guitar when I get the bluetooth connection paired, and the lights keep flashing until I run the script, then stop it. Then the lights die and I get nothing until I hit the sync button. But yeah, I still get no guitar found....

Any ideas what I should be checking?

Have you tried checking any other script to see if the wiimote is paired correctly (i.e. wiimote battery test)?

[CarlKenner]

Try adding this to a script:

Code: Select all

PIE.FrameRate = 100Hz

The Wii Remote reports data at 100Hz. But I think GlovePIE scripts default to 60 or 40Hz (depending on the version). And don't use any Poke or Send commands in the main body (use an IF statement to make them execute once), since they include a built in delay.

I think the GHWT Guitar has extra buttons that the GH3 Guitar doesn't have, is that right?

If so, what are they, how do I read them, and what should I call them?

Oh, and does anyone have a 3rd party guitar? Or know anything about the 3rd party guitars?

[MonkeyJamboree]

well, i don't know if it helps much, but here's what i'm using:
GlovePIE version 0.30 as posted earlier by curtiswwe
the last script posted by death_au, i believe it's called FoFiX GH Wiitar Script 2.0, Version 2.1, also earlier this thread
FoFiX-3.030-Full-Windows as listed somewhere on the forums or the wikia (likely in one of the getting started sections, sorry i don't have a better link
Windows Vista 64bit with SP1
a Rocketfish Micro Bluetooth USB adaptor with the default drivers that windows installs
GHWT Guitar

one thing of note, i DO have to use the "Bluetooth Fix" in GlovePIE to get it working, and i also have to remove and re-add the wii remote to windows' bluetooth devices manager thing every time i go to use it, pressing 1+2 does not autosync it.

As for the 3rd party controllers, from what i hear they're really not worth getting, for the same reason as other 3rd party merch... iffy and workable at best, but not quality. however, they SHOULD all be GH3 controllers at heart and should all work fine (only my assumption, however). And yes, the GHWT guitar has an odd little touch-sensitive fretbar that the Les Paul did not have. from what i've noticed it has ranges that it uses as "buttons" but i'm not sure exactly what ranges these are.

[death_au]

I think the GHWT Guitar has extra buttons that the GH3 Guitar doesn't have, is that right?

If so, what are they, how do I read them, and what should I call them?

This is what I posted earlier about the touch bar. Apart from that, the only difference in button layout of the guitar is that it has two plus buttons (that both seem to register the same) and one big minus button (it's big and labeled "Star power").

EDIT: I know, so many edits... I was looking at the joystick on the wii guitars through the wiimote.ExpString... The first 64 bits are the ones that change for both, but the ranges are different.
On the GH4 guitar the first two chunks vary from approximately 00 - 3F, whereas on the GH3 guitars it was C0 - FF
Also, while I'm looking at it... The touch bar seems to be governed by the 3rd chunk. On my guitar, I get these values:

Code: Select all

Not touching it  -  0F
1st (top) fret   -  04
1st AND 2nd      -  07
2nd              -  0A
2nd AND 3rd      -  0C/0D (keeps changing)
3rd              -  12/13
3rd AND 4th      -  14/15
4th              -  17/18
4th and 5th      -  1A
5th (bottom)     -  1F


You can hold two frets at once, as long as those two frets are adjacent, otherwise it will take the value of the lowest fret held (Eg, if you hold the highest and lowest fret, it reads 1F)
Note that high/low means physically on the guitar neck (in musical terms I think it's the other way around, so I thought I'd better specify)

I would really prefer if someone could confirm these values for me.

EDIT: As for the name of the variables... WiiGuitar.TouchGreen, TouchRed etc...?
I'm not sure if you should record separate variables for if two adjacent ones are held. Probably best to just see the event and set both frets to true
(e.g. for input of 07, set both TouchGreen and TouchRed to true)


@Those who want strum up to work as up in the menu rather than accept: Go into the settings of FoF and change the strum up key to something other than enter (for example Left Shift) and then change the appropriate part of the GlovePIE script:

Code: Select all

// Strum Bar
//Key.Enter = WiiGuitar.StrumUp  // <-- This one gets changed
Key.LeftShift = WiiGuitar.StrumUp  // <-- This one is the new key you assign
Key.RightShift = WiiGuitar.StrumDown

[MonkeyJamboree]

here are my values for the analog stick that i got by enabling the line "debug = var.wakeup+";" +wiimote.ExpString" in death_au's script:
note, only the first four values changed, the others seem to be for keys already defined.

Code: Select all

not touching:                                     0.00;20 20 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved left completely:                            0.00;05 20 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved right completely:                           0.00;3D 20 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved up completely:                              0.00;20 3C 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved down completely:                            0.00;20 04 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved left and up diagonal completely:            0.00;0D 35 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved left and down diagonal completely:          0.00;0C 0D 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved right and down diagonal completely:         0.00;35 0C 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
moved right and up diagonal completely:           0.00;35 35 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
with all 5 frets pressed and no analog:           0.00;20 20 0F 11 FF 07 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE

as for the fret bar, here are my numbers:

Code: Select all

not touching:           0.00;20 20 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
touch green:            0.00;20 20 04 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
touch green/red:        0.00;20 20 07 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
touch red:              0.00;20 20 0A 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
touch red/yellow:       0.00;20 20 0C 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE  //0C-0D fluctuate
touch yellow:           0.00;20 20 12 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE  //12-13 fluctuate
touch yellow/blue:      0.00;20 20 14 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE  //14-15 fluctuate
touch blue:             0.00;20 20 17 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE  //17-18 fluctuate
touch blue/orange:      0.00;20 20 1A 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
touch orange:           0.00;20 20 1F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
touching all:           0.00;20 20 1A 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE  //interestingly this is the same result as blue/orange.

whammy bar varies between 0.00;20 20 0F 11 FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
                      and 0.00;20 20 0F 1A FF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
StrumUp is                0.00;20 20 0F 11 FF FE 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE (and subtracts 01 in hex from any note button when pressed, in the FE area)
StrumDown is              0.00;20 20 0F 11 BF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE (and subtracts 40 in hex from the minus or plus button, in the BF area)
Start/"Star Power" is     0.00;20 20 0F 11 EF FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE
and Plus buttons are      0.00;20 20 0F 11 FB FF 00 00 00 00 00 00 00 00 00 00 FE FE FE FE FE

while my numbers are only a couple of bits off from death_au's for the analog stick (likely due to mfg processes and plastic parts), the numbers for the strum bar match exactly. sorry if most of these numbers are useless, i figured i would post everything i got for completeness' sake. if you need anything else, feel free to ask!

[death_au]

while my numbers are only a couple of bits off from death_au's for the analog stick (likely due to mfg processes and plastic parts), the numbers for the strum bar match exactly. sorry if most of these numbers are useless, i figured i would post everything i got for completeness' sake. if you need anything else, feel free to ask!

That is good for completeness sake.
And as for the values being off mine slightly, they're actually not. I assumed the same plastic parts type problems and so rounded off. The rounding makes sense to me, but if everyone gets the same values, perhaps there's no point...
I'm glad for confirmation of the touch bar values, too. Thanks.

[Starsghost]

First, I just want to say thanks to all those who keep putting in effort to keep open source software up and running.
Second.....I may be a huge noob, but, trying to get the GHWT guitar working, and using the latest script, I keep getting no guitar found showing up in the box in the top right, and I have tried both .29 and .30.......the wiimote is hooked up to the guitar when I get the bluetooth connection paired, and the lights keep flashing until I run the script, then stop it. Then the lights die and I get nothing until I hit the sync button. But yeah, I still get no guitar found....

Any ideas what I should be checking?

Have you tried checking any other script to see if the wiimote is paired correctly (i.e. wiimote battery test)?

Yeah, it is paired, as I tried one from page 4, and the buttons somewhat worked, but it read them as always depressed, so it was like holding down enter.

[l0stsign]

to help development on drums, here's what I've found (mostly speculation). It needs to be confirmed and completed... and made sense of by someone who isn't a completely noob like myself.

Code: Select all

first byte (X axis on analog stick) is, when left alone, defaulted to 20, and ranges from 00 (all the way left) to 3F (all the way right)
similarly, the 2nd byte (Y axis) defaults to 1F and ranges from 00 (all the way down) to 3F (all the way up)

the 3rd through 5th bytes _periodically_ change from being standard "FF"s to giving more detailed information. That is, if you drum roll for an extended period of time, only certain hits will register these bytes as something other than "FF", but most of the time that's all they are. I do not know what triggers it. It's not always the first time you hit that particular drum, it just seems to be based on cycles. Maybe the game can send something to the wiimote to get this extra data on command? Maybe it sends it only the ones that have accents?

When the wiimote does send this special data, the 3rd byte has exactly two options for each pad/pedal as follows:
Pedal: B6 or B7
Red: B2 or B3
Yellow: A2 or A3
Blue: 9E or 9F
Orange: 9C or 9D
I cannot find a reason for why it randomly switches between these. The one it picks does not seem to be connected to the 4th or 5th bytes.

the 4th byte is either in the sequence of {0C, 2C, 4C, 6C, 8C, AC, CC} or {0D, 2D, 4D, 6D, 8D, AD, CC} when this special data is sent:
The first half is an even number/letter which _does_ correlate to velocity, where a higher number/letter means a softer hit (read that again, it's counter-intuitive to me). That is, "CX" is the softest I could produce, "0X" is the hardest, where X, the second half of this byte, could either be C or D. Again, I cannot find reason for the dichotomy between using C and D, but I know it is unrelated to the choice of the 3rd byte as I've seen every kind of mix possible. It seems to randomly switch between the two.

the 5th byte, while containing the drum set's + and - buttons as already found out, also changes when the wiimote sends the special information in the 3rd and 4th bytes. It is any one of the following (when not holding down the + or - buttons): 7E, 7F, FE or FF
When holding down the + button, the second half is either "A" or "B" while the first half randomly(?) changes between "7" and "F"
When holding down the - button, the first half is either "6" or "E" while the second half randomly(?) changes between "F" and "E"
Again, I cannot find any correlation between either half of this byte with the third byte or the 2nd half of the 4th byte.


hope this at least gives someone else a start... also, thanks to all of you for getting this started, I've been looking forward to using these with computer for a while now :D