Hi, I've tried to use tilt information for a brush on an Intuos Pro M with Pro Pen 2. Krita seems not to receive anything. I tried with Rotation (to see something). The WACOM diagnosis shows the respective changes in X/Y tilt. For me, this is true for 3.3.3 as well as 4.0.0-beta.1. Let me know, if you need more information. BR Peter
The "Rotation" sensor is not related to tilt, so maybe this is why it seems to not work for you? Use the "Tilt direction" or "Tilt elevation" sensor instead.
This is exactly what I tried: I tried to control the brush tip rotation with the tilt sensor. I've tried X-Tilt, Y-Tilt, Tilt elevation, and Tilt direction. None of these influence the brush tip. I could use ANY other brush tip setting. None is influenced. I also would like to ask not to set bugs to RESOLVED when you raise questions and are not clear about what the bug is really about, i.e., when there's a request for more information. This is a bit confusing. BR Peter
(In reply to Peter Mueller from comment #2) > This is exactly what I tried: I tried to control the brush tip rotation with > the tilt sensor. I've tried X-Tilt, Y-Tilt, Tilt elevation, and Tilt > direction. None of these influence the brush tip. I could use ANY other > brush tip setting. None is influenced. Well, that would be pretty weird. We should check whether Krita can receive the tilt data in the first place. Can you make a tablet log by following the Windows section in https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F ? > I also would like to ask not to set bugs to RESOLVED when you raise > questions and are not clear about what the bug is really about, i.e., when > there's a request for more information. This is a bit confusing. I made the assumption that you might have chose the wrong option, that's why I changed the status to resolved. Anyway, don't think of it as a big deal, it's only a tag. If you follow up with information that's helpful in diagnosing the issue, it doesn't matter what status the bug was closed as.
Created attachment 110986 [details] DebugView log with wintab API The Wintab API log showed an additional aspect: That "the resource could not be saved, because there's no name." This was happening when I chose Overwrite Brush to save it with a rectangular predefined brush tip.
Created attachment 110987 [details] DebugView log with win8 API
I'm currently using 4.0.0-beta.1. (Changed respective bug attribute.)
Tried DebugView. Hope that I used it in a helpful manner. BR Peter
(In reply to Peter Mueller from comment #5) > Created attachment 110987 [details] > DebugView log with win8 API It doesn't look like you have Windows Ink enabled in the Wacom driver, so there aren't any tablet events received here. Perhaps you can retry with it enabled. If you did have it enabled, then there might be a bug with the Wacom driver... (In reply to Peter Mueller from comment #4) > Created attachment 110986 [details] > DebugView log with wintab API Weird, there appears to be no tilt data received from WinTab (xTilt and yTilt values are all 0). My impression is that tilt via WinTab is supposed to work in Krita, but I don't have tilt support and a proper WinTab driver (the surface pro 2017 supports tilt only via Windows Ink) so I'll need to ask someone else to re-check whether it is an issue with the WinTab code in Krita. Otherwise, it might be an issue with the Wacom driver. It does seem a bit unlikely since it reports the pressure levels correctly... but can you try resetting the Wacom config and reinstalling the driver just to be sure? > The Wintab API log showed an additional aspect: That "the resource could not > be saved, because there's no name." This was happening when I chose > Overwrite Brush to save it with a rectangular predefined brush tip. If you suspect it is related to another bug, please do put the information in another bug report. I'm not the right person to ask and the other devs/contributors who may be able to fix it might not see this bug report.
I've just tested on my mobile studio pro with wacom pro 2 pen, and tilt works: I modified an existing preset to have size mapped to x and y tilt instead of pressure and inverted the curve so the flatter the pen, the wider the stroke, and that worked fine.
Yup. Meanwhile I installed Photoshop and GIMP. In both it didn't work. So ... it was not Krita. I now did the following: (1) I de-installed Wacom driver. (2) I installed it fresh from within an admin account (the first install was from a standard user account using Windows run-ad admin). And, yes, it works now. Sorry for this. Next time I go and check first with other apps to not waste your time.
Heh... But on the other hand, wintab drivers are ghastly things that keep persistent per-application state, so sometimes things will work in X but not in Y, and it'll _still_ be a driver issue.