Winuae Loader Control mapping problem

[r05sco]

Hi all,
I have got the Amiga all set up working perfectly. However i cant seem to be able to map any of the inputs correctly. I'm using a Minipac, that i think is set up for mame default. I read somewhere that winuae loader default is for the Ipac, so that should be the same as minipac? I have enabled xarcade left and right, but the inputs seem to be all messed up. Tried so many different settings but with no success, the best i have managed was getting the player 2 joystick working with two buttons. Do i need to adjust my setting in winuae maybe?
Any help would be most appreciated,
Also, big up to the guys doing the wheel art for the WHDLoad set, really good work.

[UKShark]

Exactly the same problem, still trying to work it out.

[betjenten]

Anything new on this? I he the same problem.

[Goku23]

Anything new on this? I he the same problem.

Hi,

This has been bugging me for a few days now, but I have managed to get WinUAELoader to map my joystick and buttons.

P1 controls are mapped to the cursor keys and LCTRL, LALT, and Space which map directly to my standard settings on the I-Pac.

P2 controls map to R, D, F, G, with A, S, Q, being the fire buttons. So these map to the default settings for the second stick (not wired up yet).

I can play a 2P game, such as Alien Breed and both controls work. P1 games map to the P1 controller so there is no swapping (unless the game uses the ports differently). I can use the mouse in games like Cannon Fodder as well, but I'm not planning on having a trackerball in the cab, so still looking for a way to emulate the mouse with joystick.

I messed around with WinUAE but could no get anything to stick, then realised that WinUAELoader overwrites settings at a higher level so I ran more tests at that end.

First I zeroed all the input maps (KeyboardA=0,0,0...) and the enable flags to false for the 6 input options (EnableKeyboardAMap=false) in the Data/WinUAELoader.ini file, so I had a blank input setup when I go back into WinUAELoader.

In WinUAELoader, set port 0 (P2) to be "X-Arcade Right" and port 1 to "X-Arcade Left".

You should notice that in each of the 6 inputs, the enabled checkbox is blank and the third column "New Input" is all set to "none". Go to the "X-Arcade" tab and check the enabled box. I then mapped the direction buttons to the cursors and buttons 1, 2, and 3 to LCTRL, LALT, and Space. I left the other buttons alone set at "none" (for now).

For P2 go to the "X-Arcade Right" tab and just enable it. The default settings seem to work fine.

I found through testing that if you did not map the P1 buttons to the cursors, it defaults to the number pad (no P1 joystick then) and the P2 directions are shifted to the cursors, again no joystick for P2.

After that, set the rest of your settings for graphics etc. I launched though Hyperspin and started the games, but used F12 in game to go to the WinUAE config and the gameports section on host. If you have WinUAELoader running though Hyperlaunch, it should carry through your settings to WinUAE. At port 0 (X-Arcade Right), hit the "test" button and try your R, D, F, G, A, S, Q keys to see how it works in game. When you do the same for port 1, you will see that the key names refer to the number pad. Don't worry just try your cursors and you can see WinUAELoader overwriting the keys.

Click OK and play the game.

I tested with Alien Breed, launching 1 and 2 player games and in both cases player one is in green and uses the left side controls. I switched to Agony and again left side is P1.

When launching a mouse driven game, there is a line in the WHDLoad.XML file to "UseMouse=TRUE", in this case port 0 will become the mouse once you click the LMB in game.

From a little testing I found that my default Data/WHDLoad.uae (in WinUAELoader) changed slightly

joyport0=kbd5
joyport0autofire=none
joyport0mode=gamepad

changes to

joyport0=mouse1
joyport0autofire=none
joyport0mode=gamepad

When you exit and launch a 2 player joystick game, the setting defaults back to "kbd5" and P2 is working again. If you change the "UseMouse=" setting to false in the WHDLoad database, you can attempt to use the P2 controls as the mouse. I can't seem to emulate the mouse this way or any other, so that's as far as I've got. I'm not sure how a trackerball would work in this setup.

Sorry for the long first post, but I'd not found any solid answers on this or other forums and the Amiga is on of the last systems I need to setup.

If anyone needs more help, PM me and I'll try to help out.

[mr_tap]

sure I asked this before and got the answer "one fire button only".

I've spent hours trying to get all 6 fire buttons on my cab to work with no joy. Must be some fundamental issue as otherwise this kind of thing would have been sorted early on.

[brolly]

Whoever gave you that answer is wrong.

Use Goku's method and you should be able to use the 3 fire buttons just fine (even though atm I don't recall any non-cd32 game that actually needs more than 2 buttons). If you can't change the default buttons just stick with the default x-arcade ones and remap them outside using an ahk script.