Continuous Grab occasionally jumping when going across region border at high mouse polling rate #75528

Closed
opened 2020-04-08 14:24:29 +02:00 by Floatharr · 38 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.74

Blender Version
Broken: version: 2.83 (sub 13), branch: master, commit date: 2020-04-08 10:43, hash: ea5a2efb57
(broken since at least 2.6x, as long as I've used Blender)

Short description of error
With continuous grab enabled and mouse set to a high polling rate, the view occasionally jumps looping over the region border. At 1000hz it renders continuous grab nearly ununsable, and I can't reproduce at all at 125hz. Supposedly doesn't happen on Linux. Tested both on my main 144hz monitor and secondary 60hz, problem seems to be only related to mouse polling rate.

Exact steps for others to reproduce the error

  1. Set mouse polling rate to 1000hz. If you cannot adjust the polling rate, don't expect to be able to reproduce.
  2. Open the shading tab
  3. Pan the node area with MMB
  4. Quickly wiggle the mouse so that it crosses the border and loops back around

See video:

HHhX8reola.mp4

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.74 **Blender Version** Broken: version: 2.83 (sub 13), branch: master, commit date: 2020-04-08 10:43, hash: `ea5a2efb57` (broken since at least 2.6x, as long as I've used Blender) **Short description of error** With continuous grab enabled and mouse set to a high polling rate, the view occasionally jumps looping over the region border. At 1000hz it renders continuous grab nearly ununsable, and I can't reproduce at all at 125hz. Supposedly doesn't happen on Linux. Tested both on my main 144hz monitor and secondary 60hz, problem seems to be only related to mouse polling rate. **Exact steps for others to reproduce the error** 1. Set mouse polling rate to 1000hz. If you cannot adjust the polling rate, don't expect to be able to reproduce. 2. Open the shading tab 3. Pan the node area with MMB 4. Quickly wiggle the mouse so that it crosses the border and loops back around See video: [HHhX8reola.mp4](https://archive.blender.org/developer/F8456648/HHhX8reola.mp4)
Author

Added subscriber: @Floatharr

Added subscriber: @Floatharr

#96863 was marked as duplicate of this issue

#96863 was marked as duplicate of this issue

#92831 was marked as duplicate of this issue

#92831 was marked as duplicate of this issue
Author

The walk/fly navigation also likes to drift and jump around at high mouse polling rates, so I would assume this is a broader issue with how mouse input is handled in blender. I've recorded a video comparison of 125hz vs 1000hz: HDnB2pYWHH.mp4

The walk/fly navigation also likes to drift and jump around at high mouse polling rates, so I would assume this is a broader issue with how mouse input is handled in blender. I've recorded a video comparison of 125hz vs 1000hz: [HDnB2pYWHH.mp4](https://archive.blender.org/developer/F8456668/HDnB2pYWHH.mp4)

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

Added subscriber: @PrototypeNM1

Added subscriber: @PrototypeNM1

This may be improved with D9981.

This may be improved with [D9981](https://archive.blender.org/developer/D9981).

Added subscriber: @Pathogen

Added subscriber: @Pathogen

Added subscriber: @Aumnescio

Added subscriber: @Aumnescio

This happens to me constantly, and is an immense annoyance.
When rotating view, panning view, moving objects, scaling objects, or dragging any field values.

It is not limited to the shading panel. The jumping issue happens practically everywhere.
3D viewport, as well as all 2D views. All draggable fields' values: location, rotation, scale, and modifier values like bevel amount, displace amount, etc.

Confirmed that I still have this issue on Blender 2.93 beta, fresh install. (As well as 2.9, 2.91, 2.92)
And high polling rate mice seem to make it happen more often, but it still happens even with 125hz polling rate for me.

I would really like if this was pushed up in priority a little bit. It is a multiple year old issue by now.

A couple additional video examples:

2021-04-30 13-32-22.mp4

2021-04-30 15-04-26.mp4

2021-04-30 15-05-37.mp4

2021-04-30 15-10-28.mp4

This happens to me constantly, and is an immense annoyance. When rotating view, panning view, moving objects, scaling objects, or dragging any field values. It is not limited to the shading panel. The jumping issue happens practically everywhere. 3D viewport, as well as all 2D views. All draggable fields' values: location, rotation, scale, and modifier values like bevel amount, displace amount, etc. Confirmed that I still have this issue on Blender 2.93 beta, fresh install. (As well as 2.9, 2.91, 2.92) And high polling rate mice seem to make it happen more often, but it still happens even with 125hz polling rate for me. I would really like if this was pushed up in priority a little bit. It is a multiple year old issue by now. A couple additional video examples: [2021-04-30 13-32-22.mp4](https://archive.blender.org/developer/F10046800/2021-04-30_13-32-22.mp4) [2021-04-30 15-04-26.mp4](https://archive.blender.org/developer/F10046801/2021-04-30_15-04-26.mp4) [2021-04-30 15-05-37.mp4](https://archive.blender.org/developer/F10046802/2021-04-30_15-05-37.mp4) [2021-04-30 15-10-28.mp4](https://archive.blender.org/developer/F10046803/2021-04-30_15-10-28.mp4)

Added subscriber: @AgentSam-2

Added subscriber: @AgentSam-2

Added subscriber: @CookItOff

Added subscriber: @CookItOff

This is resolved on the latest Intel MacOS versions but is still an issues on the ARM64 builds.
Bug report #88386

This is resolved on the latest Intel MacOS versions but is still an issues on the ARM64 builds. Bug report #88386

Added subscriber: @Zcyber

Added subscriber: @Zcyber

it happens to me too. I am using 4 monitors and If I move object and move mouse cursor to other monitors with continuous grab on, transform values glitched. it's so annoying and I've just realized it's caused by continuous grab. It took me 7 months to find the culprit.

it happens to me too. I am using 4 monitors and If I move object and move mouse cursor to other monitors with continuous grab on, transform values glitched. it's so annoying and I've just realized it's caused by continuous grab. It took me 7 months to find the culprit.

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Confirmed' to: 'Needs User Info'

Changed status from 'Confirmed' to: 'Needs User Info'

I can't reproduce this problem anymore, so did d5c59913de fix it?
Can anyone else confirm that the issue has been resolved?

I can't reproduce this problem anymore, so did d5c59913de fix it? Can anyone else confirm that the issue has been resolved?

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'

This issue isn't resolved, just less likely to occur. The core issue is that mouse moves prior to cursor warp are still in the queue which causes the double accumulation. Fixing this is involved as SetCursorPos is unreliable.

I have fix (investigated as part of D12408) for this but haven't pushed it.

A proper fix would touch the mouse accum logic for Windows, macOS, and Linux. I don't think it's a good candidate for 3.0.

This issue isn't resolved, just less likely to occur. The core issue is that mouse moves prior to cursor warp are still in the queue which causes the double accumulation. Fixing this is involved as SetCursorPos is unreliable. I have fix (investigated as part of [D12408](https://archive.blender.org/developer/D12408)) for this but haven't pushed it. A proper fix would touch the mouse accum logic for Windows, macOS, and Linux. I don't think it's a good candidate for 3.0.

@mano-wii it's resolved on the ARM version of Blender. I started a bug report 6-ish months ago and it was resolved soon after; haven't had it happen since. Maybe the steps taken to resolve it on the ARM version will help here?

@mano-wii it's resolved on the ARM version of Blender. I started a bug report 6-ish months ago and it was resolved soon after; haven't had it happen since. Maybe the steps taken to resolve it on the ARM version will help here?
Member

Added subscribers: @LazyDodo, @lichtwerk, @PratikPB2123

Added subscribers: @LazyDodo, @lichtwerk, @PratikPB2123

Added subscriber: @lictex_1

Added subscriber: @lictex_1

Added subscriber: @joachip

Added subscriber: @joachip

This happens to me on Windows 10 on three different computers with three different brands of mice. I'm just using the standard mouse driver that comes with Windows, so I don't have any way of setting the polling rate that I'm aware of. I have disabled mouse acceleration.

It doesn't seem to have anything to do with window borders, nor having multiple monitors attached.

It happens everywhere in Blender when dragging or moving things around or adjusting values. I remember this from Blender 2.8x and 2.9x and it als happens in Blender 3.0

This happens to me on Windows 10 on three different computers with three different brands of mice. I'm just using the standard mouse driver that comes with Windows, so I don't have any way of setting the polling rate that I'm aware of. I have disabled mouse acceleration. It doesn't seem to have anything to do with window borders, nor having multiple monitors attached. It happens everywhere in Blender when dragging or moving things around or adjusting values. I remember this from Blender 2.8x and 2.9x and it als happens in Blender 3.0

I've tested several versions from 2.83, 2.9x, 3.0 and now 3.1, and I've made a video. I also had someone on the Blender VFX discord recreate the problem on his own computer.

https://www.youtube.com/watch?v=0v8r3GRYjEk

Basically happens often on every single installation of Blender I've ever tried.

I've tested several versions from 2.83, 2.9x, 3.0 and now 3.1, and I've made a video. I also had someone on the Blender VFX discord recreate the problem on his own computer. https://www.youtube.com/watch?v=0v8r3GRYjEk Basically happens often on every single installation of Blender I've ever tried.

Added subscriber: @cheteron

Added subscriber: @cheteron

This problem stretches from the version 2.8+. In version 2.79 there is no such problem!
For pen tablet - same problem

This problem stretches from the version 2.8+. In version 2.79 there is no such problem! For pen tablet - same problem

@cheteron I just took a look at the differences between 2.79 and 2.8+ and there was no obvious changes which would suggest a fix. I think this is just an issue of a difference in timing (from unrelated code) made a bug appear more readily. Even Unity has this cursor wrap bug, if you try to recreate it hard enough.

I have a prototype to fix this. The fix is to not accumulate until we can verify the cursor wrap has taken affect. This doesn't work as well for tablet input (both WM_POINTER and Wintab cursor movement input streams are asynchronous with general cursor movement). It's also not a 100% fix for mouse input, but it drastically decreases the issue (repeat accumulation before cursor position updates).

@cheteron I just took a look at the differences between 2.79 and 2.8+ and there was no obvious changes which would suggest a fix. I think this is just an issue of a difference in timing (from unrelated code) made a bug appear more readily. Even Unity has this cursor wrap bug, if you try to recreate it hard enough. I have a prototype to fix this. The fix is to not accumulate until we can verify the cursor wrap has taken affect. This doesn't work as well for tablet input (both WM_POINTER and Wintab cursor movement input streams are asynchronous with general cursor movement). It's also not a 100% fix for mouse input, but it drastically decreases the issue (repeat accumulation before cursor position updates).
Nicholas Rishel self-assigned this 2022-05-01 07:05:07 +02:00

I don't know what are the differences in the code, but this is the problem now

I don't know what are the differences in the code, but this is the problem now

In #75528#1349670, @cheteron wrote:
I don't know what are the differences in the code, but this is the problem now

Was just commenting with an @ to you so anyone reading would have the context and to document what I found. No follow up necessary on your part. :)

> In #75528#1349670, @cheteron wrote: > I don't know what are the differences in the code, but this is the problem now Was just commenting with an @ to you so anyone reading would have the context and to document what I found. No follow up necessary on your part. :)

Unity does indeed have a similar issue, but it only happens on very rare occasions. And as far as I've observed, it happens when the pointer hits the edge of the screen and wraps around.

In Blender it can happen even if the pointer starts at the middle of the screen, and I don't move the mouse far enough to bring close to the edges. So I don't think it's related to hitting the edge of the monitor in Blender's case.

Bonus info: I've recently tried a colleague's computer. I was immediately able to reproduce it, leaving him somewhat confused that he had never noticed this before.

Unity does indeed have a similar issue, but it only happens on very rare occasions. And as far as I've observed, it happens when the pointer hits the edge of the screen and wraps around. In Blender it can happen even if the pointer starts at the middle of the screen, and I don't move the mouse far enough to bring close to the edges. So I don't think it's related to hitting the edge of the monitor in Blender's case. Bonus info: I've recently tried a colleague's computer. I was immediately able to reproduce it, leaving him somewhat confused that he had never noticed this before.

Added subscriber: @jkinzel

Added subscriber: @jkinzel

Hello, everyone! I'm not super active in the developer space but is there any progress on this bug? This occurs with all mouse wrapping in Blender (sliders, node graphs, etc) and occurs nearly every time on every computer i've used blender on. It's seriously one of the most irritating things with blender and i'd argue that this should be moved to a higher priority.

Hello, everyone! I'm not super active in the developer space but is there any progress on this bug? This occurs with all mouse wrapping in Blender (sliders, node graphs, etc) and occurs nearly every time on every computer i've used blender on. It's seriously one of the most irritating things with blender and i'd argue that this should be moved to a higher priority.
Symilate commented 2022-06-20 08:31:43 +02:00 (Migrated from localhost:3001)

Added subscriber: @Symilate

Added subscriber: @Symilate

Added subscriber: @Burhursta

Added subscriber: @Burhursta

To me (2.93,9, Windows 10), the issue persists no matter what polling rate I set it to (I've tested it out on later versions of Blender and it does still happen in the exact same way, in 3.2.1 I've booted to test this while writing this, and it still happens the same way). I've tested it at many different Windows mouse sensitivity levels, polling rates, different DPI rates, it doesn't seem to have any workaround. I've even changed my mouse (Steelseries Rival 300) for an old cheap mouse (AULA KILLING THE SOUL BEHEAD), and it still happens. In my perspective, it seems to happen more often on low Windows sensitivity+low polling rate, but I can't say for certain.

This happens on both my 144hz monitor and my 60hz monitor.

Personally, this also happens on 2.79b, for me. 2022-08-04 06-20-55.mp4

I've also tried 2.70a, and it still does this. It seems to be less often to me, though.2022-08-04 06-34-30.mp4

To me (2.93,9, Windows 10), the issue persists no matter what polling rate I set it to (I've tested it out on later versions of Blender and it does still happen in the exact same way, in 3.2.1 I've booted to test this while writing this, and it still happens the same way). I've tested it at many different Windows mouse sensitivity levels, polling rates, different DPI rates, it doesn't seem to have any workaround. I've even changed my mouse (Steelseries Rival 300) for an old cheap mouse (AULA KILLING THE SOUL BEHEAD), and it still happens. In my perspective, it seems to happen more often on low Windows sensitivity+low polling rate, but I can't say for certain. This happens on both my 144hz monitor and my 60hz monitor. Personally, this also happens on 2.79b, for me. [2022-08-04 06-20-55.mp4](https://archive.blender.org/developer/F13336078/2022-08-04_06-20-55.mp4) I've also tried 2.70a, and it still does this. It *seems* to be less often to me, though.[2022-08-04 06-34-30.mp4](https://archive.blender.org/developer/F13336095/2022-08-04_06-34-30.mp4)

Closed as duplicate of #89399

Closed as duplicate of #89399
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
15 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#75528
No description provided.