Problem with a new mouse in WinUAE.

[Xiantrius]

Before that, a note, I ask everyone to read the text first, so that no help is suggested that I have already tried.

Problem:
I have a rather unusual problem.
I bought a new mouse for my PC a few days ago.
I'm currently playing Settlers 1 with someone and we need 2 mice, as most people here know.
I can't use a Windows mouse.
Must therefore go to HID compliant mouse.
This worked perfectly with the previous mouse
Have Windows 10 Pro
In any case, meet the requirements of my system.
The mouse means:
Corsair SABER PRO gaming mouse
Symptoms:
In Settler 1 I have to set the config to HID-compliant mouse.
I can move the mouse but all buttons of this mouse are not triggered within WinUAE.


Already tried to find solutions:

attempt 1
The mouse works perfectly outside of WinUAE.
Have the latest version, even before the problem occurred.

attempt 2
I have initialized all mouse drivers again. PC restarted. Unfortunately that didn't help.

attempt 3
I even tried to use the original driver for this mouse. PC was also restarted to be on the safe side, but unfortunately this was also unsuccessful.

attempt 4
Tried using the mouse on 2 other USB ports via WinUAE. That too was unsuccessful.

attempt 5
Tried both WinUAE 32-bit and WinUAE 64-bit versions.

Summary:
The Corsair SABER PRO gaming mouse can be used with Optioon Windows mouse.
But as soon as you play games where 2 mice are needed, such as: the good old The Settlers 1, I have to go to HID compliant mouse.
HID only lets my mouse move but can't click anything.
The previous mouse, on the other hand, worked without any problems.
I could use the old mouse again, but I really don't want to, because the left mouse button sometimes double-clicks.
I'm at a loss now, what else can I do?

If there is no more option.
I would like to ask Toni Wilen for help to take care of the problem.
Thanks in advance.

Here Link my new Mouse:
https://www.amazon.de/gp/product/B00...language=en_GB


Kind regards,
Xiantrius

[Toni Wilen]

It sounds like some "helper" application does something weird with rawinput events or tries to redirect them to "windows mouse".

What happens if you press Remap/Test in GamePorts panel, then press Test button to enter test mode and press mouse buttons? What appears at the bottom message line? Nothing appears? Button event is listed but mouse is wrong?

F12 to exit from test mode.

(this is simple part of test, log checks later depending on test results)

[Xiantrius]

Originally Posted by Toni Wilen

It sounds like some "helper" application does something weird with rawinput events or tries to redirect them to "windows mouse".

What happens if you press Remap/Test in GamePorts panel, then press Test button to enter test mode and press mouse buttons? What appears at the bottom message line? Nothing appears? Button event is listed but mouse is wrong?

F12 to exit from test mode.

(this is simple part of test, log checks later depending on test results)

hi, Toni Wilen, first of all thank you for taking care of the problem.

I ran the test and when I press a button on the mouse it doesn't respond, the other mouse does.
Even if the workbench was loaded in the Amiga Emulator, I can't click anything, neither with the left nor with the right mouse button.
I also have Workbench 3.2.1 there you can also use the middle button and scroll, doesn't work either.
The mouse can only be moved in WinUAE with HID setting.
Windows Mouse works great, but it fails in games where 2 mice are required.
If I interpret correctly, a new patch for the mice that are not yet fully compatible would have to fix the problem.


I bought another Shark Force mouse and just tried it out.
Link for this Maus:
Shark Force Mouse
Everything works like before.
All buttons can be pressed and movement is ok.

[Toni Wilen]

Could you do following:

Disconnect all other mice, keep only the "non-working" Corsair mouse plugged in.
Run winuae with following command line parameters: -log -inputlog 2 (winuae.exe -log -inputlog 2)
Do not load any config, don't start emulation.
Open game ports panel and click first Remap/Test button, click Test button. Press and release each mouse button one by one while checking if new log message appears (one line should appear when button is pressed and another when released).
Press F12 to exit test mode, close winuae.
Attach winuaebootlog.txt (it contains important initialization messages and above test log messages)

In "worst" case I need to buy that mouse. (But usually I can't duplicate weird problems.. so it might not solve anything..)

[Xiantrius]

hi,

1. I only have 1 mouse connected that has the problem to get along with WinUAE,
2. I entered the argument at WinUAE.
3. Did the remap test with Windows mouse and then HID compliant mouse and pressed each mouse button and moved the scroll button back and forth.
The problem with HID compliant mouse is that no buttons are displayed.

The log has been saved.

So here LogFile.

[Toni Wilen]

Log looks fine, button flags are correct. Strange.

- Does mouse button mappings look correct in Input panel? (Make sure top menu says "Game Ports panel", then select correct mouse)
- What happens if you select Input panel, click Test. Press mouse left button. Does some mouse get selected? Or nothing happens? If nothing, does correct mouse get selected if you click Test and then move the mouse? (F12 to exit)
- Delete or move configurations/default.uae and try again.

[Xiantrius]

Originally Posted by Toni Wilen

Log looks fine, button flags are correct. Strange.

- Does mouse button mappings look correct in Input panel? (Make sure top menu says "Game Ports panel", then select correct mouse)
- What happens if you select Input panel, click Test. Press mouse left button. Does some mouse get selected? Or nothing happens? If nothing, does correct mouse get selected if you click Test and then move the mouse? (F12 to exit)
- Delete or move configurations/default.uae and try again.

Hi,
I have tried everything from my side.
The mouse can only be moved, but cannot click anything with any mouse button.
When configuring, no button is displayed on this mouse and no button is displayed during the test either, while everything has always worked correctly with others and in the past.
I have tested more than 3x so far and have also initialized drivers again.
Please see post 1.
There's no point in testing this 10x if it's not a new way to hope it works.
It's definitely up to WinUAE.
I am 90% sure if you now buy the mouse I linked in the first post, you will have the same problem.
In Windows itself I have 0 problems. In WinUAE only until I set HID there are obviously problems. Maybe your emulator can't identify the mouse properly, or addresses conflict... I don't know.
I also did what you said and only connected this mouse alone, but unfortunately nothing changed with the problem.
The fact is that the mouse doesn't get along and you can possibly reproduce it in other people who buy this mouse and try to set it as a HID.
I don't know which mouse types your WinUAE doesn't support yet. The Saber Maus certainly isn't complete.
I also ran and tested WinUAE in default mode, nothing changed to positive, sorry if I'm annoying you with that.

I like using your WinUAE because it reminds me of the Amiga era and I get along with it quite well.
You have done a lot of work on your project.
That deserves respect.

best regards,
Xiantrius

[Toni Wilen]

Problem was found, mouse reports having 32 buttons (for some unknown reason) which was rejected as invalid.

[Xiantrius]

ok thx Toni Wilen,
Looking forward to the Official Fix WinUAE v4.9.2 this year.

best regards,
Xiantrius