Cursor gets stuck in the middle of 3rd Monitor + Wrong resolution

[PantheonOfSol]

Setup: 3 4k monitors, a 32" on the right and 2 27" on the left, stacked horizontally. 32" is monitor 1, the bottom 27" is monitor 2, and the top is monitor 3.

Current problematic behavior: When trying to use Monitor 3 if the cursor moves more than halfway to the left, or top, or tries to go down to Monitor 2 it will get stuck and only be able to move vertically, and will keep moving on its own randomly. It's possible to gain control of the mouse back by switching to a different app. It's actually made the app unusable.
Monitor 3 also reports 1080p

I did go from using a DP>HDMI adapter that didn't do 4k to just using DP, I'm guessing that caused some kind of issue.

Undoing all the changes does nothing, nor does restarting the system.

Expected Behavior: Correctly detect monitor resolution, cursor should move smoothly across all monitors

Here's the config:
LittleBigMouse.Export.gz

lmk what other information we can provide, this app is dope and we really appreciate the hard work yall are puttin in.

[hink0001]

I experience similar situation with the following config:

24" 1080p (DP)	27" 2K (DP, primary)
13" 4K (HDMI)

Moving the cursor to the third monitor (13" 4K) will cause the cursor to stuck on the edge and only the vertical movement is allowed.
I found a workaround by setting the third monitor as primary and the cursor will work as expected. Then I configured the primary back to the original monitor, the issue disappears with the original config, even restarting the LBM serivce.

[PantheonOfSol]

Thanks for the response! I’ll try this out (hopefully) today On Jun 24, 2024, at 10:32 AM, hink0001 ***@***.***> wrote: I experience similar situation with the following config: 24" 1080p (DP) 27" 2K (DP, primary) 13" 4K (HDMI) Moving the cursor to the third monitor (13" 4K) will cause the cursor to stuck on the edge and only the vertical movement is allowed. I found a workaround by setting the third monitor as primary and the cursor will work as expected. Then I configured the primary back to the original monitor, the issue disappears with the original config, even restarting the LBM serivce. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[FWest98]

#325

Same issue as this one; for me it was resolved by making sure that in Windows each monitor does not touch more than one other monitor on each side, as explained in the other thread.