Lose wacom presure when use two windows. #53553

Closed
opened 2017-12-13 11:33:32 +01:00 by Alberto Velázquez · 39 comments

System Information
Windows 7 64bits
Two monitors

Blender Version
2.79
It's broken since I remember, only that I ignored the problem.

Short description of error
When you uses multiple windows in same blender instance and a wacom tablet blender lost the pressure or "focus" of the wacom and only go back when you click in the secondary window. And sometimes blender don't paint the grease pencils

The bug affect to painting modes, sculpt, and grease pencil drawing. The problem, that I was ignored because click in the secondary window to obtain presure is not a big problem. But now I have see that also you can have problems with grease pencil, creating "invisible" strokes that don't work with bsurfaces. Blocking the workflow until you "imagine" the problem or close and open blender other time.

Exact steps for others to reproduce the error

  • Open Blender and create a secondary window with 3D view (in my test work with other panels themes)
  • Click in the secondary window
  • Open other program, browser for example (chrome)
  • hide the secondary window
  • focus in chrome
  • focus in primary 3D view
  • Try to paint

Notes:

  • In my test it works with windows in different or same monitor, I don't know if it affects to the problem.
  • Some times it doesn't work and you must try so iterations of Blender -> Chrome ->Blender -> hide secondary. But I obtain it making few iterations, in less that one minute
**System Information** Windows 7 64bits Two monitors **Blender Version** 2.79 It's broken since I remember, only that I ignored the problem. **Short description of error** When you uses multiple windows in same blender instance and a wacom tablet blender lost the pressure or "focus" of the wacom and only go back when you click in the secondary window. **And sometimes blender don't paint the grease pencils** The bug affect to painting modes, sculpt, and grease pencil drawing. The problem, that I was ignored because click in the secondary window to obtain presure is not a big problem. But now I have see that also you can have problems with grease pencil, creating "invisible" strokes that don't work with bsurfaces. Blocking the workflow until you "imagine" the problem or close and open blender other time. **Exact steps for others to reproduce the error** - Open Blender and create a secondary window with 3D view (in my test work with other panels themes) - Click in the secondary window - Open other program, browser for example (chrome) - hide the secondary window - focus in chrome - focus in primary 3D view - Try to paint Notes: - In my test it works with windows in different or same monitor, I don't know if it affects to the problem. - Some times it doesn't work and you must try so iterations of Blender -> Chrome ->Blender -> hide secondary. But I obtain it making few iterations, in less that one minute

Added subscriber: @AlbertoVelazquez

Added subscriber: @AlbertoVelazquez

#65602 was marked as duplicate of this issue

#65602 was marked as duplicate of this issue

#68188 was marked as duplicate of this issue

#68188 was marked as duplicate of this issue
pati5202 commented 2017-12-14 04:07:23 +01:00 (Migrated from localhost:3001)

Added subscriber: @pati5202

Added subscriber: @pati5202
pati5202 commented 2017-12-14 04:07:23 +01:00 (Migrated from localhost:3001)

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
pati5202 commented 2017-12-14 04:07:23 +01:00 (Migrated from localhost:3001)

This comment was removed by @pati5202

*This comment was removed by @pati5202*

Added subscriber: @mont29

Added subscriber: @mont29

Removed subscriber: @pati5202

Removed subscriber: @pati5202

Changed status from 'Resolved' to: 'Open'

Changed status from 'Resolved' to: 'Open'

Added subscriber: @kiiiwii

Added subscriber: @kiiiwii

Removed subscriber: @kiiiwii

Removed subscriber: @kiiiwii
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

I cant seem to be able to reproduce this (but I am on linux gnome). Could you confirm this on other machines? Does this happen on other OSes as well?

I cant seem to be able to reproduce this (but I am on linux gnome). Could you confirm this on other machines? Does this happen on other OSes as well?

I have never tried two monitors/windows in linux or macOS. But I can confirm this in Windows 7 64bits in a lot of machines and configurations.

I have never tried two monitors/windows in linux or macOS. But I can confirm this in Windows 7 64bits in a lot of machines and configurations.
Member

note that I only tested this with one monitor, still possible this happens with two (but report mentioned this also fails with only one monitor)
A bit speculative, but tagging as windows until someone can reproduce elsewhere...

