Gaomon Pen Tablet Stops Functioning #101807

Open
opened 2022-10-13 20:41:10 +02:00 by Kaze Sequeris · 17 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: AMD Radeon R9 200 / HD 7900 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a9
Worked: Not sure, not since 3.0 at least.

Short description of error
Using Gaomon pen tablet (M10K with latest drivers, 16.0.0.37)
Pen tablet stops functioning under various circumstances.
Pen stops functioning only in Blender. When Blender is not active window, pen resumes function. Pen will not function again inside Blender until all instances of Blender are completely closed and reopened. Starting a new empty scene from file menu does not fix it. Interestingly, only the motion itself is disabled - the buttons on the pen and tablet will still work (right clicking with the pen still opens the context menu, hotkeys still perform function, ect).

Perhaps unrelated, might be a different bug, but after rotating the camera with the pen middle-mouse, any attempt to rotate with the mouse middle-mouse button does so in clunky steps, instead of smoothly. Alt-tabbing to a different window then alt-tabbing back fixes this and makes it smooth again.

Three tested things so far that break the tablet:

  • Subdividing an Object
    Using the subdivision modifier is the most consistent, and breaks the tablet with lower face count of 23,000.

  • Raising Face Count Too High
    Without using subdivision, extruding and loopcutting a cube enough times breaks the tablet at around 120,000 faces

  • Enabling a hidden Collection
    Enabling a disabled collection with more than one object. This doesn't always happen. Collection tested has 3 objects (even when hidden in viewport) with no modifiers and face count below 20,000

Simply loading a save with one of the above already saved also breaks the pen function, making progress impossible.

Exact steps for others to reproduce the error
TabletBug post failure.blend

Simply loading "TabletBugPostFailure.blend" produces error. Pen will not move cursor at all.

TabletBug Pre failure.blend

After loading "TabletBugPreFailure.blend", add a subdivision modifier to the rounded cube object. Pen will move cursor before subdivision, but will not move after the modifier is added.

Tablet Bug character file.blend

After loading "TabletBugCharacterFile.blend", add a subdivision modifier to the character "body" object. Pen stops functioning

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: AMD Radeon R9 200 / HD 7900 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6 **Blender Version** Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: `b292cfe5a9` Worked: Not sure, not since 3.0 at least. **Short description of error** Using Gaomon pen tablet (M10K with latest drivers, 16.0.0.37) Pen tablet stops functioning under various circumstances. Pen stops functioning only in Blender. When Blender is not active window, pen resumes function. Pen will not function again inside Blender until all instances of Blender are completely closed and reopened. Starting a new empty scene from file menu does not fix it. Interestingly, only the motion itself is disabled - the buttons on the pen and tablet will still work (right clicking with the pen still opens the context menu, hotkeys still perform function, ect). Perhaps unrelated, might be a different bug, but after rotating the camera with the pen middle-mouse, any attempt to rotate with the mouse middle-mouse button does so in clunky steps, instead of smoothly. Alt-tabbing to a different window then alt-tabbing back fixes this and makes it smooth again. Three tested things so far that break the tablet: - Subdividing an Object Using the subdivision modifier is the most consistent, and breaks the tablet with lower face count of 23,000. - Raising Face Count Too High Without using subdivision, extruding and loopcutting a cube enough times breaks the tablet at around 120,000 faces - Enabling a hidden Collection Enabling a disabled collection with more than one object. This doesn't always happen. Collection tested has 3 objects (even when hidden in viewport) with no modifiers and face count below 20,000 Simply loading a save with one of the above already saved also breaks the pen function, making progress impossible. **Exact steps for others to reproduce the error** [TabletBug post failure.blend](https://archive.blender.org/developer/F13674354/TabletBug_post_failure.blend) Simply loading "TabletBugPostFailure.blend" produces error. Pen will not move cursor at all. [TabletBug Pre failure.blend](https://archive.blender.org/developer/F13674364/TabletBug_Pre_failure.blend) After loading "TabletBugPreFailure.blend", add a subdivision modifier to the rounded cube object. Pen will move cursor before subdivision, but will not move after the modifier is added. [Tablet Bug character file.blend](https://archive.blender.org/developer/F13674382/Tablet_Bug_character_file.blend) After loading "TabletBugCharacterFile.blend", add a subdivision modifier to the character "body" object. Pen stops functioning
Author

