<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Blender viewport "goes crazy" when mouse reaches viewport window edge in fly mode (Shift+F) or moving object (G)" href="https://bugs.freedesktop.org/show_bug.cgi?id=100740#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Blender viewport "goes crazy" when mouse reaches viewport window edge in fly mode (Shift+F) or moving object (G)" href="https://bugs.freedesktop.org/show_bug.cgi?id=100740">bug 100740</a> from <a class="email" href="mailto:jesse.dubord@gmail.com" title="Source0f1 <jesse.dubord@gmail.com>"> Source0f1</a> <pre>(In reply to Jonas Ådahl from <a href="show_bug.cgi?id=100740#c16">comment #16</a>) > (In reply to Source0f1 from <a href="show_bug.cgi?id=100740#c15">comment #15</a>) > > Did something change? I just tested Blender, today, on Ubuntu 17.10 beta 2 > > (ubuntu-modified gnome shell under wayland) and issue #1 appears to be > > fixed: pressing shift+f to enter fly mode and move around the scene no > > longer causes the camera to behave sporadically and it moves like it does in > > Xorg. Issues #2 and #3 still exist, however. > > > > Still, progress is progress! > > Given the methods we have under Wayland (pointer locking and confinement > instead of clients directly controlling the pointer cursor) we have > implemented various support for emulating the X11 ways of implementing those > features (locking/confinement). What Blender does however is taking control > of the mouse cursor (without hiding it) and then moving it around on the > screen (you'll see that it suddenly warps when hitting some edge in the UI). > > This is the known remaining issue, and we cannot really solve it without > going back to giving clients arbitrary control of the pointer cursor. > Therefore we opened a bug on Blender about this issue, arguing that the > issue would best be mitigated in Blender. > > The bug was swiftly closed as wont-fix however, and the recommended work > around is to disable the warp functionality. See > <a href="https://developer.blender.org/T53004">https://developer.blender.org/T53004</a> for more details. Thanks for the update. I also wrote a comment in the Blender bug you linked, hoping greater collaboration could be done to find a more seamless solution than "turn off a setting in User Preferences to restore basic functionality for all Wayland/XWayland users". With Wayland/Xwayland becoming default for many, that would seem like a sore inconvenience for Blender users, everywhere.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>