Cintiq 27 Pro - possible WM bug #108113

New Issue

Closed

opened 2023-05-21 01:49:05 +02:00 by Kittyn-Xr · 5 comments

Kittyn-Xr commented

2023-05-21 01:49:05 +02:00

System Information
Operating system: Windows 11 Enterprise
Graphics card: NVidia 4090

Blender Version
Broken: 3.5.1
Worked: Worked perfectly on previous generation Cintiqs

When using blender, then pen input will become unresponsive when lifting it from the screen and placing it in another window or context. For example lifting the pen in the viewport and setting it down in the outliner.

The only way to get the pen cursor back while using blender is to use it in windowed mode and when it happens -- drag the pen - while in range of the screen - to one of the edges without lifting up.

The interesting thing about this bug is that it doesn't occur when blender is minimized. Even if blender is open in the background this problem will persist system-wide no matter what program I'm using until it gets minimized.

Have done a full system rebuild and even with everything fresh it persists.

I've set up a blender build environment to start searching for the cause of the problem and do custom builds, but am hopeful that someone here might already know what could cause this.

The new Cintiq pro has a new driver and Wacom app, so my guess is it's related to that.

One thing that stood out to me about the new driver is the ability to set the "Windows Ink Mode" on a per app basis rather than having to do it per-pen.

Thanks for your help or input!

**System Information** Operating system: Windows 11 Enterprise Graphics card: NVidia 4090 **Blender Version** Broken: 3.5.1 Worked: Worked perfectly on previous generation Cintiqs When using blender, then pen input will become unresponsive when lifting it from the screen and placing it in another window or context. For example lifting the pen in the viewport and setting it down in the outliner. The only way to get the pen cursor back while using blender is to use it in windowed mode and when it happens -- drag the pen - while in range of the screen - to one of the edges without lifting up. The interesting thing about this bug is that it doesn't occur when blender is minimized. Even if blender is open in the background this problem will persist system-wide no matter what program I'm using until it gets minimized. Have done a full system rebuild and even with everything fresh it persists. I've set up a blender build environment to start searching for the cause of the problem and do custom builds, but am hopeful that someone here might already know what could cause this. The new Cintiq pro has a new driver and Wacom app, so my guess is it's related to that. One thing that stood out to me about the new driver is the ability to set the "Windows Ink Mode" on a per app basis rather than having to do it per-pen. Thanks for your help or input!

Kittyn-Xr added the

labels 2023-05-21 01:49:05 +02:00

Iliya Katushenock added the

label 2023-05-21 10:46:21 +02:00

Pratik Borhade commented

2023-05-22 19:40:31 +02:00

Member

Hi, thanks for the report.

Even if blender is open in the background this problem will persist system-wide no matter what program I'm using until it gets minimized.

Do you observe unresponsive pen-touch just in Blender instance or the entire system?

The new Cintiq pro has a new driver and Wacom app, so my guess is it's related to that.

Could you reinstall or try previous version to ensure drivers are culprit?

Any improvement in behavior with different tablet API?: Edit > Preference > Input > tablet

Hi, thanks for the report. > Even if blender is open in the background this problem will persist system-wide no matter what program I'm using until it gets minimized. Do you observe unresponsive pen-touch just in Blender instance or the entire system? > The new Cintiq pro has a new driver and Wacom app, so my guess is it's related to that. Could you reinstall or try previous version to ensure drivers are culprit? Any improvement in behavior with different tablet API?: `Edit > Preference > Input > tablet`

Pratik Borhade added

Needs Information from User

and removed

labels 2023-05-22 19:40:43 +02:00

YimingWu commented

2023-05-23 11:53:06 +02:00

Member

Hi, Cintiq 27 Pro is a very new piece of hardware. We probably would need the exact same device to be able to replicate the issue. I'm not even sure if it still uses WinTab driver. Try enabling windows ink in both Wacom driver and Blender and see if the situation improves.

AFAIK Blender doesn't specifically handle pen enter/leave event. So it might very likely be a problem of the driver itself if pointer is disabled system-wise. Do you have any problems with other art programs or this is only with Blender?

Also you mentioned setting up a build environment, you could try adding some printfs inside void GHOST_SystemWin32::processWintabEvent(GHOST_WindowWin32 *window) in GHOST_SystemWin32.cc and try to see if there's any specific "rogue" event that triggers the behaviour. Thanks!

