Bug 358428 - [WACOM CINTIQ] No pressure sensitivity
Summary: [WACOM CINTIQ] No pressure sensitivity
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 2.9.10
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-23 14:10 UTC by elfronza
Modified: 2018-05-20 16:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
bug log (499.30 KB, text/plain)
2016-01-23 14:12 UTC, elfronza
Details
krita.bak (8.88 KB, application/x-rar)
2016-01-31 22:34 UTC, elfronza
Details

Note You need to log in before you can comment on or make changes to this bug.
Description elfronza 2016-01-23 14:10:28 UTC
Hello, I am not able to get pressure sensitivity with any brush in Krita 2.9.10 in my Cintiq13HD and in Windows10. I have re-installed my tablet drivers and krita but that didnt solve the issue. The pressure sensitivity works with any other software that I own (Zbrush, photoshop, substance painter), Krita is the only tool that is apparently not working somehow. Can you please help me? Krita is my favorite tool tbh.

Reproducible: Always

Steps to Reproduce:
1.Open Krita
2.Use any brush and press on the screen

Actual Results:  
No pressure sensitivity on my strokes

Expected Results:  
Pressure Sensitivity
Comment 1 elfronza 2016-01-23 14:12:47 UTC
Created attachment 96799 [details]
bug log

Here is my Dbgview log
Comment 2 Halla Rempt 2016-01-23 15:21:35 UTC
Hi,

Could you check whether removing your krita settings makes a difference? 

close Krita
Press windows + r
type "AppData" in the Windows Run dialog and press enter
navigate to the Roaming folder and rename the krita folder to krita.bak
start krita again and check whether it works now.
Comment 3 elfronza 2016-01-23 15:38:59 UTC
IT WORKED!!!! THANK YOU SO MUCH (specially for answering me so fast in a saturday). Have a great day! :D
Comment 4 Halla Rempt 2016-01-23 20:43:34 UTC
Heh, it's not like we're a company with working hours. Volunteer labor for free software here... And we've got a coding/design/planning sprint in my house now, so I was focused on Krita anyway.
Comment 5 Halla Rempt 2016-01-23 20:46:27 UTC
Can you also zip up your krita.bak/share folder (if you kept it...) and attach it to the bug report? Together with the tablet log we might be abvle to figure out what's going on here, because you're like the tenth person for whom krita stopped listening to the wacom tablet after a windows update, where removing the config (which doesn't contain any tablet info...) fixed the issue!
Comment 6 Halla Rempt 2016-01-23 20:48:56 UTC
Oh! And did you reboot your system in between, too?
Comment 7 elfronza 2016-01-31 22:33:51 UTC
Hello, thanks for the attention. it turns out that everytime I restart my computer, the krita.bak solution stops working, which in turn I have to do it again and again, let me upload the latest krita.bak for you,

thanks
Comment 8 elfronza 2016-01-31 22:34:29 UTC
Created attachment 96948 [details]
krita.bak
Comment 9 Halla Rempt 2016-02-01 07:13:53 UTC
Okay -- "wontfix" is the wrong resolution, though, that means that we won't try to fix the bug, not that the proposed fix didn't fix the bug :-). I'm putting looking into this on my todo for tomorrow.
Comment 10 elfronza 2016-02-01 09:03:29 UTC
Hi Boudewijn, sorry about that, I thought it meant that the problem "wont fix" when I try to fix it eheh (went for the wrong semantics). Thanks for the help though
Comment 11 Halla Rempt 2016-06-17 09:23:59 UTC
Do you still have this problem with Krita 3.0? I am afraid I still haven't been able to reproduce, though I have to admit I use my cintiq with the windows 7, not the windows 10 test computer.
Comment 12 Raghavendra kamath 2018-05-20 16:44:20 UTC
Hi Elfronza,

Can you please check if this problem is reproducible in the latest version of Krita.

For now I am closing this bug report , if you are still facing this bug please feel free to re-open this bug report.

thank you