Next Generation Emulation banner

1 - 10 of 10 Posts

·
Registered
Joined
·
14 Posts
Discussion Starter #1
I'm having trouble configuring the joypad/directional control in VBA.
When I first downloaded Version 1.2, I configured the joypad without any problems. One day the joystick controls all of a sudden quit working and I can't figure out how to get it working again. There are some strange and baffling factors involved here and I was hoping somebody might have an idea what's going on and how I can resolve this.

First off, when I say 'joystick controls' I'm referring strictly to the directionals, or the buttons that VBA recognizes as Joy 1 Up, Joy 1 Down, Joy 1 Left, and Joy 1 Right. The default settings match the joypad on my game controller (Gravis Eliminator Gamepad Pro). Before the joypad quit working with VBA, I didn't originally need to configure them. I can assign any of the remaining buttons on my game controller to the directionals but I can't assign the joypad to them.

During the long process of trying to figure this thing out on my own, I discovered after downloading all VBA versions dating back to Version 0.7, that I can configure the joypad with versions 0.7 and 0.8. I cannot configure the joypad with all newer versions starting with Version 0.9a. I consulted Version 0.9a's 'readme.txt' to see what changes were implemented, in the hope that I might find a clue in there somewhere. These were the only entries I found listed in the 'readme.txt' that were relevant to joystick configuration:

- fixed bug reading joypad when LCD is off (under Gameboy Changes)

- support for more joystick axes and HAT(POV) (under Windows Changes)

I DID reinstall the drivers for my game controller right around the same time I discovered that the joypad wasn't working in VBA 1.2 anymore. As was mentioned before, it used to work but then it stopped. So I'm thinking the problem quite possibly stems from that. On the other hand, it doesn't readily explain why the joypad still works with the older VBA versions but not the newer versions. Also, my joypad works with everything else, including several emulators (ZSnes and UltraHLE for example) as well as several PC games. The only thing it doesn't work with is the newer versions of VBA.
Has anyone else ever experienced this problem who might know what the solution is?

System specs: Pentium3 866 L2; WindowsME; 128MB RAM. I hope I didn't forget anything.
 

·
Registered
Joined
·
483 Posts
The joystick configuration changed from version 0.9a on, so if you configured the joystick with a prior version, you will need to reconfigure it.

I assume you are using the Options->Joypad->Configure... menu to do it.
 

·
Registered
Joined
·
14 Posts
Discussion Starter #3
Yes, I am using the Options->Joypad->Configure menu. I have ten buttons on my gamepad in addition to the directionals (VBA recognizes these as 'Joy 1 Buttons 1-10'). I can configure these, because they still work. It's just the directionals (Joy1 Up, Joy1 Down, Joy1 Left, and Joy1 Right) that don't work.

I did try and reconfigure. Actually, Version 1.2 was the first version I had installed on my computer. I grabbed Version 0.7 after experiencing the problem with 1.2 and found out that I could configure 0.7.
 

·
Registered
Joined
·
483 Posts
Download the SDL configurator from the following link:

http://vboy.emuhq.com/downloads/SDLTest-Win32.zip

Run it and see if you get any numbers when you press the directions on the joystick. If so, post them here.

The only explanation I have is that either your joystick has a mode where it is not behaving as expected or you have some joystick program that maps the joystick to keys or something.

Another thing that changed from version 0.8 to version 0.9 is that VBA tries to configure the joystick range, which could potentially fail if the joystick driver does not work correctly.
 

·
Registered
Joined
·
14 Posts
Discussion Starter #5
I did find out where the problem stemmed from after all. Sort of, anyway. I'm pretty sure either UltraHLE or the UltraHLP gamepad configurator is somehow fouling things up with Visual Boy Advance's game controls.
I reinstalled my game controller's drivers and grabbed another copy of VBA 1.2, and got the joypad/directionals working again! Next, I ran UltraHLE and Zelda OoT. At first, Link was running around a bit on his own, changing directions, stopping & going, etc. without any help from me. I took control of Link with my gamepad and ran this automatic movement out of him, which took a few seconds or so. After Link was restored back to normal, I quit UltraHLE and ran VBA 1.2 again. I could not configure the joystick controls anymore.
Something must have happened during those few seconds I was running UltraHLE which disabled the joystick function in VBA.

As for the SDL configurator, I couldn't run it. It called up what looked to me like a DOS prompt and then quickly blinked out. I'll keep working with it.
 