Hi, Cintiq 27 Pro is a _very_ new piece of hardware. We probably would need the exact same device to be able to replicate the issue. I'm not even sure if it still uses WinTab driver. Try enabling windows ink in both Wacom driver and Blender and see if the situation improves. AFAIK Blender doesn't specifically handle pen enter/leave event. So it might very likely be a problem of the driver itself if pointer is disabled system-wise. Do you have any problems with other art programs or this is only with Blender? Also you mentioned setting up a build environment, you could try adding some `printf`s inside ` void GHOST_SystemWin32::processWintabEvent(GHOST_WindowWin32 *window)` in `GHOST_SystemWin32.cc` and try to see if there's any specific "rogue" event that triggers the behaviour. Thanks!

Kittyn-Xr commented

2023-05-23 15:50:19 +02:00

Author

Hi, Cintiq 27 Pro is a very new piece of hardware. We probably would need the exact same device to be able to replicate the issue. I'm not even sure if it still uses WinTab driver. Try enabling windows ink in both Wacom driver and Blender and see if the situation improves.

AFAIK Blender doesn't specifically handle pen enter/leave event. So it might very likely be a problem of the driver itself if pointer is disabled system-wise. Do you have any problems with other art programs or this is only with Blender?

Also you mentioned setting up a build environment, you could try adding some printfs inside void GHOST_SystemWin32::processWintabEvent(GHOST_WindowWin32 *window) in GHOST_SystemWin32.cc and try to see if there's any specific "rogue" event that triggers the behaviour. Thanks!

Thanks for the reply, I figured this was the case -- will give this a try later today or tomorrow to see if we can learn anything!

As for setting windows ink in both blender and the driver, I have tried all combinations and it didn't improve the situation.

It doesn't happen in any other art programs so long as blender stays minimized.

Will update as soon as we have some results - thanks!

> Hi, Cintiq 27 Pro is a _very_ new piece of hardware. We probably would need the exact same device to be able to replicate the issue. I'm not even sure if it still uses WinTab driver. Try enabling windows ink in both Wacom driver and Blender and see if the situation improves. > > AFAIK Blender doesn't specifically handle pen enter/leave event. So it might very likely be a problem of the driver itself if pointer is disabled system-wise. Do you have any problems with other art programs or this is only with Blender? > > Also you mentioned setting up a build environment, you could try adding some `printf`s inside ` > void GHOST_SystemWin32::processWintabEvent(GHOST_WindowWin32 *window)` in `GHOST_SystemWin32.cc` and try to see if there's any specific "rogue" event that triggers the behaviour. Thanks! Thanks for the reply, I figured this was the case -- will give this a try later today or tomorrow to see if we can learn anything! As for setting windows ink in both blender and the driver, I have tried all combinations and it didn't improve the situation. It doesn't happen in any other art programs so long as blender stays minimized. Will update as soon as we have some results - thanks!

Kittyn-Xr commented

2023-05-24 20:03:28 +02:00

Author

Seems the problem is isolated to 3.5.x

Got everything to build and threw in a couple printfs in that method but on loading into debug mode - realized the source was for blender 4.0 -- but the bug is gone.

I got the tablet right about the time 3.5 released so never even bothered with the previous versions since all the plugins I use are compatible with 3.5. I would keep using the alpha but some things I use often don't work with it yet.

Solved: Will just skip 3.5 or wait for a later version to test.

But if you end up needing a tester with this device later on feel free to ping me - will keep the build environment. Cheers!

Seems the problem is isolated to 3.5.x Got everything to build and threw in a couple printfs in that method but on loading into debug mode - realized the source was for blender 4.0 -- but the bug is gone. I got the tablet right about the time 3.5 released so never even bothered with the previous versions since all the plugins I use are compatible with 3.5. I would keep using the alpha but some things I use often don't work with it yet. Solved: Will just skip 3.5 or wait for a later version to test. But if you end up needing a tester with this device later on feel free to ping me - will keep the build environment. Cheers!

Kittyn-Xr closed this issue

2023-05-24 20:03:31 +02:00

Blender Bot added

and removed

Needs Information from User

labels 2023-05-24 20:03:31 +02:00

YimingWu commented

2023-05-25 03:40:14 +02:00

Member

@Kittyn-Xr Thanks for letting us know. I'll note this down in case of further reports. I don't think in the case of WM anything changed between 3.5 and 4.0, so that's kinda interesting. Glad you make it work again!

@Kittyn-Xr Thanks for letting us know. I'll note this down in case of further reports. I don't think in the case of WM anything changed between 3.5 and 4.0, so that's kinda interesting. Glad you make it work again!

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

3 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#108113

No description provided.