Homebrew Controller Problems with VBA GX

[Barim]

Very simply, since the emulator auto-updated to 2.2.7, my gamecube controller has gone messed up on the emulator. It is not like all buttons have been reassigned, all buttons still do what they need to do, with an almost random lag. I've tried both my GC controllers, so the controllers themselves most likely aren't the issue. Anyone else have this problem and found a solution?

Edit: I forgot, this only happens while playing games that worked perfectly fine before, haven't seen any random input lag in the emulator's menus so far.

There used to be an issues section on the emulators main page, but I can no longer find it, so I thought I'd look here for help.

 

[GhostlyDeath]

I also have this problem, however I only have ever used 2.2.7. I was searching through Google to find a solution and found this post.

The controls have a huge delay input and it feels like they stick.

The other emulators such as FCEU GX, SNES9x GX work perfectly fine however.

 

[daxtsu]

Known issue, but it won't be fixed, according to the author. No solution, either, except to use an older version(2.2.5 is the last version for me that didn't have input lag).

 

[Barim]

If I may ask, since it is a recognized issue and was only introduced in a later build, shouldn't it be possible to fix?

 

[daxtsu]

I didn't say can't, I said won't.

So yes, if someone were to go through the code, it'd be possible to fix it. But don't expect to see a fix from Tantric.

 

[Barim]

Then allow me to be more direct, did he tell why he won't? Does it conflict with something or?

 

[daxtsu]

He only releases maintenance updates(new libogc, etc.) of these emulators now, so he has no desire to fix bugs. Or that's how I took it.

 

[Barim]

Right, so if I were to put 2.2.5 back on, would I get an update message every start-up, or only once?

 

[daxtsu]

Every time, but if you can wait until tomorrow, I could upload a version with the update check disabled.

 

[Barim]

Maintaining two versions is not a bad idea actually.

 

[daxtsu]

I managed to compile 2.2.5 with the latest libogc/devkitppc, but I discovered something interesting: The input lag isn't caused by a specific version of VBA, it's apparently caused by the newest libogc, because the officially compiled version of 2.2.5 has no input lag issues, while my compiled one does. I'll try updating to an SVN version of libogc and devkitppc to see if that fixes it.

Edit: ..Nope, it still has input lag even with the latest SVN of libogc. So weird. In any case, here's the 2.2.5 without update checks as you requested, if you want to see if you get input lag or not. I certainly do.

http://www.peejeshare.com/files/363244174/vbagx_wii.zip.html

 

[Barim]

Strangely enough, it gets the same input lag...

Maybe we do need Tantric's aid...

 

[daxtsu]

I peeked through VBA's code a bit, but I'm not really sure where to begin to look for what might be causing the problem. It's just so strange. The latest libogc = input lag, yet only VBA-GX out of the three GX emulators(snes9xgx and fceugx being the others) has this input lag, and they all use the same input and menu code, as far as I know.

So it's like..libogc = input lag, vba = input lag..it's just confusing.

I did a little more testing with other emulators compiled with my toolchain, and it's still only VBA with input lag, so it's definitely pointing to some sort of bug within VBA. Something within it doesn't like newer libogc versions.

 

[Tantric]

Pad.c was changed in libogc awhile back. Vbagx apparently doesn't work well with those changes. I haven't been able to track down why though. But the controller code in vba gx was changed quite a bit from the other emulators when Carl Kenner added the "Wii controls" feature.

 

[Barim]

So, theoretically, the feature might cause more conflicts in the future?

 

[AngryGreek766]

so this isinst going to be fixed?

 

[daxtsu]

This post is a bit redundant, but for those suscribed to this topic...Tantric has resolved the GC controller issue with a new release today.