Summary: | Fuzzy Dab ignores curves calculation mode, appears to just use multiply. | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Brendan <abcd_z> |
Component: | Brush engines | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | dimula73, griffinvalley, tamtamy.tymona |
Priority: | NOR | Keywords: | triaged |
Version: | 5.0.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Brendan
2022-11-02 08:00:54 UTC
Hi, thank you for your report. I can confirm with the Krita Version: 5.2.0-prealpha (git 5c98a72) Appimage with Qt 5.15.7 I would be careful about fixing this bug, because judging from the code in here: "KisCurveOption::ValueComponents KisCurveOption::computeValueComponents(const KisPaintInformation& info) const" (kis_curve_option.cpp, line 389) https://invent.kde.org/graphics/krita/-/blob/master/plugins/paintops/libpaintop/kis_curve_option.cpp#L389 it seems like it was a design choice. There are a few types of sensors and apparently Fuzzy Dab, Fuzzy Stroke, Rotation, Tilt and Drawing Angle are calculated separately from the rest. Whole logic was designed and explained here: https://invent.kde.org/graphics/krita/-/commit/159a61263e6d4f7812ba56e38fa29a1a02dcae11 It seems like it might be necessary for values like Hue etc. I'm afraid that is an intentional behavior. Sensor mode is applied only to "scaling" sensors, which are all sensors except of Rotation, Fuzzy Dab, Fuzzy Stroke, Tilt Direction and Drawing Angle. The latter ones are considered "additive" and they just add up to the final value of the option value. I don't think we can change that without breaking sanity of the brush behavior in special cases, like Rotation and HSV values. |