Tablet Pressure not working in New Window #93323
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#93323
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10 20H1
Graphics card: Nvidia 2070 8G
Drawing Tablet: Huion Kamvas 16 Pro 2019
system-info.txt
Blender Version
Broken: 2.92.0 and 2.93.6
Short description of error
Pen pressure not working on newly created window. Very repeatable.
The steps outlined bellow as well as the attached video evidence prove that the Tablet Pen is working In blender just not on the newly created window.
Exact steps for others to reproduce the error
Pressure is working.
Expected behavior would be that the pressure works in the newly created window.
Added subscriber: @adamc1228
With a fresh restart of my computer and fresh eyes, I can confirm that the default scene exhibits this behavior and that it does not appear project specific.
Results of additional Testing:
If you repeat the process and omit step 3 and drag the main window to the Kamvas tablet instead, then the pressure works. This testing was done with the default scene and cube. During this additional testing I think I can make out what is the inner ring that indicates the pressure but it appears to instantly snap to maximum radius of the brush. The best I can relate this behavior to is that it is treating the tablet input on the new window as a mouse click which would use the the max radius we defined.
Added subscriber: @PrototypeNM1
Could you check if the issue is present in Blender 3.0?
I can confirm that Blender 3.0.0 beta available for download (Beta November 24, 02:41:54 - v30 -
3844e9dbe7
- zip) exhibits the same issue. Interestingly, the inner ring to indicate pressure, is constantly cycling (visually) from tiny to large as I paint but continues to operate as if 100% pressure is applied all the time as in blender 2.92 and 2.93.6 in the new window.There's a common driver bug where the tablet sends input to the wrong window. When I get a down moment I'll add some logging to check if that's the case.
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Works fine for me here (but I am on Linux, single monitor with a Wacom Intuos 4, so I cant really "move the window to the tablet").
@PrototypeNM1 : did you get to adding the logging? How can we proceed here?
Added subscriber: @Voguart
Hello friends,
I have a relatively similar problem with my Huion tablet.
Blender version 3.0
Huion kamvas pro 20 tablet with latest huion driver update.
System Windows 10, 64 Pro,
Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz 4.00GHz
The support of the latter and random in sculpt mode, once the stylus is lifted from the screen the test pattern of the stylus disappears, I have to press the screen more times with the stylus so that the pattern remains on the screen . This problem only occurs from Blender version 3.0.
This comment was removed by @Voguart
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
@adamc1228 could you repeat the bug by running
blender.exe --debug-wintab
with this build, copy the system console to this link, and link the paste in a reply to this report?Thanks, I will download that and hopefully give it a try before the end of the weekend.
@adamc1228 Quick reminder for followup. :)
Hi Nicholas,
Sorry for the delay. I have attached the link with the Console data as requested. Additionally, I recorded a short video of the test if that assists you. I would like to point out that my system specs have changed slightly since this was opened in December.
Changes;
Fresh Install Windows 11
GPU is now 3080.
2022-05-23 21-15-10.mkv
Console Paste
Looking at the logs, it appears that the Wintab context recognizes that the window has changed, then keeps delivering events to the first window (paired with the Wintab context for the latter window). This is unambiguously a driver bug, but one we might be able to work around.
Given we've seen this same broken behavior for other drivers, I think I'll at least test an approach that would fix it. Just a heads up that If the "fix" breaks other devices we might have to write this off as a driver issue that we can't fix and we'll have to redirect to reporting the bug to the manufacturer.
Changed status from 'Needs User Info' to: 'Confirmed'
Germano Cavalcante referenced this issue2024-04-03 20:01:53 +02:00