https://bugs.kde.org/show_bug.cgi?id=489657
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #20 from [email protected] --- Reproduced Conclusions: I did some iterations and realised that in case the pointer acceleration is on, the problem seems to be related to which monitor is detected first. If you move the cursor from the 1st detected monitor to the 2nd detected monitor, the barrier comes up, but does not come up when moving from the 2nd detected monitor to the 1st detected monitor. I used 2 different mice for the 1st 2 iterations (both mice for 2 iterations each, not one or the other), but when I realised they were giving similar results, just stuck with one. These 2 mice were Steelseries gaming mice, with DPIs > 5000. After the 6th iteration, I tried a Dell Wireless mouse (with "normal" DPI) to get similar results. Then I turned off pointer acceleration (speed still -1) and the bug appeared in both directions regardless of which monitor was detected first. Following is the iterations I tried: - D1 and D2 are 2 separate physical monitors, both 1920x1080. D1 has 100Hz capability. - portA and portB are the 2 ports on the GPU I connected those monitors to, both DisplayPort™ ____ 1 ____ Settings: Left monitor [D1-portA] - Res: 1920x1080 Refresh: 100Hz Scaling: 100% [Set as default monitor] Right monitor [D2-portB] - Res: 1920x1080 Refresh: 60Hz Scaling: 100% Mouse - Speed: -1 Acceleration: Enabled Edge barrier: None Observation: The perceived edge barrier only happens when moving from the Left monitor to Right monitor. When moving from the right to the left one, no barrier is perceived. ____ 2 ____ Settings: Right monitor [D1-portA] - Res: 1920x1080 Refresh: 100Hz Scaling: 100% [Set as default monitor] Left monitor [D2-portB] - Res: 1920x1080 Refresh: 60Hz Scaling: 100% Mouse - Speed: -1 Acceleration: Enabled Edge barrier: None Observation: The perceived edge barrier only happens when moving from the Right monitor to Left monitor. ____ 3 ____ Swapped ports while the computer was running Inserted D2 first and D1 second Settings: Left monitor [D1-portB] - Res: 1920x1080 Refresh: 60Hz/100Hz (tried both) Scaling: 100% Right monitor [D2-portA] - Res: 1920x1080 Refresh: 60Hz Scaling: 100% Mouse - Speed: -1 Acceleration: Enabled Edge barrier: None Observation: The perceived edge barrier only happens when moving from the Right monitor to Left monitor. ____ 4 ____ Settings: Right monitor [D1-portB] - Res: 1920x1080 Refresh: 60Hz Scaling: 100% Left monitor [D2-portA] - Res: 1920x1080 Refresh: 60Hz Scaling: 100% Mouse - Speed: -1 Acceleration: Enabled Edge barrier: None Observation: The perceived edge barrier only happens when moving from the Left monitor to Right monitor. ____ 5 ____ Took out D2 and put it back in Settings: Right monitor [D1-portB] - Res: 1920x1080 Refresh: 100Hz Scaling: 100% Left monitor [D2-portA] - Res: 1920x1080 Refresh: 60Hz Scaling: 100% Mouse - Speed: -1 Acceleration: Enabled Edge barrier: None Observation: The perceived edge barrier only happens when moving from the Right monitor to Left monitor. ____ 6 ____ Live Swapped ports again Inserted D2 first Settings: Left monitor [D1-portB] - Res: 1920x1080 Refresh: 100Hz Scaling: 100% Right monitor [D2-portA] - Res: 1920x1080 Refresh: 60Hz Scaling: 100% Mouse - Speed: -1 Acceleration: Enabled Edge barrier: None Observation: The perceived edge barrier only happens when moving from the Right monitor to Left monitor. ____ Removed tag for "default monitor" because I tested setting either of them as default in all conditions Finally saying, I tested these under very slow conditions thanks to the -1 pointer speed. The fastest I was getting with acceleration off, was 2mm per pixel-on-screen and the Dell one was 5mm per pixel on screen, which I then purposefully moved slowly. This caused a greater amount of up/down movement per right/left movement which might matter depending upon the transfer function used. Either way, the barrier was set to "None", so the relevant transfer function should not have been invoked in the first place. -- You are receiving this mail because: You are watching all bug changes.
