Logitech game controller don't work as it should in WinUAE v.4.3.0

Apone_90s · 29 January 2020, 21:47

Hallo
My Logitech Cordless RumblePad 2 gamepad doesn't work as it should in WinUAE v.4.3.0 (final version).
It works fine in the Mouse & Joystick settings when i use the Remap/Test function but, not in emulation.
When i play games the X & Y Axis works but not the fire buttons.
Everything works in WinUAE v.4.2.1.

My OS is Windows 10 64-bit
I have made and attached log files for both WinUAE versions.

Kind Regards

DamienD · 30 January 2020, 12:55

Heya Apone_90s,

Welcome to EAB

You could try using -nodirectinput or -norawhid command line parameters when starting WinUAE 4.3.0 as see if it helps.

Toni Wilen · 30 January 2020, 20:19

Logs are practically identical..

Does it only happen if you use it in CD32 pad mode? Does fire work if you configure it as a "normal" joystick?

Apone_90s · 31 January 2020, 01:41

Running WinUAE with '-nodirectinput' or '-norawhid' doesn't change anything :-(
Configure it as a "normal" joystick, the fire button is now working :-)

Toni Wilen · 31 January 2020, 20:02

Command line parameters won't help if Input test/remap works.

Did you try multiple games? Does it only affect non-CD32 games or also CD32 games?

Apone_90s · 01 February 2020, 02:18

The problem appears in other games. But it was very difficult to test CD32 games (iso) because WinUAE keep crashing when i want to boot the CD iso's.
Sometimes it boots fine undtil game intro finish then it just stuck. These things don't appear in WinUAE v.4.2.1 i have tester that today also.

I tried to remap the joypad Buttons to my PC-Keyboad and discovered that the problem also appears there too.
And again, no problems in v.4.2.1

Toni Wilen · 01 February 2020, 09:31

Button problem confirmed, depending on config, cd32 red is not working as a normal fire (cd32 pad mode is incorrectly detected).

How does it crash? Does it also happen in windowed mode? Does it create crash dump file?

Apone_90s · 01 February 2020, 16:15

WinUAE just shut down like the process is terminated.
It also happens in window mode.
It create crash dump files

I have attached some dmp files.

Toni Wilen · 01 February 2020, 16:34

For some reason memcmp() seems to access bytes after end of start+size range and there is no memory mapped after it, causing the crash.

Possibly it is msvc redistributable bug or version mismatch or something even more weird, especially if it works randomly.

You can bypass this crash by setting 68020 CPU in CD32 mode.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Controller adaptors don't work	Sgt Jack V	support.FS-UAE	2	03 February 2018 15:10
compiled demo don't work on winuae a500 smartstart	Raislin77it	Coders. Blitz Basic	8	24 January 2016 23:00
Controls don't work at all (not WinUAE)	shapey	New to Emulation or Amiga scene	8	21 January 2009 15:02
What do you do when you configure a Logitech USB controller?	Cardynal	New to Emulation or Amiga scene	0	15 November 2006 19:01
Scanlines don't work in new mini WinUAE	dreamkatcha	support.WinUAE	0	27 July 2003 17:59

30 January 2020, 12:55	#2
DamienD Banned Join Date: Aug 2005 Location: London / Sydney Age: 47 Posts: 20,420	Heya Apone_90s, Welcome to EAB You could try using -nodirectinput or -norawhid command line parameters when starting WinUAE 4.3.0 as see if it helps.

30 January 2020, 20:19	#3
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,516	Logs are practically identical.. Does it only happen if you use it in CD32 pad mode? Does fire work if you configure it as a "normal" joystick?

31 January 2020, 01:41	#4
Apone_90s Registered User Join Date: Jan 2020 Location: Denmark Posts: 4	Running WinUAE with '-nodirectinput' or '-norawhid' doesn't change anything :-( Configure it as a "normal" joystick, the fire button is now working :-)

31 January 2020, 20:02	#5
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,516	Command line parameters won't help if Input test/remap works. Did you try multiple games? Does it only affect non-CD32 games or also CD32 games?

01 February 2020, 02:18	#6
Apone_90s Registered User Join Date: Jan 2020 Location: Denmark Posts: 4	The problem appears in other games. But it was very difficult to test CD32 games (iso) because WinUAE keep crashing when i want to boot the CD iso's. Sometimes it boots fine undtil game intro finish then it just stuck. These things don't appear in WinUAE v.4.2.1 i have tester that today also. I tried to remap the joypad Buttons to my PC-Keyboad and discovered that the problem also appears there too. And again, no problems in v.4.2.1

01 February 2020, 09:31	#7
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,516	Button problem confirmed, depending on config, cd32 red is not working as a normal fire (cd32 pad mode is incorrectly detected). How does it crash? Does it also happen in windowed mode? Does it create crash dump file?

01 February 2020, 16:34	#9
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,516	For some reason memcmp() seems to access bytes after end of start+size range and there is no memory mapped after it, causing the crash. Possibly it is msvc redistributable bug or version mismatch or something even more weird, especially if it works randomly. You can bypass this crash by setting 68020 CPU in CD32 mode.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)