Graphics Pen Tablet Input Broken with version 2.77 and 2.77a #48129

Closed
opened 2016-04-12 21:08:38 +02:00 by Simon · 14 comments

System Information
Windows 7
Nvidia Gefore GTX 970 (driver version 10.18.13.6451)
Monoprice 8" x 6" Graphics Tablet (#13653) (UGTizer Driver version 6.1.7600.16385)
Driver links: http://driverlibs.com/download/PenTablet-Device
http://driverlibs.com/download/PenTablet-TabletPC-driver

Blender Version
Broken: 2.77a 2016-04-05 18:12 Hash: abf6f08
Worked: 2.76b 2015-Nov-04 07:53:43

After starting Blender 2.77(a), the every cursor input with the pen tablet (in absolute positioning mode) locks the cursor to one position (2.77 the coordinates are 0,0 and 2.77a the coordinates are 1476,0). Using the mouse will move the cursor away from these coordinates but every subsequent pen tablet input will lock the cursor back to the listed coordinates. If any of the buttons of the Pen are depressed, the cursor will move to the actual coordinates but this will not allow cursor input.

Link to Screen Captures
http://imgur.com/a/17OMN (Note the "Mouse Pos" application window)

Exact steps for others to reproduce the error

  1. Ensure tablet is connected, drivers are installed, and tablet is functioning
  2. Open Blender 2.77
  3. Use pen anywhere on the graphics tablet.
**System Information** Windows 7 Nvidia Gefore GTX 970 (driver version 10.18.13.6451) Monoprice 8" x 6" Graphics Tablet (#13653) (UGTizer Driver version 6.1.7600.16385) Driver links: http://driverlibs.com/download/PenTablet-Device http://driverlibs.com/download/PenTablet-TabletPC-driver **Blender Version** Broken: 2.77a 2016-04-05 18:12 Hash: abf6f08 Worked: 2.76b 2015-Nov-04 07:53:43 After starting Blender 2.77(a), the every cursor input with the pen tablet (in absolute positioning mode) locks the cursor to one position (2.77 the coordinates are 0,0 and 2.77a the coordinates are 1476,0). Using the mouse will move the cursor away from these coordinates but every subsequent pen tablet input will lock the cursor back to the listed coordinates. If any of the buttons of the Pen are depressed, the cursor will move to the actual coordinates but this will not allow cursor input. **Link to Screen Captures** http://imgur.com/a/17OMN (Note the "Mouse Pos" application window) **Exact steps for others to reproduce the error** 1) Ensure tablet is connected, drivers are installed, and tablet is functioning 2) Open Blender 2.77 3) Use pen anywhere on the graphics tablet.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @neuone

Added subscriber: @neuone

Added subscriber: @tompov

Added subscriber: @tompov

I don't know, if it's a similar porblem with my wacom tablet, I had a few days ago:
Here it was caused by no longer existing blender-app.exe in latest Blenderversions.
My Blender specific Wacomsettings pointed to this file. After changing this target to blender.exe all was fine again.

I don't know, if it's a similar porblem with my wacom tablet, I had a few days ago: Here it was caused by no longer existing blender-app.exe in latest Blenderversions. My Blender specific Wacomsettings pointed to this file. After changing this target to blender.exe all was fine again.
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

That would make sense, @neuone, can you confirm that this works?

That would make sense, @neuone, can you confirm that this works?
Author

The tablet I'm using doesn't have any application specific settings so I don't think that is the issue.

The tablet I'm using doesn't have any application specific settings so I don't think that is the issue.
Author

@tompov and @JulianEisel I may have found the source of the bug. It looks like the functions GHOST_WindowWin32.processWin32TabletInitEvent() and GHOST_WindowWin32.processWin32TabletEvent() functions weren't parsing the cursor X,Y,Z locations (they weren't defined in GHOST_WindowWin32.h). I'm going to do some further testing before I submit any changes but right now my tablet is working with my debug build.

@tompov and @JulianEisel I may have found the source of the bug. It looks like the functions GHOST_WindowWin32.processWin32TabletInitEvent() and GHOST_WindowWin32.processWin32TabletEvent() functions weren't parsing the cursor X,Y,Z locations (they weren't defined in GHOST_WindowWin32.h). I'm going to do some further testing before I submit any changes but right now my tablet is working with my debug build.

Added subscriber: @mont29

Added subscriber: @mont29

@neuone any news on this one?

@neuone any news on this one?
Author

@mont29 unfortunately no. I've been too busy with work to devote any time to this bug this week. It seems like tablet input hasn't been completely fleshed out in GHOST. This problem seems to be tied to how blender grabs and processes a system tablet or mouse event, even when blender is not the application that is in focus. I have found only one application that can maintain control of a system tablet event while Blender is running: the tablet driver settings panel. When I defined the PACKETDATA PK_X, PK_Y, and PK_Z GHOST stopped hijacking the cursor. This lead to the discovery of another bug (not really a bug, more of a lack of implementation) though: the cursor wrap/warp functions don't know how to handle input from an absolute positioning device and the warp/wrap funtions cause the cursor delta to change more rapidly. Say you're translating in X just a few units, when the cursor moves out of the viewport, the translation will shoot up an order of magnitude.

This bug will probably require the attention of someone more knowledgeable than myself.

@mont29 unfortunately no. I've been too busy with work to devote any time to this bug this week. It seems like tablet input hasn't been completely fleshed out in GHOST. This problem seems to be tied to how blender grabs and processes a system tablet or mouse event, even when blender is not the application that is in focus. I have found only one application that can maintain control of a system tablet event while Blender is running: the tablet driver settings panel. When I defined the PACKETDATA PK_X, PK_Y, and PK_Z GHOST stopped hijacking the cursor. This lead to the discovery of another bug (not really a bug, more of a lack of implementation) though: the cursor wrap/warp functions don't know how to handle input from an absolute positioning device and the warp/wrap funtions cause the cursor delta to change more rapidly. Say you're translating in X just a few units, when the cursor moves out of the viewport, the translation will shoot up an order of magnitude. This bug will probably require the attention of someone more knowledgeable than myself.

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-03-19 10:49:15 +01:00

Pressure input on Windows has been completely changed since this was reported. Closing under the assumption that this was fixed, can reopen if it's not the case.

Pressure input on Windows has been completely changed since this was reported. Closing under the assumption that this was fixed, can reopen if it's not the case.
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#48129
No description provided.