Menu Navigation Painfully slow when using drum controller.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use RB2 Wireless drums. (Possibly others.)
2. Attempt to scroll with yellow/blue pads.
3. Notice the amount of hits it takes to actually scroll to the next menu
item/song.

What is the expected output? What do you see instead?
I would expect for the lists to scroll upon each hit of the drum pad,
however, it takes two, three, sometimes even five or more hits to scroll to
the next item. Paradiddles don't even improve the scrolling.

What version of the product are you using? On what operating system?
r875, Kubuntu Linux. RB2 Drums, and default xpad kernel drivers.

Please provide any additional information below.
I believe this issue first popped up when holding down the strumbar was
implemented in the game, but I'm not sure. I've been a bit too busy with
work to post an issue about this.

I should probably mention that using the Y and X buttons have the same
result, same thing with the D-Pad. The test keys menu however, recognise
every hit, so it isn't the drums themselves.

Original issue reported on code.google.com by lysdestic@gmail.com on 30 Jan 2009 at 4:09

[GoogleCodeExporter]

Get a fraps-like Linux utility and check your framerate. If it's really low, the
drums don't seem to pick up hits as well (that's why -- I think -- that in Test 
keys
the drum keys dont light up that well... it's such a quick hit its tough for 
the game
to register it).

Essentially that was my problem, mostly caused by the Rock Band 2 playlist due 
to the
loading of album images. However, I did not have your problem with the buttons, 
so
maybe this could be a new issue.

Original comment by ryanturcotte@gmail.com on 30 Jan 2009 at 7:03

[GoogleCodeExporter]

I should mention that the key tester doesn't have the issue, all hits are 
recognised.
In game is fine as well, the only time I have the issue is when I am browsing 
menus
or the set list.

As far as a fraps like utility, no need, I have display FPS set to on in game, 
and
luckily, this sends output to the terminal (not in game) even when I am 
browsing the
set list, and it never dips below 30. In game it runs smooth as well, usually 
over 80.

Original comment by lysdestic@gmail.com on 30 Jan 2009 at 3:14

[GoogleCodeExporter]

Tried it with an entirely new xbox driver for Linux, one that reads the 
controller in
an entirely different manner, and the same issue occured. So it isn't the 
driver, and
certainly isn't the controller.

Original comment by lysdestic@gmail.com on 31 Jan 2009 at 1:08

[GoogleCodeExporter]

Okay, some seemed to discount the code as the issue, but, here is the deal. I 
went
through the tedious process of rolling back revisions until I found where the 
issue
started, and finally discovered that the problem went away once I made it to 
r836,
meaning that one of the changes that happened to GameEngine, Dialogs, Settings, 
or
Menu.py in r837 is what started this issue.

I hope this helps, and I hope that all the research I have done is enough to 
confirm
this issue.

So, let's recap.

1. RB2 Drums take multiple hits in order to scroll the menus.
2. I've tried multiple drivers, same issue.
3. I've tried other GFX drivers, and the FPS is good; same issue.
4. Clean .ini did nothing.
5. This occurs in all menus, but not in the game itself, or in the keytester, 
meaning
the game is getting the correct amount of hits. (This point made the alternative
driver idea moot...)
6. Rolling back to r836 eliminated the issue.

What changes were made in 836, and is there any chance of seeing a fix for this?

Original comment by lysdestic@gmail.com on 31 Jan 2009 at 11:15

[GoogleCodeExporter]

Ah, I meant to say, "What changes were made in r837, and is there any chance of
seeing a fix for this?"

Original comment by lysdestic@gmail.com on 31 Jan 2009 at 11:16

[GoogleCodeExporter]

I don't have the issue you have, but what you did to try to get it work is a 
valid
way of finding where the bug is. 

I looked at the code, but without understanding how your Linux drivers are 
processing
the drum hits I don't know where the problem would be. The code looks valid.

Maybe one of the developers can probably figure it out eventually.

Original comment by ryanturcotte@gmail.com on 31 Jan 2009 at 11:53

[GoogleCodeExporter]

Verbose out put from the driver can be found here: http://pastebin.com/f3bc658ee

Ignore the blank ones and the double hits--the double hits are from pressure
sensitivity, I think.

That was me doing a four tom roll, four hits to each pad, and hitting the bass 
pedal
every four hits.

Original comment by lysdestic@gmail.com on 1 Feb 2009 at 12:31

[GoogleCodeExporter]

Not that it matters since I'm the only one having the issue according to 
Akedrou, but
it happens when I scroll with the keyboard too.

Original comment by lysdestic@gmail.com on 1 Feb 2009 at 5:16

[GoogleCodeExporter]

I can confirm it happens with the keyboard too; on Windows.
You just have to tap the key quickly, and it won't register. Of course with 
drum sets
you have no choice but to tap quickly, and some kits hold the note on longer 
than others.

Original comment by death.au on 2 Feb 2009 at 9:15

[GoogleCodeExporter]

So, I guess that confirms it isn't Linux related, nor is it related to the 
drums.

Hopefully, someone will take notice of this soon.

Original comment by lysdestic@gmail.com on 2 Feb 2009 at 10:56

[GoogleCodeExporter]

Should be fixed in r900.

Original comment by john.stumpo on 2 Feb 2009 at 11:25

• Changed state: Fixed

[GoogleCodeExporter]

Thanks a bunch, John. That did the trick. looking at the code, it was something
simple, but alas, I'm no programmer.

I knew it had to be something basic, I'm just glad to know it wasn't on my end.

Original comment by lysdestic@gmail.com on 3 Feb 2009 at 1:28