Noticed in the last couple beta versions the cursor jumps at a certain pixel count. Running dual display, the issue only occurs on the secondary monitor which has the Windows taskbar.

Open the gif attached, it displays what happens while moving the cursor over the windows taskbar on the secondary monitor. When the cursor reaches a certain pixel depth (horizontal) the cursor jumps down nearly 20px. It only occurs while DF is running.

Though, I just now reinstalled DF beta4 and unable to replicate the issue. If it occurs again I'll try capturing a better view. I'm sure this has to do with DF and HiDPI res.

Captured a better shot, though I wasn't able to preserve the mouse-trailing after rendering the gif. Then again, I'm unsure what software is available to record and preserve mouse-trailing, It would provided a far better detailed view of the issue.

Edit: It could be something with the DF taskbar attempting to stretch over to the second display. That seems quite possible since we've seen issues with the DF taskbar stacking on top (or below) the Windows taskbar.

Additionally, the capture provided is from the secondary display with the Windows taskbar displaying. The primary monitor, partially visible to the left, is running the DF taskbar. I've provided a detailed log.

Another view using MS Paint tracking cursor.

Yep, disabling that feature seems to have resolved the issue. Will try it out for a few days.

Can you define "listing really weird screen resolutions" ?

I've used HiDPI for quite a while, the DSR factors are normal.

These are correct resolutions while using DSR scaling, it's been in all previous logs for a year. DSR = Dynamic Super Resolution (Nvidia). What you see in the log is correct, and displays the same within Windows Resolutions.

np. its quite new.nvidia released DSR in driver 322 a year or two ago, IIRC. The only problem I've had with it is Windows scaling and Microsoft and other software is lagging behind.

I'm curious about what caused the bug.

AND... it's back.

It's been for a while but I've been ignoring it until now. The initial post was regarding the bug in Windows 10, now that I went back to Windows 8.1 the same issue occurs. It seems that it only occurs when certain applications are launched, I use an old, but powerful, browser Presto 12.15 and the cursor reacts the same as noted above. It also occurs with AutoCad.

disabling "Prevent mouse cursor from snagging" does not resolve the issue.

Issue is back. Almost certain it's due to the last DF update. Does not occur with all applications and I've been ignoring the issue, however, I installed Steam for some reason today and when Steam is maximized the OP issue occurs often. Exact location.

Time: 1514 - 1516

Exact location as noted in previous issue. This particular issue occured with steam.exe running in the foreground.

As previously mentioned in original post. Issue only happens while DF is running. I've created several extensive videos showing this. Also, I've looked through several log files and none make any reference to DF "moving" the mouse. I've spent several minutes moving the mouse and there is no log indicating anything. This is a display 'bounding box' graphical issue with DF, in relation to the windows 10 start menu. Additionally, the issue seams to only appear when applications written in C++ and/or Objective-C are running in the foreground.