Added subscriber: @KazeSequeris

Added subscriber: @KazeSequeris
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Does changing the tablet API in Preferences > Input > Tablet API make any difference? Does any of the options work better?

Does changing the tablet API in Preferences > Input > Tablet API make any difference? Does any of the options work better?
Author

It appears that yes, changing the API has an effect. Both options will stop the error. Pen even still works when switching back to automatic during the session, but will stop working again when loading a new file while automatic is saved in preferences. Automatic is the only setting that breaks the pen.

Thank you for pointing these settings out to me, switching the API means I can continue to work!

In the event more testing brings up the same/very similar error, should I reply to this thread with it, or would that require I open a new task?

It appears that yes, changing the API has an effect. Both options will stop the error. Pen even still works when switching back to automatic during the session, but will stop working again when loading a new file while automatic is saved in preferences. Automatic is the only setting that breaks the pen. Thank you for pointing these settings out to me, switching the API means I can continue to work! In the event more testing brings up the same/very similar error, should I reply to this thread with it, or would that require I open a new task?
Member

Added subscriber: @PrototypeNM1

Added subscriber: @PrototypeNM1
Member

@PrototypeNM1 Any idea about the behavior described in the comment above where Automatic tablet API selection can cause issues?

@KazeSequeris If it is the same issue, you can just comment back on this report and we can reinvestigate.

@PrototypeNM1 Any idea about the behavior described in the comment above where Automatic tablet API selection can cause issues? @KazeSequeris If it is the same issue, you can just comment back on this report and we can reinvestigate.

Added subscriber: @dyonisius

Added subscriber: @dyonisius

I'm having the exact same problem with a Gaomon s620, anything that causes a heavy load crashes the tablet motion, setting tablet API to wintab still crashes, it only stops crashing when I set to Windows Ink

I'm having the exact same problem with a Gaomon s620, anything that causes a heavy load crashes the tablet motion, setting tablet API to wintab still crashes, it only stops crashing when I set to Windows Ink

Could you run blender --debug-wintab and recreate the issue, then paste the console log here and link the paste to this report?

Could you run `blender --debug-wintab` and recreate the issue, then paste the console log [here](https://developer.blender.org/paste/edit/form/default/) and link the paste to this report?

There you go
Debug

There you go [Debug ](https://developer.blender.org/P3257)

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'

At a glance this sounds like input buffer filled and we didn't get a message to empty it. Will have to investigate.

At a glance this *sounds* like input buffer filled and we didn't get a message to empty it. Will have to investigate.
Nicholas Rishel self-assigned this 2022-12-18 00:12:40 +01:00

Is there any news about this? I have a Gaomon s620 and the pen pressure stops working when opening the program or when there are heavy loads.
It only happens in Blender 3.0 to 3.6, version 2.93 this does not happen.

Is there any news about this? I have a Gaomon s620 and the pen pressure stops working when opening the program or when there are heavy loads. It only happens in Blender 3.0 to 3.6, version 2.93 this does not happen.

I have a gaomon tablet, I meet the same issue, what happened! any solution?

I have a [gaomon tablet](https://pctechtest.com/best-gaomon-drawing-tablets), I meet the same issue, what happened! any solution?

Still no solution :,(

Still no solution :,(
Author

I can't speak for the devs of course, but in my case, changing the tablet API in Preferences > Input > Tablet API to something other than 'automatic' fixed the issue for me. Might need to test each option in turn, but if that works, at least you can continue using the pen while they figure out what exactly is wrong. If not, maybe open a new ticket? I'm sure the devs are working on fixes for things and will get to it when they can, but more attention might bump it up a little on the priority list.

I can't speak for the devs of course, but in my case, changing the tablet API in Preferences > Input > Tablet API to something other than 'automatic' fixed the issue for me. Might need to test each option in turn, but if that works, at least you can continue using the pen while they figure out what exactly is wrong. If not, maybe open a new ticket? I'm sure the devs are working on fixes for things and will get to it when they can, but more attention might bump it up a little on the priority list.
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
7 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#101807
No description provided.