Regression: Pen tablet navigation and continuous drag produces eternal rotation #89928

Closed
opened 2021-07-18 02:12:21 +02:00 by Vyacheslav Kobozev · 24 comments

System Information
Operating system: Windows-8.1-6.3.9600-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47

Blender Version
Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c
Worked: 2.79

Short description of error
As title says.

2021-07-18_03-05-01.mp4

2.79 just disable continuous drag for pen and all work fine. And this what I expect from pen with absolute cordinates.
2021-07-18_03-10-52.mp4

**System Information** Operating system: Windows-8.1-6.3.9600-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47 **Blender Version** Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: `1b8d33b18c` Worked: 2.79 **Short description of error** As title says. [2021-07-18_03-05-01.mp4](https://archive.blender.org/developer/F10226878/2021-07-18_03-05-01.mp4) 2.79 just disable continuous drag for pen and all work fine. And this what I expect from pen with absolute cordinates. [2021-07-18_03-10-52.mp4](https://archive.blender.org/developer/F10226883/2021-07-18_03-10-52.mp4)

Added subscriber: @Vyach

Added subscriber: @Vyach

Added subscribers: @PratikPB2123, @lichtwerk

Added subscribers: @PratikPB2123, @lichtwerk

This comment was removed by @Vyach

*This comment was removed by @Vyach*

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

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

Removed subscribers: @lichtwerk, @PratikPB2123, @Vyach

Removed subscribers: @lichtwerk, @PratikPB2123, @Vyach
Member

Added subscriber: @Vyach

Added subscriber: @Vyach
Member

Hi @Vyach , does the issue happen with 2.93.2 and not in 3.0.0? In that case you can reopen the ticket.

I don't have similar system to test the issue, may be Philipp Oeser has the wacom tablet.

Hi @Vyach , does the issue happen with 2.93.2 and not in 3.0.0? In that case you can reopen the ticket. I don't have similar system to test the issue, may be Philipp Oeser has the wacom tablet.

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123

@PratikPB2123 Yes, correct. Please reopen. Still not fixed for 2.93.2

Also I made new report for walk navigation. May be it is related too #90491 (Walk navigation with pen tablet fails in 2.93.2 (continous rotation))

@PratikPB2123 Yes, correct. Please reopen. Still not fixed for 2.93.2 Also I made new report for walk navigation. May be it is related too #90491 (Walk navigation with pen tablet fails in 2.93.2 (continous rotation))
Member

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

Changed status from 'Archived' to: 'Needs Triage'
Member

Added subscriber: @PrototypeNM1

Added subscriber: @PrototypeNM1
Member

Hi @PrototypeNM1 , can you replicate the issue on 2.93.2?

Hi @PrototypeNM1 , can you replicate the issue on 2.93.2?

#90491 won't be related as walk navigation uses a different mechanism.

Continuous grab is disabled if an operator starts while a tablet is present. I'd bet to trigger this 1. the pen must not be in range of the tablet when the operator starts (e.g. when g is pressed) and 2. the tablet API is set to Automatic or Wintab. This issue wouldn't be present in 3.0 due to the Wintab rewrite.

#90491 won't be related as walk navigation uses a different mechanism. Continuous grab is disabled if an operator starts while a tablet is present. I'd bet to trigger this 1. the pen must not be in range of the tablet when the operator starts (e.g. when `g` is pressed) and 2. the tablet API is set to Automatic or Wintab. This issue wouldn't be present in 3.0 due to the Wintab rewrite.
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

Not sure how to proceed here.
@PrototypeNM1 : do you think there is a chance of isolation some commit from the Wintab rewrite that could still fix this in 2.93 LTS?

Not sure how to proceed here. @PrototypeNM1 : do you think there is a chance of isolation some commit from the Wintab rewrite that could still fix this in 2.93 LTS?

oh, here this old report. Still actual sadly

oh, here this old report. Still actual sadly

@Vyach Could you check if the issue occurs if the pen is in range of the tablet before grabbing/rotating?

@Vyach Could you check if the issue occurs if the pen is in range of the tablet before grabbing/rotating?

In #89928#1249333, @PrototypeNM1 wrote:
@Vyach Could you check if the issue occurs if the pen is in range of the tablet before grabbing/rotating?

Tablet have absolute cordinates, so if mouse curson in the range of screen, it means the pen in the range of tablet.
An yes, it is. In the rangeof drawing area and in height range too

(I hope, I understand your question correct)
For me, as a user, it loks like issue appears just because pen continuously set same position of cursor but blender tries to set another one (as for mouse, on the other side of viewport).
in "mouse mode" (relative cordinates) for tablet there is no bug.
2021-11-07_06-47-59.mp4

Also ask Simon Tommes, he had same issue on the stream (with pizza) and i suppose, he use touchpad or pen.

> In #89928#1249333, @PrototypeNM1 wrote: > @Vyach Could you check if the issue occurs if the pen is in range of the tablet before grabbing/rotating? Tablet have absolute cordinates, so if mouse curson in the range of screen, it means the pen in the range of tablet. An yes, it is. In the rangeof drawing area and in height range too (I hope, I understand your question correct) For me, as a user, it loks like issue appears just because pen continuously set same position of cursor but blender tries to set another one (as for mouse, on the other side of viewport). in "mouse mode" (relative cordinates) for tablet there is no bug. [2021-11-07_06-47-59.mp4](https://archive.blender.org/developer/F11755616/2021-11-07_06-47-59.mp4) Also ask Simon Tommes, he had same issue on the stream (with pizza) and i suppose, he use touchpad or pen.

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk

@lichtwerk to fix this window->m_tabletInRange would need to be updated during WT_PROXIMITY (2.93) events. You can reference the changes in 3.0 for in vs out of range. Note that 2.93's WT_CRSCHANGE falls through to WT_PROXIMITY, so the two would need to be decoupled or the WT_PROXIMITY handling moved before the fall through.

Because of changes in 3.0 this issue shouldn't be present.

@lichtwerk to fix this `window->m_tabletInRange` would need to be updated during [WT_PROXIMITY (2.93)](https:*developer.blender.org/diffusion/B/browse/blender-v2.93-release/intern/ghost/intern/GHOST_SystemWin32.cpp$1471) events. You can reference the [changes in 3.0](https:*developer.blender.org/diffusion/B/browse/master/intern/ghost/intern/GHOST_SystemWin32.cpp$1606) for in vs out of range. Note that 2.93's WT_CRSCHANGE falls through to WT_PROXIMITY, so the two would need to be decoupled or the WT_PROXIMITY handling moved before the fall through. Because of changes in 3.0 this issue shouldn't be present.
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar
Member

I can't reproduce this issue anymore in master. Is this still an issue or can this be closed?

I can't reproduce this issue anymore in master. Is this still an issue or can this be closed?

@JulienKaspar
Also not reproducible for me in:
3.3.0 Beta, c9a996790307, 2022-08-19 20:22
3.4.0 Alpha, branch: master, commit date: 2022-08-20 00:16, hash: acf083a5bf
So can be closed

@JulienKaspar Also not reproducible for me in: 3.3.0 Beta, `c9a996790307`, 2022-08-19 20:22 3.4.0 Alpha, branch: master, commit date: 2022-08-20 00:16, hash: `acf083a5bf` So can be closed
Member

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Pratik Borhade self-assigned this 2022-08-24 08:12:51 +02:00
Pratik Borhade removed their assignment 2022-08-24 08:13:01 +02:00
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
5 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#89928
No description provided.