[CSDb] - User Forums - VICE 3.7.1 testers needed (Mouse emulation)

You are not logged in - nap

CSDb User Forums

Forums > CSDb Discussions > VICE 3.7.1 testers needed (Mouse emulation)

2023-02-03 19:22

chatGPZ

Registered: Dec 2001
Posts: 11108

VICE 3.7.1 testers needed (Mouse emulation)

So!

Apparently we have a strange bug related to mouse emulation on Windows systems. It would be great if all of you could do a quick test:

- grab the 3.7.1 release from https://github.com/VICE-Team/svn-mirror/releases/tag/3.7.1
- start it and reset settings (just incase it picks up settings from another release)
- enable 1351 mouse emulation for port 1
- run the following program: Mousetest V2
- now enable mouse grab (alt-m) and move around the mouse

Now if that does NOT move the 1351 icon as expected, please report that, and give some details about your system. In particular interesting is the exact OS (eg "Windows 10 22H2"), your graphics card and driver version, and your screen resolution...

Some people reported it does not work for them - while it works for others. This is very strange, we could not yet determine what the systems where it does not work have in common - hence this request.

Thanks in advance!

... 25 posts hidden. Click here to view all posts....

2023-02-06 13:11

chatGPZ

Registered: Dec 2001
Posts: 11108

OK So, those where it doesnt work, please try the following: before you enable "mouse grab", move the VICE window to the center of the screen, and place the mouse pointer in the center of the VICE window. NOW press ALT-M. Acoording to the current working theory this should then make it work. Does it?

2023-02-06 15:22

Angel of Death

Registered: Apr 2008
Posts: 210

Quote: OK So, those where it doesnt work, please try the following: before you enable "mouse grab", move the VICE window to the center of the screen, and place the mouse pointer in the center of the VICE window. NOW press ALT-M. Acoording to the current working theory this should then make it work. Does it?

Did some more testing on different positions on the screen and the mouse is not necessarily placed in the center of the main screen as such but as far as I can see displaced one screen width to the right.

+---------.+ +---------.+
+---s2----+ +----s1---+
+---------.+ +---------.+
+---------.+ +---------.+

