Wacom tablet input doesn't work in "mouse mode" in 2.92.0 Alpha (Nov 25th build) #83041

Closed
opened 2020-11-26 10:03:05 +01:00 by Jeroen Backx · 23 comments

System Information
Operating system: Windows 10
Graphics card: Geforce 2070

Blender Version
Broken: 2.92 Alpha e09d0c0d07
Worked: 2.91

Short description of error
Using my Wacom tablet in "mouse mode" in Blender 2.92.0 Alpha seems to scale the input. It is difficult to explain but the video below demonstrates the issue.

This happens on a fresh system startup and only in Blender (no other software). It also doesn't matter whether I had it set to mouse-mode before or during Blender being active.

I had posted this video previously on a different ticket but I had not gotten a response then so I am trying again as this bug is not yet resolved. Thank you!

Exact steps for others to reproduce the error
See video below...
pen mouse mode input scaling issue.mp4

**System Information** Operating system: Windows 10 Graphics card: Geforce 2070 **Blender Version** Broken: 2.92 Alpha e09d0c0d077c Worked: 2.91 **Short description of error** Using my Wacom tablet in "mouse mode" in Blender 2.92.0 Alpha seems to scale the input. It is difficult to explain but the video below demonstrates the issue. This happens on a fresh system startup and only in Blender (no other software). It also doesn't matter whether I had it set to mouse-mode before or during Blender being active. I had posted this video previously on a different ticket but I had not gotten a response then so I am trying again as this bug is not yet resolved. Thank you! **Exact steps for others to reproduce the error** See video below... [pen mouse mode input scaling issue.mp4](https://archive.blender.org/developer/F9337488/pen_mouse_mode_input_scaling_issue.mp4)
Author

Added subscriber: @Grimreth

Added subscriber: @Grimreth

#84124 was marked as duplicate of this issue

#84124 was marked as duplicate of this issue

Closed as duplicate of #82775

Closed as duplicate of #82775

Added subscriber: @rjg

Added subscriber: @rjg

This comment was removed by @rjg

*This comment was removed by @rjg*

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

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

I'm re-opening the ticket as the issue is not the same, it has only has been discussed in the other ticket.

I'm re-opening the ticket as the issue is not the same, it has only has been discussed in the other ticket.

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

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

I can confirm the issue. Mouse mode causes an offset in the input. @PrototypeNM1

I can confirm the issue. Mouse mode causes an offset in the input. @PrototypeNM1

Added subscriber: @PrototypeNM1

Added subscriber: @PrototypeNM1
Nicholas Rishel self-assigned this 2020-11-27 03:47:27 +01:00
Author

Is there any progress on this issue? I am still unable to use my tablet in mouse mode in the latest builds of 2.92.

Thank you!

Is there any progress on this issue? I am still unable to use my tablet in mouse mode in the latest builds of 2.92. Thank you!

What's happening here is that Wintab is reporting absolute coordinates to Blender, but moving the mouse as though it was a relative mouse.

I spent a bit of time today trying to find a way to have Wintab inform when the system cursor is in mouse mode, but the APIs that seemed promising didn't actually work (or I don't know how to make them work).

On review GIMP, Krita, and MyPaint and found they all had the same problem (all use Wintab xy position directly, which Blender does too in 2.92).

All this is to say I'm not entirely sure the best way to proceed here. The changes in 2.92 are the only way to get high frequency tablet events for Wintab, and maintaining two versions of Wintab handling isn't a pleasant thought. I can force Wintab to handle the system cursor in absolute coordinates while Blender is active, effectively disabling mouse mode Wintab in Blender, but that's not a great solution either.

I'll have to think/research this a bit more.