·
Registered
Joined
·
483 Posts
The SDL Configurator needs the SDL.dll file in the file, so you need to extract both into a directory. Try running it from a command line (DOS prompt). It will open a small window and then you should try moving the joystick.

At least now you have some idea of what is going wrong.
 

·
Extra Large Member
Joined
·
936 Posts
The problem could be your control pad. My gravis gamepad pro frequently gets a sort of stuck key error with different emulators wherein it acts as though the control pad is constantly being pressed to the right. It'll go left or up or down while I press left/up/down, but as soon as I let go it goes right again. Sometimes a reboot clears it up. Also, you might want to try insatlling an older driver for it. Using the most updated drivers increased my problems, but reverting to the ones that came on my comp often clears it up.
 

·
Registered
Joined
·
1 Posts
Similar Problem.

I seem to be having a similar problem, though in a much different situation, and I was hoping I could get some advice.

Some system information:
Linux debian 2.6.7-custom-k7 #1 Sat Jul 3 15:13:58 PDT 2004 i686 GNU/Linux
VisualBoyAdvance version 1.7.2 [SDL] (from Debian unstable Packages)
libsdl1.2debian
1.4 GHz Processor, 256MB of RAM, excessive HD Space.

I'm using a USB HID compliant Joystick under Linux, and while I can configure all the other buttons, the directional buttons and the joysticks for the device (a PSX controller) don't seem to function. I don't have a GUI menu system for VBA, but I can edit '/etc/VisualBoyAdvance.cfg', which has allowed me to set all of my other buttons correctly. Here is the relevant exceprt from the cfg file. Again, all of this works except for the directionals. This device functions fine with other programs that utilize joysticks.

Joy0_Left=1000
Joy0_Right=1001
Joy0_Up=1002
Joy0_Down=1003
Joy0_A=1082
Joy0_B=1081
Joy0_L=1086
Joy0_R=1087
Joy0_Start=1088
Joy0_Select=1089
Joy0_Speed=1085
Joy0_Capture=1084

Motion_Left=1001
Motion_Right=1002
Motion_Up=1003
Motion_Down=1004

When I rnu 'SDL-Test', I get the following codes.

For the X-Axis on the directional pad (both Left AND Right return the same value):
JOY AXIS code: 1000

For the Y-Axis on the directional pad (both Up AND Down return the same value):
JOY AXIS code: 1002

The comments in the VisualBoyAdvance.cfg file are not entirely clear what I'm supposed to do with these values. The way they describe it seems as though the values ought to be different in each direction, but I'm not certain.

Any suggestions?
 

·
Registered
Joined
·
2 Posts
13 year thread necro? Why not?

Messing around with an old netbook the only version of VBA I could get working in i386 Lubuntu 17.04 is the SDL version of VBA-M, which like the above post requires editing the config file directly. It appears to be the same file with the same unclear instructions. I got it working thanks to this post, so I thought I'd add my knowledge to the internet archives.

This is to clarify the comments in the config file itself, which are vague at best. What it wants to see is a 4 digit hex code with the first digit being the joystick number (0 for keyboard). My controller appears to be joy0 but using 1 worked for VBA. The other three digits:
  • For a joystick axis, double the axis number (in hex) to get the negative direction, add 1 for the positive direction. Joystick 1 axis 0 is 1000 for left/up, 1001 for right/down. Axis 6 is 100c for left/up, 100d for right/down.
  • For a hat switch (d-pad on many gamepads), multiply the hat number by 4 and add it to 020. Then add 0, 1, 2, or 3 for up, down, right, and left respectively. Usually there is only one hat switch, 0, so 1020, 1021, 1022, 1023 are up, down, right, and left.
  • For all other buttons, add the button number to 080.
Hopefully this will help out a random Google searcher someday...
 

·
Registered
Joined
·
1 Posts
Thanks. I am that Google searcher, but after trying many things and searching on Google many things with several hours invested, the best thing to do is use Visualboy Advance-M or compile it. However, that failed on my old 2006 laptop, so the next best thing is to install "antimicro" to setup the controller for linux or use xpadder for windows.

Antimicro or Xpadder will let you set certain buttons on the controller fire off buttons on the keyboard. As VBA will work with keyboard buttons. This will save you the headache of trying to configure the controller and manually finding out what buttons are what. Granted Antimicro's UI isn't the greatest and its a bit confusing, but its still easier than figuring out the keys to edit in the config for VBA. Just be sure to close the program when you are done with VBA, so it wont interupt play on another emulator.
 
1 - 10 of 10 Posts
Top