FS-UAE <= 2.9.x development series

[Retro-Nerd]

If i press the buttons on the pad and mouse i get this OSD messsage.

For WHDLoad: I see.

[prowler]

Originally Posted by Retro-Nerd

Those scanlines look nice, Retro!

[TCD]

Originally Posted by prowler

Those scanlines look nice, Retro!

Have a look here prowler: http://eab.abime.net/showthread.php?t=67490

(and of course at FS-UAE too )

[prowler]

Originally Posted by TheCyberDruid

Have a look here prowler: http://eab.abime.net/showthread.php?t=67490

I had suspected that somehow.

Originally Posted by TheCyberDruid

(and of course at FS-UAE too )

Oh yes, of course!

(I really don't know how Frode keeps up the pace of development! )

[FrodeSolheim]

Originally Posted by Retro-Nerd

Another thing: I always use the latest WHDLoad beta, but the launcher automatically downloads the latest full version. In this case 17.1. Is there a workaround?

Some versions will be selectable with the x_whdload_version option in the next development release. Added "2013-03-01" (beta) version. "16.0" - "16.9" and "17.0" and "17.1" can be selected too. It defaults to 17.1.

[Retro-Nerd]

"16.0" - "16.9" and "17.0" and "17.1" can be selected (defaults to 17.1)

And maybe the 17.2 beta too? Any clue why the CD32 pad option doesn't work properly? I can't start any game then.

[TCD]

Originally Posted by FrodeSolheim

Added "2013-03-01" (beta) version.

That's the 17.2 beta

[FrodeSolheim]

Originally Posted by Retro-Nerd

Any clue why the CD32 pad option doesn't work properly? I can't start any game then.

Well, based on the screenshots and what you say, FS-UAE acts like it receives (bogus?) mouse button presses which re-inserts the mouse in port 0. Could be a bug but I haven't encountered it. After you have started FS-UAE and triggered the bug, can you quit FS-UAE and post FS-UAE.log.txt?

[Retro-Nerd]

If i start with a CD32 option for my pad, and press the first button once in a game, the mouse port is replaced by the pad too. Strange.

[FrodeSolheim]

I don't know (yet) if this is the problem, but:

device #01 found: ?
- 2 buttons 0 hats 2 axes 0 balls
device #02 found: ? #2
- 2 buttons 0 hats 2 axes 0 balls
device #03 found: USB GAMEPAD
- 9 buttons 0 hats 2 axes 0 balls

a couple of devices with invalid(?) names are found, and FS-UAE later uses a blank string for these it seems. It is possible FS-UAE gets confused by this. Do you have anything with 2 buttons and 2 axes you can try to plug out?

(i also assume you don't have any mapping software which maps gamepad buttons to mouse button).

[Retro-Nerd]

This "?" device is an USB adapter for real Amiga/Atari Style 9pin sticks. I've already tried it without, no luck. And no, i don't use any installed software for gamepad mapping. The CD32 pad option works perfectly in WinUAE though.

[FrodeSolheim]

Originally Posted by Retro-Nerd

If i start with a CD32 option for my pad, and press the first button once in a game, the mouse port is replaced by the pad too. Strange.

I checked the logs, and there is one problem - the're no CD32 mapping for this joystick. (Amiga automatically works since the joystick is so simple, CD32 gamepad needs a mapping). So open the Joystick config tool from FS-UAE Launcher and configure your gamepad.

(It is possible the auto-select bug is an accidental consequence of the missing CD32 mapping, will check that later).

[Retro-Nerd]

Mmh, happens with my Logitech Dual Action pad too. And WinUAE needs no manually mapping for the CD32 pad option. Well, will try it though.

Edit: Nope, doesn't work with a manually configured pad. The config is saved properly, but if i re-check the mappings in the Launcher it shows nothing.

# USB Gamepad

[default]
include = universal_gamepad
axis_0_neg = dpad_left
axis_0_pos = dpad_right
axis_1_neg = dpad_up
axis_1_pos = dpad_down
button_3 = west_button
button_4 = north_button
button_1 = east_button
button_0 = south_button
button_8 = start_button
button_5 = menu_button
button_6 = left_trigger
button_7 = right_trigger

[FrodeSolheim]

Originally Posted by Retro-Nerd

Nope, doesn't work with a manually configured pad. The config is saved properly, but if i re-check the mappings in the Launcher it shows nothing.

The old config is not (yet) re-loaded when you start the tool again, so this not a problem just test that it works in FS-UAE. (This tools needs a little bit of love).

Originally Posted by Retro-Nerd

If i press the buttons on the pad and mouse i get this OSD messsage.

Sorry, I missed the "and mouse" bit. I though you got both messages by just pressing a single button on the gamepad. That's what made me scratch my head. It all makes sense now.

Btw, FS-UAE *could* support autoconfiguring any game pad for CD32, it's just that the button order would basically be random. You would have to just try which one is the red button etc.

But I'll make sure to add an OSD message if the device is missing config!

[Retro-Nerd]

Wait, the Logitech Dual Action pad works indeed with your CD32 autoconfig option. Well, it's the Sega Saturn USB Pad then. WinUAE has no problem with it.

[FrodeSolheim]

Originally Posted by Retro-Nerd

Wait, the Logitech Dual Action pad works indeed with your CD32 autoconfig option. Well, it's the Sega Saturn USB Pad then. WinUAE has no problem with it.

It would be strange if it does not work with that device too. But you need to create a separate mapping for that device if you haven't already done so.

[Retro-Nerd]

I did, as i posted above. Also copied the created usb_gamepad_9_2_0_0_windows.conf from "c:\Users\Name\Documents\FS-UAE\Controllers\" to "d:\fs-uae\share\fs-uae\input\". Really Strange.

Edit: Now it works. I had to delete the automatically created file from "c:\Users\Name\Documents\FS-UAE\Controllers\". Strangely Slam Tilt WHDLoad with the new CD32 pad patch behaves still in the same way.

Edit2: Also found out why. If i start Slam Tilt WHDLoad directly via Zip archive it doesn't work properly with the pad patch+CD32 option. But it works fine if i boot a ClassicWB with Slam Tilt installed.

[FrodeSolheim]

A new development version has been released. Changes in FS-UAE 2.1.31dev:

• Shortcuts F12 + P or Pause/Break key to pause the emulation.
• Left and right mouse buttons are aliased to joystick port 0 fire and 2nd button (unless joystick_port0_mode is nothing, or mouse is already used in a port).
• Disabled automatic port 0 joystick switching for mouse, alias mouse buttons instead.
• Disabled automatic port 0 joystick switching for emulated joystick.
• Warn, if necessary, when joystick/gamepad has no config for CD32 game pad.
• Fixed scanline code for PPC.
• Support for a more advanced viewport syntax.
• Updated bitmap font with new character.
• Updated translations: pl [grimi].
• (Launcher) Retry database download operations several times on failure.
• (Launcher) Support floppy_list field from online database, as well as new database fields.
• (Launcher) WHDLoad versions can be selected via the new x_whdload_version option.
• (Launcher) Added WHDLoad versions 16.0 – 16.9 [TheCyberDruid].
• (Launcher) ADFFileExtractor module [TheCyberDruid].
• (Launcher) SetPatch is extracted using the new ADFFileExtractor module instead of the old hack.

[Retro-Nerd]

-(Launcher) WHDLoad versions can be selected via the new x_whdload_version option
-(Launcher) Added WHDLoad versions 16.0 – 16.9 [TheCyberDruid]

Any chance that you add 17.2 beta too? Works fine btw.

[FrodeSolheim]

Originally Posted by Retro-Nerd

Any chance that you add 17.2 beta too? Works fine btw.

yep custom option: x_whdload_version = 2013-03-01