What's happening here is that Wintab is reporting absolute coordinates to Blender, but moving the mouse as though it was a relative mouse. I spent a bit of time today trying to find a way to have Wintab inform when the system cursor is in mouse mode, but the APIs that seemed promising didn't actually work (or I don't know how to make them work). On review GIMP, Krita, and MyPaint and found they all had the same problem (all use Wintab xy position directly, which Blender does too in 2.92). All this is to say I'm not entirely sure the best way to proceed here. The changes in 2.92 are the only way to get high frequency tablet events for Wintab, and maintaining two versions of Wintab handling isn't a pleasant thought. I can force Wintab to handle the system cursor in absolute coordinates while Blender is active, effectively disabling mouse mode Wintab in Blender, but that's not a great solution either. I'll have to think/research this a bit more.

Added subscriber: @shaqualeek

Added subscriber: @shaqualeek

Quick update, I learned that relative input setup in Wintab API is not the same as mouse mode set in the driver preferences. Relative input modifies input reporting to offsets instead of absolute points. Mouse mode in the driver preferences does mousy things, like mouse acceleration. These two things looks similar but are incompatible.

Quick update, I learned that relative input setup in Wintab API is not the same as mouse mode set in the driver preferences. Relative input modifies input reporting to offsets instead of absolute points. Mouse mode in the driver preferences does mousy things, like mouse acceleration. These two things looks similar but are incompatible.
Author

@PrototypeNM1 Thank you very for your continued efforts in resolving the issue and your detailed feedback. I regularly check new builds and the issue still persists.

You didn't ask for it but I created another console log based on the latest build here: https:*blender.community/c/graphicall/Wlbbbc/
The log is here: https://developer.blender.org/P1875

I noticed you also asked other users to check Gimp for similar issues. I also did this and did not notice any issues there. I currently only experience the mouse-mode offset/scaling issue in blender.

I really hope this can be resolved as I depend on mouse-mode to comfortably work on multi-monitor setups. If there is anything I can do to help to resolve this issue please let me know.
Thank you again.

@PrototypeNM1 Thank you very for your continued efforts in resolving the issue and your detailed feedback. I regularly check new builds and the issue still persists. You didn't ask for it but I created another console log based on the latest build here: [https:*blender.community/c/graphicall/Wlbbbc/ ](https:*blender.community/c/graphicall/Wlbbbc/) The log is here: https://developer.blender.org/P1875 I noticed you also asked other users to check Gimp for similar issues. I also did this and did not notice any issues there. I currently *only* experience the mouse-mode offset/scaling issue in blender. I really hope this can be resolved as I depend on mouse-mode to comfortably work on multi-monitor setups. If there is anything I can do to help to resolve this issue please let me know. Thank you again.

@Grimreth could you verify that pressure is working correctly with a mouse mode tablet in GIMP?

@Grimreth could you verify that pressure is working correctly with a mouse mode tablet in GIMP?
Author

Thanks for getting back... As you probably suspected, I had not properly configured my input devices in GIMP. As a result everything seemed fine initially but upon re-evaluation it became clear that I did not have pressure sensitivity. Once I did properly configure my input devices in GIMP I encountered similar scaling/offset issues as Blender 2.92 onward.

I then became curious to see whether I would experience similar issues in Photoshop so I went and checked. As it turns out, yes, Photoshop 2020 and 2021 both demonstrate similar issues with scaling/offset in mouse mode. Other software such as Marmoset also experiences the issue. This of course indicates that it is an issue outside of blender.

It seems any interaction with any canvas or 3d viewport in Mouse-mode gets scaled/offset, whereas regular Windows UI has no issues. The only other place where I do not experience issues is Blender 2.91 and prior. This also was the cause of my assumption that it had something to do with Blender in the first place. Sorry about that, my mistake.

I updated once more to the latest Wacom drivers but that doesn't seem to help any. I will create a ticket over at the Wacom website as well, I hope someone over there will have some answers.

I am just left wondering why older Blender versions do not have this issue, do you have any idea?

Thanks for getting back... As you probably suspected, I had not properly configured my input devices in GIMP. As a result everything seemed fine initially but upon re-evaluation it became clear that I did not have pressure sensitivity. Once I did properly configure my input devices in GIMP I encountered similar scaling/offset issues as Blender 2.92 onward. I then became curious to see whether I would experience similar issues in Photoshop so I went and checked. As it turns out, yes, Photoshop 2020 and 2021 both demonstrate similar issues with scaling/offset in mouse mode. Other software such as Marmoset also experiences the issue. This of course indicates that it is an issue outside of blender. It seems any interaction with any canvas or 3d viewport in Mouse-mode gets scaled/offset, whereas regular Windows UI has no issues. The only other place where I do not experience issues is Blender 2.91 and prior. This also was the cause of my assumption that it had something to do with Blender in the first place. Sorry about that, my mistake. I updated once more to the latest Wacom drivers but that doesn't seem to help any. I will create a ticket over at the Wacom website as well, I hope someone over there will have some answers. I am just left wondering why older Blender versions do not have this issue, do you have any idea?

Older versions of Blender don't use the position reported by Wintab. It instead used Window's mouse position and the most recent Wintab pressure and tilt. This Frankenstein tablet input worked some of the time, but there were issues where the two would desync especially at either end of a line.

With high frequency mouse and tablet input these issues would have been more pronounced.

Older versions of Blender don't use the position reported by Wintab. It instead used Window's mouse position and the most recent Wintab pressure and tilt. This Frankenstein tablet input worked some of the time, but there were issues where the two would desync especially at either end of a line. With high frequency mouse and tablet input these issues would have been more pronounced.
Author

I understand. It's unfortunate that a fix for one thing exposes another issue but I suppose my use case is a small minority. I'll see if I can find help through Wacom as the issue really resides outside Blender. Thank you very much for your explanation and all your work.

I understand. It's unfortunate that a fix for one thing exposes another issue but I suppose my use case is a small minority. I'll see if I can find help through Wacom as the issue really resides outside Blender. Thank you very much for your explanation and all your work.

This should be resolved by 2e81f2c01a, if the issue is still present after tonight's daily build please let me know and I'll reopen the issue. If the daily build is earlier than Feb 17, the above change has not yet taken effect.

This should be resolved by 2e81f2c01a, if the issue is still present after tonight's daily build please let me know and I'll reopen the issue. If the daily build is earlier than Feb 17, the above change has not yet taken effect.

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Author

I can confirm it works perfectly on the latest build! Thank you so very very much. You really saved my way of working in Blender, even though the issue really came from outside of it. Fantastic job!

I can confirm it works perfectly on the latest build! Thank you so very very much. You really saved my way of working in Blender, even though the issue really came from outside of it. Fantastic job!

Heads up that mouse mode may lack pressure support in 2.93 and later, but there won't be any issues with the cursor being offset as before.

Heads up that mouse mode may lack pressure support in 2.93 and later, but there won't be any issues with the cursor being offset as before.
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
4 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#83041
No description provided.