Main > Main Forum
GP-Wiz40 Problems
Mat:
In regards to the MAME issue on the PC, I set the default.cfg file to read-only, but it didn't help. After starting a new game the MAME menu still had the pause function assigned to "N/A", even though the .cfg file had it assigned to the pause input on the GP-Wiz. I tried wiring my pause button to the 2-player button 1 input on the GP-Wiz and so far it still works after starting several new games. This'll be a problem though when I build my 2-player joystick.
As for the BNES issue on the Mac, I couldn't find any gaming controller test app. I downloaded a program called "Joystick and Gamepad Tester", and according to it the X-axis and Y-axis are providing at-rest values of 127, minimum values of 0, and maximum values of 255. I don't really know what this info means or what to do with it, but there it is.
I installed two programs that are supposed to allow gamepads to initiate virtual keyboard button presses as a round-a-bout method of using the emulator called "Enjoy" and "GamePad Companion 2.4." Both of these worked fine for the shot buttons, but the same problems with the directional inputs that existed without using them were still present.
So that's where I am now...
CoryBee:
Forgot to mention before, "Mame.ini" is the file that holds controller configurations.
Change your controller setup in mame, exit and set mame.ini too "read only"
Hope anything we say helps. There must be a particular reason this is happening though. :banghead:
RandyT:
It sounds like you may be confusing the "common use" heading in the documentation for fixed functions. There is no specific "pause" function in the hardware, rather recommended uses for the buttons. The "pause' button is simply "Button 18" on the device, so changing them around doesn't cause any issues. If you go into the Windows Game Controllers test, you can see what the hardware is doing, and verify that all of the functions of the GP-Wiz40 are working. However, it sounds like the MAME variant you are using may not be properly saving control configurations, or causing them to change. Have you tried a different version, or perhaps the official MAME release to see if the issue goes away?
Also, make sure that you don't have separate configurations defined for the game(s) you are seeing this happen with. If you do, they will override the defaults. If you had game-specific configurations defined for your gamepads, those definitions may be linked to something which no longer exists. Try clearing any and all game-specific configurations and see if the issue persists. If all else fails, start from a clean slate to be sure.
As for the Mac OS, we do not directly support it, so I cannot speak to what the issues are with that OS. I know from doing some research on gaming controllers and Macs that they seem to be picky about the hardware they work with. I have seen reports of game controllers locking up the system, and other strange behavior, in the absence of drivers, or in cases where the hardware was not specifically designed for the Mac OS. The software you downloaded is reading the reports correctly, but the application you are running does not seem to be interpreting that data properly. You may want to check with the author to see if this is a known issue. Alternatively, you might want to try ControllerMate to see if it allows for calibration of the axes. Frankly, it seems odd that the OS doesn't have a built in function for gaming controller calibration. Are you certain none exists? Alternatively, you can use any 4 button inputs for joystick directions (provided the application allows for it... most do) in the event that that you cannot calibrate the axes. With 40 inputs, you will still have enough to disregard the axes and make a fully functional 2-player panel, with some left over.
Navigation
[0] Message Index
[*] Previous page
Go to full version