(screen size for both is 1920x1080)
eg. VICE is in center screen s2, mouse reappears in center s1.
Move VICE anywhere on s2 and mouse reappears one screen width to the right of it but on the same Y coordinate.
If VICE is started somewhere on s1 the mouse will reappear on the right most edge of s1 (no desktop there so can't go any further).

Here's the log:
AUTOSTART: Done.
Sync reset
GTK3MOUSE: Status changed: 1 (enabled)
mouse move 705.000000, 492.000000 GetCursorPos: 1207, 669
mouse move 700.000000, 344.000000 GetCursorPos: 1202, 521
mouse move 669.000000, 492.000000 GetCursorPos: 1171, 669
mouse move 562.000000, 351.000000 GetCursorPos: 1064, 528
mouse move 691.000000, 303.000000 GetCursorPos: 1193, 480
mouse move 1416.000000, 631.000000 GetCursorPos: 1918, 808
mouse move 1415.000000, 628.000000 GetCursorPos: 1917, 805
mouse move 1415.000000, 627.000000 GetCursorPos: 1917, 804
mouse move 1414.000000, 625.000000 GetCursorPos: 1916, 802
mouse move 1414.000000, 626.000000 GetCursorPos: 1916, 803
mouse move 1414.000000, 625.000000 GetCursorPos: 1916, 802
mouse move 1416.000000, 631.000000 GetCursorPos: 1918, 808
-
mouse move 1417.000000, 634.000000 GetCursorPos: 1919, 811
mouse move 1417.000000, 632.000000 GetCursorPos: 1919, 809
mouse move 1417.000000, 633.000000 GetCursorPos: 1919, 810
mouse move 1417.000000, 633.000000 GetCursorPos: 1919, 810
mouse move 1417.000000, 631.000000 GetCursorPos: 1919, 808
mouse move 1417.000000, 632.000000 GetCursorPos: 1919, 809
mouse move 688.000000, 415.000000 GetCursorPos: 1190, 592
mouse move 1417.000000, 632.000000 GetCursorPos: 1919, 809
mouse move 1417.000000, 634.000000 GetCursorPos: 1919, 811
mouse move 1417.000000, 634.000000 GetCursorPos: 1919, 811
mouse move 1417.000000, 634.000000 GetCursorPos: 1919, 811
-
mouse move 1417.000000, 631.000000 GetCursorPos: 1919, 808
mouse move 1417.000000, 632.000000 GetCursorPos: 1919, 809
mouse move 1417.000000, 632.000000 GetCursorPos: 1919, 809
mouse move 1417.000000, 632.000000 GetCursorPos: 1919, 809
mouse move 440.000000, 8.000000 GetCursorPos: -965, -163
mouse move 686.000000, 32.000000 GetCursorPos: -719, -139
mouse move 695.000000, 407.000000 GetCursorPos: -710, 236
(moved VICE window to second screen coords+1920)
mouse move 2274.000000, 632.000000 GetCursorPos: 869, 461
mouse move 2275.000000, 634.000000 GetCursorPos: 870, 463
mouse move 2275.000000, 634.000000 GetCursorPos: 870, 463
mouse move 2277.000000, 640.000000 GetCursorPos: 872, 469
mouse move 2279.000000, 641.000000 GetCursorPos: 874, 470
-
mouse move 2273.000000, 631.000000 GetCursorPos: 868, 460
mouse move 2272.000000, 631.000000 GetCursorPos: 867, 460
mouse move 2272.000000, 632.000000 GetCursorPos: 867, 461
mouse move 2272.000000, 631.000000 GetCursorPos: 867, 460
GTK3MOUSE: Status changed: 0 (disabled)

2023-02-07 22:50

aNdy

Registered: Jan 2004
Posts: 41

Now using 3.7.1 r43064...

Running x64sc.exe
Dell G15 Ryzen Edition Laptop
Windows 11 Home 21H2 (build 22000.1455)
1920x1080
NVIDIA GeForce RTX 3050 Laptop GPU (Driver 30.0.15.1277)
No touchscreen or second monitor

Test WORKS using both built in track-pad and USB wireless mouse.

2023-02-07 23:00

chatGPZ

Registered: Dec 2001
Posts: 11108

I think to reproduce the problem the following is needed:
- two monitors
- a relatively high display resolution (1920xsomething or so at least)

2023-02-08 18:51

Angel of Death

Registered: Apr 2008
Posts: 210

Quote: I think to reproduce the problem the following is needed:
- two monitors
- a relatively high display resolution (1920xsomething or so at least)

This weekend I hope I'll have the opportunity to test that properly.
"I'll be back..."

2023-02-11 16:20

chatGPZ

Registered: Dec 2001
Posts: 11108

OK Good news: I can reproduce. And i can explain why it works for some and not for others: it depends on which side the primary monitor is located!

Please confirm:
- primary monitor "left", its broken
- primary monitor "right", it works fine

Also macOS and Linux users, please try this as well, so we can see if this is a bug in generic code or OS specific.

2023-02-11 17:44

Angel of Death

Registered: Apr 2008
Posts: 210

Quote: OK Good news: I can reproduce. And i can explain why it works for some and not for others: it depends on which side the primary monitor is located!

Please confirm:
- primary monitor "left", its broken
- primary monitor "right", it works fine

Also macOS and Linux users, please try this as well, so we can see if this is a bug in generic code or OS specific.

I did some further testst and for me it only works when I have only one monitor connected. As far as I can see it doesn't matter whether the primary screen (or whatever spot VICE is on) is configured left or right.
Because of stubborn hardware I was not able to test different resolutions, though.

2023-02-11 18:12

Burglar

Registered: Dec 2004
Posts: 1031

ubuntu 22.04: 2160p left, 1440p right (primary)
3.7.1 and r43064 are both fine

ubuntu 22.04: 2160p left (primary), 1440p right
3.7.1 and r43064 are both fine

2023-02-12 18:28

chatGPZ

Registered: Dec 2001
Posts: 11108

Windows PPL please try https://github.com/VICE-Team/svn-mirror/releases/tag/r43150

2023-02-12 21:30

Angel of Death

Registered: Apr 2008
Posts: 210

Did some testing with moving about and screwing around with settings (and resetting them, etc) and works fine for me now.
Even through my docking station with dodgy drivers.
Good job, VICE people! \o/

Previous - 1 | 2 | 3 | 4 - Next

Refresh

Subscribe to this thread: