Cursor lock bug crossig between specific monitors

[NeonGrayX]

Hello,

I have three monitors set up in a triangle, all 27" with different resolutions. I noticed a bug when trying to cross between the top and bottom left screens. When coming from the top, the cursor will lock at the left edge of the top screen without crossing to the bottom. Pressing the Windows button or tabbing to a different application will release it again. Similarly, when moving from the bottom left screen to the top, the mouse will lock on the bottom screen on a line about a quarter into the screen from the right. All other crossings work as expected, and I also tried both loop directions, which have the same issue at the same border and work flawlessly everywhere else.

Here's a screen capture showing the issue with the monitors set up to scale, and the LittleBigMouse setup is shown for reference.

Mouse.behaviounr.mp4

[krudkutter]

I am currently having the same issue. Did you ever come across a solution?

[NeonGrayX]

I am currently having the same issue. Did you ever come across a solution?

Unfortunately, I haven’t found a solution yet. However, I did manage to get the same monitors to work when connected via a docking station to my laptop. It appears that this issue might be related to specific hardware setups.

[ArchiusPendragon]

Similarly, experiencing this issue; both monitors are leftmost, same resolution; connected via a splitter.
Crossing monitors is iGPU of Ryzen 7950X and a 7900XTX GPU for outputs works fine, it is specifically going from the bottom monitor to the top monitor - crossing all other monitors operates as expected.

Layout is currently in an
XY
XZX
Configuration - X monitors are 1600x900 monitors, and on splitter, Y is 1080P monitor, Z is a 1440p monitor.

[bigboss9191]

Same issue. Just re-built computer. On old PC it worked fine, but I downloaded the newest version of LBM and it is doing this now.

[bigboss9191]

I think I fixed it. Because I was using little big mouse, I left my monitors in Windows display settings in disarray. After I corrected these to be more accurate the issue went away.

[NeonGrayX]

I could fix it through Windows display settings now as well, but instead of correcting it, I had to change it to something different from my actual setup. I also tried some other layouts in Windows, and it seems that some of them, with misaligned monitors, cause this exact problem. However, aligning them always fixed it, regardless of how else they were set up.

Before (non working):

After (working):

[iantrudell]

I am having the same issue, two same resolution, same size monitors stacked vertically on the far left, 3 other displays to the right. I can move between everything except vertically between the two left-most. When I try, the cursor immediately goes to the far left edge and gets stuck.

One of those two monitors uses DisplayLink over USB to bypass my video card's 4 display limit.

In the image, moving the cursor between the two monitors where the red line is snaps the cursor to the far left edge and prevents me from moving the cursor in the x axis.

Monitor 5 is the DisplayLink monitor (USB to DisplayPort)

[OGJakearroo]

This..... is insane.
I had the same problem and seeing @MesserschmittX's response I moved the displays around in windows and it.... works now.
Ive just slightly offset it so when LBM crashes or stops working its not unlivable, but thats kinda insane

[iantrudell]

Any updates on what might be causing this, or a potential workaround for now?

[mgth]

👋 LittleBigMouse 5.3.0-beta.1 is out and should fix this.

The v5 engine had four bugs causing the cursor to get stuck at certain screen edges until Alt-Tab: a coordinate mix-up when clamping the cursor into a screen zone, transition rectangles built with a wrong width, a randomly-initialized border resistance, and layout options (loops, max travel distance) applied after the zone links were computed. All identified thanks to #460 and fixed in #466.

⚠️ The beta requires the .NET 10 Desktop Runtime (x64) — install it first if the app doesn't start.

Could you give it a try and report back? If the problem is gone, this issue will be closed with the stable release.

[NeonGrayX]

I tried the Version and i did not encounter the same issue as before. It does now seem to be fixed with this.