Pressure sensitivity stops working after I open "Edit -> Preferences" window (Veikk a15 tablet) #75644
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
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#75644
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-10.0.18362-SP0 64 Bits
Graphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007
Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash:
375c7dc4ca
Short description of error
I am using a Veikk a15 tablet. Pressure sensitive stops working after I open the "Edit -> Preferences" window. Now I work with version 2.82a, but I found the same problem in 2.79 - 2.83a versions. I tried changing the "Preferences -> Input -> Tablet API" settings, but that didn't help.
Exact steps for others to reproduce the error
I open the program in sculpting mode or general and pressure sensitivity works well.
If I open the "Edit -> Preferences" window, then the pressure sensitivity stops working until I restart the program.
Also, pressure sensitivity stops working after opening the save window (ctrl + s).
Added subscriber: @Characters
#79943 was marked as duplicate of this issue
#76181 was marked as duplicate of this issue
Pressure sensitivity not working (veikk a15 tablet)to Pressure sensitivity stops working after I open "Edit -> Preferences" window (Veikk a15 tablet)Added subscriber: @PrototypeNM1
Could you open a second window and check if pressure sensitivity works in it or not?
I tried next steps:
Opened the first Blender window -> It works pressure sensitive.
Opened "Preferences" window -> Pressure sensitivity has stopped working.
Reopened the first Blender window.
Opened "Save(ctrl + s)" window -> Pressure sensitivity has stopped working.
Closed the "Preferences" and "Save window" of the first Blender window
Opened the second Blender window -> It works pressure sensitivity, but only in the second window.
Opened "Preferences" of the second Blender window -> Pressure sensitivity works, but only in the second window.
Opened the "Save window" of the second Blender window -> Pressure sensitivity works, but only in the second window.
Bottom line: In the second window, pressure sensitivity works without problems.
**Video:**https://youtu.be/ZKcfYV1evbA
but...
If I do not close the "Preferences" of the first Blender window, and then open the second Blender window -> The second window reveals problems from steps 2 and 4.
**Video:**https://youtu.be/8O3ETA58crw
I also repeated the algorithm, without performing steps 2-5 -> Pressure sensitivity stops working after opening "Preferences" or "Save" windows in the second Blender window.
**Video:**https://youtu.be/PndwQwzKs7A
This comment was removed by @Characters
@Characters Could you recreate the issue in this build and copy the resulting output to the system console here?
@PrototypeNM1 Sorry, but I can't run this build, becouse I don't have msvcp140D.dll, runtime140D.dll, runtime140_1D.dll, I think, for this build need to have VC++ DebugRedistributable, but I don't have it.
Yep, my bad. Here's a release build of the same.
@PrototypeNM1 I checked.
Console log:
@Characters same thing this build, added more logging information.
@PrototypeNM1 Done
Console log:
If I close the Preferences window, then no logs are displayed in the console, after using Pen. The program seems to treat my pen like a mouse.
That's exactly what's happening. This is a driver bug and I see at least two issues. 1. it's not respecting a change in overlap order and instead continues delivering proximity events to the most recently opened context, 2. the information provided with WT_PROXIMITY events are possibly non-complaint to the wintab spec.
I'll have to think a bit more on this but an obvious solution that doesn't add complications isn't popping up in my mind.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @MeguMeme
https://developer.blender.org/T76181 sorry i occasionally created new task with similar trouble how to remove it or merge with this one?
@Characters @MeguMeme
Could you repeat the bug in this build and copy the system console here? I added additional logging to figure out what Veikk is doing with Wintab contexts.
Yeah i did recreate it
Read prefs: C:\Users\╨а╨╛╨╝╨░\AppData\Roaming\Blender Foundation\Blender\2.90\config\userpref.blend
lcOutOrgX: 0, lcOutOrgY: 0, lcOutExtX: 1920, lcOutExtY: -1080
left: 0, top: 0, width: 1920, height: 1080
initializeWintab numDevices: 1
initializeWintab maxPressure: 8191
initializeWintab maxAzimuth: 3600, maxAltitude: 900
e05ba 30 max contexts, 3 open contexts
initializeWintab queueSize: 500, queueSizeGet: 500
initializeWintab cursor 0 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 1 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 2 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
e05ba updateWintab enable: 1, overlap: 1
found bundled python: D:\Programs\blender-2.90.0-git20200424.6ea5a4d7e766-windows64\2.90\python
e05ba WT_CTXOPEN
e05ba WT_CTXOVERLAP CXS_ONTOP
e05ba WT_CTXOVERLAP CXS_ONTOP
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba updateWintab enable: 1, overlap: 0
e05ba WT_CTXOVERLAP CXS_OBSCURED
e05ba updateWintab enable: 1, overlap: 1
e05ba WT_CTXOVERLAP CXS_ONTOP
e05ba OS button down
Image not found
e05ba OS button up
Image not found
Image not found
Image not found
Image not found
Image not found
Image not found
Image not found
e05ba OS button down
e05ba OS button up
Image not found
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba OS button down
e05ba wintabMouseToGhost left click
e05ba wintab button down ... associated to system button
e05ba 1 system buttons
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba wintabMouseToGhost left click
e05ba wintab button up ... but no system button
e05ba 0 system buttons
e05ba OS button up
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 0
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba OS button down
e05ba wintabMouseToGhost left click
e05ba wintab button down ... associated to system button
e05ba 1 system buttons
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba wintabMouseToGhost left click
e05ba wintab button up ... but no system button
e05ba 0 system buttons
e05ba OS button up
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 0
e05ba WT_PACKET
e05ba OS button down
e05ba OS button up
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba OS button down
e05ba wintabMouseToGhost left click
e05ba wintab button down ... associated to system button
e05ba 1 system buttons
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba wintabMouseToGhost left click
e05ba wintab button up ... but no system button
e05ba 0 system buttons
e05ba OS button up
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 0
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba OS button down
e05ba wintabMouseToGhost left click
e05ba wintab button down ... associated to system button
e05ba 1 system buttons
e05ba wintabMouseToGhost left click
e05ba wintab button up ... but no system button
e05ba 0 system buttons
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba OS button up
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 0
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 0
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba OS button down
e05ba wintabMouseToGhost left click
e05ba wintab button down ... associated to system button
e05ba 1 system buttons
e05ba WT_CSRCHANGE
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 1
e05ba wintabMouseToGhost left click
e05ba wintab button up ... but no system button
e05ba 0 system buttons
e05ba OS button up
e05ba WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
e05ba processWintabProximityEvent inRange: 0
e05ba WT_PACKET
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba updateWintab enable: 1, overlap: 0
lcOutOrgX: 0, lcOutOrgY: 0, lcOutExtX: 1920, lcOutExtY: -1080
left: 0, top: 0, width: 1920, height: 1080
initializeWintab numDevices: 1
initializeWintab maxPressure: 8191
initializeWintab maxAzimuth: 3600, maxAltitude: 900
6065a 30 max contexts, 4 open contexts
initializeWintab queueSize: 500, queueSizeGet: 500
initializeWintab cursor 0 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 1 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 2 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
6065a updateWintab enable: 1, overlap: 1
e05ba WT_CTXOVERLAP CXS_OBSCURED
6065a WT_CTXOPEN
6065a WT_CTXOVERLAP CXS_ONTOP
6065a WT_CTXOVERLAP CXS_ONTOP
e05ba updateWintab enable: 1, overlap: 1
e05ba WT_CTXOVERLAP CXS_ONTOP
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba OS button down
e05ba OS button up
e05ba updateWintab enable: 1, overlap: 0
e05ba WT_CTXOVERLAP CXS_OBSCURED
Does pressure stop working if you leave the preferences window open?
Yeah tried to leave preferences window open pressure still stops working here is log in case you need this
Read prefs: C:\Users\╨а╨╛╨╝╨░\AppData\Roaming\Blender Foundation\Blender\2.90\config\userpref.blend
lcOutOrgX: 0, lcOutOrgY: 0, lcOutExtX: 1920, lcOutExtY: -1080
left: 0, top: 0, width: 1920, height: 1080
initializeWintab numDevices: 1
initializeWintab maxPressure: 8191
initializeWintab maxAzimuth: 3600, maxAltitude: 900
d0338 30 max contexts, 3 open contexts
initializeWintab queueSize: 500, queueSizeGet: 500
initializeWintab cursor 0 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 1 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 2 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
d0338 updateWintab enable: 1, overlap: 1
found bundled python: D:\Programs\blender-2.90.0-git20200424.6ea5a4d7e766-windows64\2.90\python
d0338 WT_CTXOPEN
d0338 WT_CTXOVERLAP CXS_ONTOP
d0338 WT_CTXOVERLAP CXS_ONTOP
d0338 OS button down
d0338 OS button up
d0338 OS button down
d0338 OS button up
d0338 OS button down
d0338 OS button up
d0338 updateWintab enable: 1, overlap: 0
d0338 WT_CTXOVERLAP CXS_OBSCURED
d0338 updateWintab enable: 1, overlap: 1
d0338 WT_CTXOVERLAP CXS_ONTOP
d0338 OS button down
Image not found
d0338 OS button up
Image not found
Image not found
Image not found
Image not found
Image not found
Image not found
Image not found
Image not found
Image not found
d0338 OS button down
d0338 OS button up
Image not found
d0338 OS button down
d0338 OS button up
d0338 OS button down
d0338 OS button up
d0338 OS button down
d0338 OS button up
d0338 OS button down
d0338 OS button up
d0338 OS button down
d0338 OS button up
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 0
d0338 OS button down
d0338 OS button up
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 wintabMouseToGhost left click
d0338 wintab button up ... but no system button
d0338 0 system buttons
d0338 OS button up
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button up
d0338 wintabMouseToGhost left click
d0338 wintab button up ... associated to system button
d0338 0 system buttons
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button up
d0338 wintabMouseToGhost left click
d0338 wintab button up ... associated to system button
d0338 0 system buttons
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 0
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 wintabMouseToGhost left click
d0338 wintab button up ... but no system button
d0338 0 system buttons
d0338 OS button up
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 0
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button up
d0338 wintabMouseToGhost left click
d0338 wintab button up ... associated to system button
d0338 0 system buttons
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 0
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button up
d0338 wintabMouseToGhost left click
d0338 wintab button up ... associated to system button
d0338 0 system buttons
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 wintabMouseToGhost left click
d0338 wintab button up ... but no system button
d0338 0 system buttons
d0338 OS button up
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 wintabMouseToGhost left click
d0338 wintab button up ... but no system button
d0338 0 system buttons
d0338 OS button up
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 wintabMouseToGhost left click
d0338 wintab button up ... but no system button
d0338 0 system buttons
d0338 OS button up
d0338 OS button down
d0338 wintabMouseToGhost left click
d0338 wintab button down ... associated to system button
d0338 1 system buttons
d0338 WT_CSRCHANGE
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 1
d0338 OS button up
d0338 wintabMouseToGhost left click
d0338 wintab button up ... associated to system button
d0338 0 system buttons
d0338 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
d0338 processWintabProximityEvent inRange: 0
d0338 OS button down
d0338 OS button up
d0338 OS button down
d0338 OS button up
d0338 updateWintab enable: 1, overlap: 0
lcOutOrgX: 0, lcOutOrgY: 0, lcOutExtX: 1920, lcOutExtY: -1080
left: 0, top: 0, width: 1920, height: 1080
initializeWintab numDevices: 1
initializeWintab maxPressure: 8191
initializeWintab maxAzimuth: 3600, maxAltitude: 900
2b0630 30 max contexts, 4 open contexts
initializeWintab queueSize: 500, queueSizeGet: 500
initializeWintab cursor 0 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 1 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
initializeWintab cursor 2 buttons
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
2b0630 updateWintab enable: 1, overlap: 1
d0338 WT_CTXOVERLAP CXS_OBSCURED
2b0630 WT_CTXOPEN
2b0630 WT_CTXOVERLAP CXS_ONTOP
2b0630 WT_CTXOVERLAP CXS_ONTOP
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
2b0630 updateWintab enable: 1, overlap: 0
d0338 updateWintab enable: 1, overlap: 1
d0338 OS button down
2b0630 WT_CTXOVERLAP CXS_OBSCURED
d0338 WT_CTXOVERLAP CXS_ONTOP
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_PACKET
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button up
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 0
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button down
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button up
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 0
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 0
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button down
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button up
d0338 OS button down
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button up
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 0
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button down
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button up
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 0
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button down
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button up
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 0
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button down
2b0630 WT_CSRCHANGE
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 1, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 1
d0338 OS button up
2b0630 WT_PROXIMITY loword (!0 enter 0 leave context): 0, hiword (!0 enter !0 leave hardware): 1
2b0630 processWintabProximityEvent inRange: 0
d0338 OS button down
d0338 OS button up
d0338 updateWintab enable: 1, overlap: 0
d0338 WT_CTXOVERLAP CXS_OBSCURED
Added subscriber: @Inferus
Hi! I have exactly the same issue. Mine is a Veikk A30.
Thanks for the hard work <3
im rly sorry if bother, but any updates?
@Characters @Inferus @MeguMeme
What driver version are you using? I ask because this issue looks very similar to a bug reported in GIMP here . Someone in that thread reported contacting Veikk and getting a new driver version 2.0.0.0 which fixed the issue.
To be clear, I believe this is a driver problem which should be solved on Veikk's side. Time permitting I might reach out to them to report the issue.
i downloaded latest driver version from the site(2.0.0.3) and problem still not fixed i also will try to contact Veikk. Ty.
Same here. With the latest version (2.0.0.3) doesn't work either.
Added subscriber: @Davebl
Just got the veikk A50 and have this exact same problem when sculpting, it also does the same thing when using the 2D animation part as well
Im using blender 2.83a and veikk firmware v2.0.0.3 will contact veikk as well
Veikk tech support conclusion. After ~2 hours of trying to fix driver with teamviewer
Lol im going to return my veikk A50 as they still havnt answerd my email i sent them on friday
Any good suggestions for an alternative that actually works properly with sculpting in blender 2.83a and windows 10 pc?
try to write in to chat on their website. After couple of emails i've been asked to move there.
So i returned my veikk A50 for a refund and bought a Huion HS610 and it works great with blender 2.8 with none of the problems of the viekk A50. Very happy now thanks for help
Changed status from 'Confirmed' to: 'Resolved'
I've emailed Veikk with my understanding of the problem; it seems like they're fairly responsive and I think the issue should in-principle be simple so hopefully they can fix this. In the meantime I'm going to mark this as closed as I'm confident this is Veikk's issue.
I'll keep this task updated on Veikk's followup.
Just a quick follow up for closure. I emailed Veikk 2 weeks ago the following (snipped) message:
They responded the same day that they "have already transferred it to our technicians. If there is any need for help. We will contact you."
To date they have not had any further followup and I have no way of checking on their follow through so at this point I must leave the issue to those more invested in the problem.
Added subscribers: @Natustell, @SuBrebu, @Hongyu, @iss
for me it my a15 always worked, until 2.9. and veikk didn't have any driver update.
it still work in 2.83 for me. so I'm not sure if it is purely viekk's problem.
@Hongyu I'll investigate if you run [this build ]] and upload the console log [ https:*developer.blender.org/paste/edit/form/default/ | here .
blender.log
the weird thing happened, official 2.9 now works fine..i have no idea why. before it didn't work
but the version u gave me was bugged. it only draw on the top left corner. i have one 4k monitor and 2 hd
Added subscriber: @nicholas-14
@Hongyu From the log I only see one window receiving events.
Blender 2.9 had not significant change in tablet input, so that the issue appears and disappears without clear cause combined with known issues in their driver makes me further suspect driver issues.
I'll likely have more questions wrt only being able to draw in the top left corner.