Summary: | Brush color changes after color picking with a noticeable delay | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | katearcher89 |
Component: | Color Selectors | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | dimula73, halla, regulus2626, saranvale |
Priority: | NOR | ||
Version: | 3.0.1.1 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: |
Description
katearcher89
2016-11-25 02:55:12 UTC
Hi Kate, I'm sorry, but I haven't been able to reproduce :-(. But I also don't experience lagginess, not even with 7000x8000 images and a 1000px brush. (Well, not with instant preview enabled.) I'm testing with the latest 3.1 release candidate, which is a bit newer than 3.0.1.1, but I also have never seen it with earlier releases. Hi, At least two other people have reported that they've seen the same issue, so we can confirm. I can confirm. It happens only when Instant preview is disabled and you pick before the calculation of the previous stroke is finished. The problem happens because since recently color picking is a stroke as well, therefore the picking itself is postponed till the previous stroke is finished. Therefore, the global color will change only when the previous stroke has been completed. Added to phabricator: https://phabricator.kde.org/T4879 (In reply to Dmitry Kazakov from comment #3) > I can confirm. It happens only when Instant preview is disabled and you pick > before the calculation of the previous stroke is finished. > > The problem happens because since recently color picking is a stroke as > well, therefore the picking itself is postponed till the previous stroke is > finished. Therefore, the global color will change only when the previous > stroke has been completed. Actually no, in my case it happens regardless if instant preview is on or off. I've turn it on and tried to repeat the steps and yes, it still happens with instant preview on. (In reply to Boudewijn Rempt from comment #1) > Hi Kate, > > I'm sorry, but I haven't been able to reproduce :-(. But I also don't > experience lagginess, not even with 7000x8000 images and a 1000px brush. > (Well, not with instant preview enabled.) I'm testing with the latest 3.1 > release candidate, which is a bit newer than 3.0.1.1, but I also have never > seen it with earlier releases. A little more information about laggy Krita. It turns out Krita was running with default intel HD 530 graphic card(I have two on my desktop, one is nvidia and the other one is intel obviously). And with intel card I experience noticeable lags(which weren't there in krita 2.9.11), but with gtx960 I have no lags at all(no wonder though). Hope this information helps. I would like to add few of my own observations: I confirm: ---------- 1. It happens also for me. 2. It happens with big images. 3. It lags when using color picking via hotkey (alternative invocation of brush tool) 4. Drawing immediately after picking color is impossible, often Krita needs time to apply selected color and puts a stroke with previous color. 5. It happens with instant preview turned on. My own observations: -------------------- 1. Number of layers has direct influence on the lag in my case. 12 layers (filled with random stuff) with resolution 3840 x 2160 creates a noticeable lag in my case (although I don't have a powerful computer) 2. With the same set up (12 layers, res 3840 x 2160) color picking using color selector tool (default shortcut: P) works without any lag. Annoying workaround: -------------------- To pick a color: 1. Switch to color selector tool. 2. Pick a color. 3. Switch back to brush. 4. Paint. Conclusion: ----------- I think the hardware doesn't seem to be the problem in my case. Since color picking using color selector tool works without any problems. Only color picking via alternative invocation of brush tool with instant preview creates the lag. I want to add this info that is helping me: I'm on windows an using full screen mode makes this problem better. It still happens, but more rarely. In my case I see this when working in 16 bit, where I have more performance issues. |