https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #47 from bugzilla@biechl.net --- (In reply to bugzilla from comment #46)
Created attachment 59398 [details] Cursor trace of Fallout4
wine2.8+staging WINEDEBUG=-all,+event,+cursor for upper part, WINEDEBUG=-all,+dinput,+cursor for lower Game in fullscreen (1280x720) Xubuntu 16.04 AMD R290X using Mesa 17.2.2-0 (padoka stable repo) 3 Monitors (no difference in the logs, when I deactivate 2 of them within the OS) No DLL overrides
I don't think this bug is related to Fallout4 - we might need to file a new bug report - but I'll leave this here for now:
I don't know much about the internals of wine and windows, but I've tried to trace the problem a bit, here is what I've come up with:
see attachment: fallout4_cursor-trace.log - Part 1
In the last 4 lines there is again a rather big jump on the x-axis: from 183 to 0. Prior to the jump there is a ConfigureNotify, which isn't there in the previous lines. Also the event id changed from 4449 to 4450. I can see this all over my logs when I'm in 3D camera mode. This does not occur when being in any sort menu.
Also there is something strange with the clipping, don't know if this is normal or not: (WINEDEBUG=-all,+dinput,+cursor), different log.
see attachment: fallout4_cursor-trace.log - Part 2
It first clips with the correct window size (1280,720), then it does another clipping, but with a different window size. "trace:cursor:grab_clipping_window Clip window shrinked" is an added debug output by me, as well as " | clip_rect: (X,Y)-(X2,Y2)".
I'll do a full trace later this day, but this might be of help already?