note that I only tested this with one monitor, still possible this happens with two (but report mentioned this also fails with only one monitor) A bit speculative, but tagging as windows until someone can reproduce elsewhere...

After some test I can't reproduce with one monitor in macOS, so probably is only a problem in windows systems.

After some test I can't reproduce with one monitor in macOS, so probably is only a problem in windows systems.

Added subscribers: @kickkill, @Adam-Doda

Added subscribers: @kickkill, @Adam-Doda
Member

Added subscribers: @Dargorn, @Kijai, @ZedDB, @brecht

Added subscribers: @Dargorn, @Kijai, @ZedDB, @brecht
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

Changed status from 'Confirmed' to: 'Needs Developer To Reproduce'

Changed status from 'Confirmed' to: 'Needs Developer To Reproduce'
Member

In order to add support for specific device we need to be able to have access to the device. So marking this for now as Known Issue, with low priority and needs developer to reproduce.

In order to add support for specific device we need to be able to have access to the device. So marking this for now as Known Issue, with low priority and needs developer to reproduce.

Raising the priority of this a bit, I think it's a fairly important issue.

Raising the priority of this a bit, I think it's a fairly important issue.

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Changed status from 'Needs Developer To Reproduce' to: 'Archived'
Alberto Velázquez self-assigned this 2020-04-02 23:14:13 +02:00

I cant reproduce the bug actually

I cant reproduce the bug actually
Member

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo
Member

i'm not sure if i can repro it in the current state, but while testing D6675 this one was real easy to trigger, as soon as the blender window does not have the focus you lose pressure

i'm not sure if i can repro it in the current state, but while testing [D6675](https://archive.blender.org/developer/D6675) this one was real easy to trigger, as soon as the blender window does not have the focus you lose pressure

In #53553#902444, @LazyDodo wrote:
i'm not sure if i can repro it in the current state, but while testing D6675 this one was real easy to trigger, as soon as the blender window does not have the focus you lose pressure

If you are able to reproduce easily you are free to check it, actually all my computer have change since the bug and because the lockdown I can't go to pick the old parts

> In #53553#902444, @LazyDodo wrote: > i'm not sure if i can repro it in the current state, but while testing [D6675](https://archive.blender.org/developer/D6675) this one was real easy to trigger, as soon as the blender window does not have the focus you lose pressure If you are able to reproduce easily you are free to check it, actually all my computer have change since the bug and because the lockdown I can't go to pick the old parts

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'
Alberto Velázquez was unassigned by Brecht Van Lommel 2020-04-03 00:17:49 +02:00

Leaving open, there are 3 other bug reports merged into this one so it's not just about one case.

Leaving open, there are 3 other bug reports merged into this one so it's not just about one case.

OK, I only closed the bug by petition of a dev by blender.chat.

OK, I only closed the bug by petition of a dev by blender.chat.

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

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

There have been significant changes to tablet handling on Windows today. Can those who had this problem verify if this is now working correctly in the latest build?
https://builder.blender.org/download/

There have been significant changes to tablet handling on Windows today. Can those who had this problem verify if this is now working correctly in the latest build? https://builder.blender.org/download/

Been a while I've used the tablet, but now that I try the behavior is still the same for me: only main window gets pressure.
blender-2.90-76e56e2ba70f-windows64

Been a while I've used the tablet, but now that I try the behavior is still the same for me: only main window gets pressure. blender-2.90-76e56e2ba70f-windows64
Member

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Added subscriber: @AdrianCabrera

Added subscriber: @AdrianCabrera

I also have this issue with Blender 2.9

I am using a Huion Kamvas Pro 16 graphics tablet.

When I open a new window in the same instance of Blender pressure sensitivity no longer works in the original window.

I also have this issue with Blender 2.9 I am using a Huion Kamvas Pro 16 graphics tablet. When I open a new window in the same instance of Blender pressure sensitivity no longer works in the original window.

Added subscriber: @PrototypeNM1

Added subscriber: @PrototypeNM1

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Nicholas Rishel self-assigned this 2020-10-31 02:41:05 +01:00

D7840 resolved the motivating bug for this report. If one of the merged bugs was not resolved please open an new issue.

[D7840](https://archive.blender.org/developer/D7840) resolved the motivating bug for this report. If one of the merged bugs was not resolved please open an new issue.
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
12 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#53553
No description provided.