Possible bug in Input panel in WinUAE 4.10.1.0?

[A500+]

Hi Toni et. al.

WinUAE 4.10.1.0

So I've noticed an issue when trying to set up some controls for a specific game. For some reason Gunship 2000 (AGA) refuses to detect input from any joystick in port 2. Now presumably that's a problem with either the game itself or perhaps the WHDLoad Slave, not WinUAE.

The workaround, or so I thought, is to select '<none>' for 'Port 2' in the 'Game ports' panel and then to map the keyboard inputs for the game to the device you're using in the 'Input' panel. In my case I'm using a PS4 controller so I use the 'Input' panel to map for example the Cursor Keys to Left Stick for cyclic controls, Return to X for fire etc.

Now that works just fine for the session in which you have mapped the controls. The problem arises the next time you launch that config as the 'Device enabled' checkbox for the controller defaults to unchecked (even though the button mappings have been saved and the device is plugged in already etc.) and so I'm forced to hit F12 and manually check the box each time I want to play. Not the end of the world, granted, but it's not expected behaviour.

I've tested using a Quickstart config too - only changing the relevant settings in the 'Game ports' and 'Input' panels and leaving everything else at default and sure enough once '<none>' is selected in the 'Game ports' panel then 'Device enabled' defaults to unchecked whenever the config is loaded.

I've tested the same configs with WinUAE 4.9.1.0 and this behaviour is not present, so looks like a bug introduced in 4.10.1.0?

Edit: I've attached the boot logs for each version in case they help. The logs were taken with an Xbox 360 controller plugged in as I was testing to see if a different controller made a difference but it didn't - same behaviour no matter the input device it seems.

Thanks.

[Toni Wilen]

Attach your config file, thanks (use Xbox pad if possible)
4.10.0 probably works? 4.10.1 had some input fixes.

[A500+]

Apologies for the late response - the real world got in the way again unfortunately!

Originally Posted by Toni Wilen

Attach your config file, thanks (use Xbox pad if possible)

Config with Xbox 360 pad input bindings now attached.

Originally Posted by Toni Wilen

4.10.0 probably works? 4.10.1 had some input fixes.

Yeah just tested and 4.10.0 works as expected so looks like the bug was only introduced in 4.10.1.

[Toni Wilen]

Thanks. winuae.7z should fix it, please confirm.

[A500+]

Yeah that seems to have fixed the issue