Cursor jumps to other monitor when hovering an overlayed window
Magpie version 程序版本
0.11.1
Windows version 系统版本
win10 22H2
Related screenshot (optional) 相关截图(可选)
https://github.com/user-attachments/assets/8ed8bf02-f385-438b-b6f6-31ea053c3da2
Reproduction steps 复现步骤
Have the game in fullscreen using magpie, and use an overlay window, for example JL or windows built-in On-Screen Keyboard. Then mouse over the overlay, sometimes the cursor will be seen for a single frame on the other monitor, or sometimes it will jump there completely and you will have to move it back to your main monitor manually. I've attached a video showing the effect (ignore the double cursor, it's just my recording software) of the mouse completely jumping to the other monitor when simply hovering JL. I've reproduced this with Magpie 0.11.0 and 0.11.1, but it worked correctly in 0.10.6 and other previous versions.
Log files 日志文件
This is likely because the overlay window has a higher integrity level than Magpie, and due to UIPI, the OS prevents Magpie from changing the cursor position. I’ll look into this when I have some free time.
Did you look into this? I have an similar issue when im running an aplication in full screen with magpie and i move my cursor from 1 monitor to an other monitor.
Update: I downloaded the v0.10.1 version where this issue doesnt seem to excist for me. Just that the cursor alignment is off when moving from 1 monitor to an other monitor
This issue should be resolved in v0.11. Try running Magpie as an administrator.
Im running v0.11.1 and even running as an admin, this issue still happens
Here a video example of the issue. Running magpie in admin
https://github.com/user-attachments/assets/7abb8801-36de-4920-920c-9f710591dabb
Are you referring to the cursor automatically skipping over black borders? This is intended behavior: if there’s no screen beyond the black border, the cursor will stop at it; otherwise, it will skip over.
This is not what iam refering to. Im quikly moving my cursor between my 2 monitors to trigger it. Please watch at 0:05 where it first happens. The cursor jumps quikly all the way left - in my left monitor. This happens 3 times total in this video.
Ill send a new video later without the black borders. Maybe it will make it more clear
Hopefully this video makes it more clear. Magpie is still in fullscreen through the magpie toggle itself, in admin mode.
Update: I think this might be an issue related to windows 11. My friend has the same issue once he updated to windows 11. He did not have this issue when he was running windows 10. Iam running windows 11 aswell
https://github.com/user-attachments/assets/01fd2979-da64-47ce-8108-8e30ad6f9711
Thank you for the video; it clearly demonstrates the issue. I’m using Win11 23H2 and haven’t encountered this error, but I’ll investigate further.
I have also been encountering the same behavior on v0.11.1 in Win 11 22H2. I have two vertical monitors and then a horizontal one on the right. The horizontal one is where i use magpie w/ VN's, and it jumps two monitors over when it enters the horizontal duplicate display magpie screen.
Dropped back to a very old version i had, v0.9.1 and it does not have the issue.
Same issue on Windows 10 22H2, exactly as demonstrated in the video. I'd revert to an older version but unfortunately (as far as I'm aware) CuNNy is not available on older builds.
I use two horizontal monitors, one 1920x1080 60fps and the other 2560x1440 165fps. Scaling the cursor the same as the window and adjusting cursor speed seemed to help reduce the bug, but it still happens. It happens most frequently close to the border between the two monitors and when the cursor is moving particularly fast. In my case, it jumps to the left side of the left monitor (the 1080p one). Wish this could be adressed as it's particularly annoying when mining visual novels and I need to move the cursor between the two windows very often.
Also have this issue
I also get this on Windows 11 24H2 with version 0.11.1. I went back and tried 0.10.4, and I wasn't able to repro with that version (but the graphics capture is pretty laggy)