WinTab + other window interactivity bugged (& WinInk pressure bug?)

Heya!

I’ve stumbled upon another weird interactivity bug regarding WinTab on Nomad.
Tested on Stable 23, Beta 25 & Beta 27. They all behave similarly so I will focus on Beta 27.

WinTab Issue

Everything explained behaves correctly when using WinInk OR the mouse.
My current problem will ONLY happen with these settings:
WinTab = ON & WinInk = OFF
(Further below I will explain why using WinInk isn’t great for me. (Pressure Bug))

In the video below you will see me start out using only the pen to interact with the screen (Using the mouse behaves as expected, until it misbehaves and then also the mouse stops working.) The video starts out using only the right click functionality, and when it misbehaves I will spam click everything so you can see what happens.

  • Firstly I rotate the model using hold right click
  • Then I will hold right click into Pureref (Usually this enables PureRef to be dragged across the screen to reposition it.)
  • This doesn’t work as it just right clicks
  • When I try to go back into Nomad by left clicking or right clicking you can see it Freeze, continued by lagging and stuttering.
  • During the freeze I am still moving and clicking the mouse and pen, but the mouse cursor doesn’t update, nor does the Nomad sculpt circle
  • This only fixes itself if I don’t move the mouse and let the lagging operations (sculpting/rotating) catch up to me. (Even switching to my mouse does not stop the lag/stutter until caught up)

Video:

Additional info:
The issue seems to only happen when Nomad is not the active window!

If I am tabbed into any other window besides Nomad Sculpt (i.e. Firefox browser) and I use the pen to hover back into Nomad, the same thing will happen. It lags and doesn’t function for a little while. Switching to mouse does also not make it work again. I just have to wait it out. If I were to tab into nomad BEFORE using my pen, it will work.

WinInk issue

(I think this specific WinInk issue might not happen on Wacom tablets, but I have none to test this. I’ve had WinInk issues in the past, so this might not be a Nomad Sculpt issue! I am just reporting as to why I’d rather have WinTab than WinInk.)

This WinInk issue will ONLY happen with these settings:
WinTab = OFF & WinInk = ON

I don’t like using WinInk for now, because it usually interferes with zBrush and Photoshop. Leaving it disabled is a must for me because otherwise both programs will have issues with pressure. I can disable/enable WinInk on a per program basis, so if I need to use WinInk in the future this won’t be too big of an issue.

But as you can see in the video below, a weird pressure bug appears when I use WinInk. You will also see what the default PureRef usability should be, I can drag it across the screen using hold right click like normal. (This only works with WinInk = ON and WinTab = OFF)

  • Any time I start a stroke, you can see it creates a dot at the start of each stroke
  • I start every stroke with the same very low pressure, but for some reason it registers a higher pressure at the start, to then snap back to very low pressure.
  • I forgot to record strokes in the first video, but using WinTab the pressure behaves as expected!

Video:

I hope this has informed you enough, let me know if there’s anything else I can do to test!
I’ve heard developing pressure/tablet stuff is hell on earth, so I hope this doesn’t cause too much trouble haha! I am loving Nomad, but this does make it harder to use sometimes.

So 2 bugs:

  1. changing window context with wintab

  2. initial pressure press with window ink

I’ll see if I can replicate the bug with wintab but if I can’t it will be a won’t fix. I’ll test with pureref.

For 2 I do force a pressure of 100% when the pressure is 0 (there’s a reason behind it). I’ll stop doing that and see if it fixes your issue, but there’s no guarantee as maybe the pressure is really 100%.

I can see WinInk having 100% pressure at the start being a real issue, but let’s see if that fixes the issue!

For bug 1 it happens with every window, just as soon as Nomad is inactive so to speak. Here’s another video where Firefox is selected, and just hovering over nomad you can see the lag, and then clicking on Nomad the issue arrives. But when I click Firefox for some reason it acts like it’s always left clicking? Hard to explain, but you can see it here in the video.
Video:

I think it might be looping a process when a window is selected above the nomad window that interferes with WinTab? (speaking from my very limited knowledge) it’s very strange.

And for some reason WinTab also causes brush menu’s to sometimes take a couple clicks to pop-up, shown here. Doesn’t seem to affect any other menu items though.

Works as expected with WinInk!

Video:

.28 live

WinInk works as expected now!
It no longer causes the 100% intensity at the start! So this makes it very usable for me. You said it had a reason for being 100%, will that be a problem down the line?

WinTab still behaves the same, weird glitches when Nomad is not the active window and secondary windows that take a couple clicks to open.

I can’t test whether the WinTab issue is one from my Huion Tablet or something else. Maybe someone with Wacom can confirm if WinTab is working as expected for them?

For now I am perfectly happy to switch over to WinInk for Nomad, so far everything feels buttery smooth!

It should be fine, but the risk is that some devices return 0 pressure when they don’t actually support pressure. That’s how it sometimes work in browser or in Android but hopefully not on windows.


For the window focus thing I don’t think you are the only one but I don’t replicate on my device. I’ll wait and see if others have the issue.

1 Like