Share curve across all settings

I am trying to understand the behaviour of the tick-boxes to ‘share curve across all settings’ when making a brush preset.

I think that it’s only the curves within a chosen feature (opacity, size or whatever) that get shared. Is this correct?

It seems that ticking a sensor to share its curve, alters all the sensors that are already ‘shared’. Not always what I want!

I’m having difficulties when some sensors are already ‘shared’ but not all.

Does the order in which the sensors are ticked (or unticked) make a difference?
If one curve deals with angle (for tilt) whilst another deals with percent (for pressure) how are the curves shared?

I have tried experimenting but think there may be a bug or two!

I have tried some more experiments and reached the following conclusions: :slightly_smiling_face:

When ‘share curve across all settings’ is ticked for a specific brush preset feature or characteristic (eg. size) then all the sensors for that feature are affected together. The opposite happens when you untick the ‘share’ box. So my concern about trying to share for some sensors but not others, was rubbish.

Unticking the ‘share’ box after it has been previously ‘shared’ can result in some weird curves! So, it might be best to either ‘share’ or ‘not share’ from the start. And not change one’s mind too often later!

If I make a brush preset without ‘sharing curves’ it behaves oddly when I look at the settings later. If I click on any sensor and then click on my chosen one, then my chosen sensor can get a weird curve! Just clicking without changing anything registers as a change in the preset. So I have to hit the ‘reset’ button before actually using the brush. And certainly before making any new changes.

I can see that sharing curves may be useful when sensors are similar (eg. x-tilt and y-tilt) but not so good otherwise (eg. x-tilt and tilt elevation or pressure).

1 Like

Thank you for sharing your research, @MikeAndrews. I’ve been watching this post to see what we can learn from your question.

1 Like

Thanks for your feedback Sooz
:slightly_smiling_face:
I think I fully understand what’s going on now.

The ‘share curve across all settings’ tick-box and the ‘curves calculation mode’ both assume that people might want to control a single brush feature (or characteristic) using more than one sensor.

I don’t imagine this is a frequent requirement. But if it is then there is a problem!

It will work as long as both sensors use the same curve. That is a significant limitation. However it won’t work currently if the sensors require different curves - for the following reason:

When one curve is set up, then setting up a second curve changes the first one! The two curves are not independent even when ‘share curve…’ is turned off!

Under Windows 10 Pro, I just checked this using the current release version of Krita, so the 5.2.6, as well as the 5.2.9-prealpha (git 606eef8) and the 5.3.0-prealpha (git 3001ea5). I can confirm that there exists an issue, but it seems to vary between your and my system, as well as between different versions of Krita.
By the way, you have not named the exact version of Krita you use as well as you did not name the OS you use, this is important information to hunt down bugs.

For me the 5.2.6 and 5.2.9 show the same results, i.e. after adding a third curve, the first manipulation of the three curves causes at least one of the unmanipulated curves to change its curve.

With 5.3.0 this erroneous behavior could also be provoked, but it was only sometimes the same as with the Krita versions from above, and sometimes it was a little different. Should mean: it also shows this error with a third curve, but only sometimes.
There were situations with three curves where I could change any curve without affecting the other curves, whether adding nor removing nodes or moving nodes did change another curve. And I can not tell what is the reason for it sometimes working and sometimes not working.
And then there were times when it needed a fourth curve, but at the latest after adding this fourth curve, the error always occurred after manipulating one of the curves. Also, here I have no idea what is causing this and what is not.

All tests were made using the brushes b) Basic-1, b) Basic-5 Size Opacity from the bundle Krita 4 Default Resources and HNE Bark or Twigs 2, HNE Foothills and HNE Miles away from iForce73’s Environments 2.0 brush collection.

For all three versions of Krita, the following is true on my side: As long as there are only two curves, these can be set up independently, sometimes at the moment a third (fourth)¹ curve is added it “gets out of balance” but at latest at the moment you manipulate one of these curves, this manipulation changes additionally one of the not manipulated curves unpredictably.

It also doesn’t seem to make a difference whether I uncheck the Share curve across all settings box before adding more curves or after adding them, at least I’m not able to tell the difference if there is one.


@MikeAndrews, this means you have just discovered a bug, and therefore you deserve the honor of reporting it on bugs.kde.org. :wink:

If you want, then you can report it as a bug via the KDE-Bugtracking System at https://bugs.kde.org/.

To report a bug, you must register at https://bugs.kde.org/ to gain access to the “KDE bug tracking system”, i.e. “KDE’s bug tracker”. Keep in mind that the e-mail address you use there must firstly be existing / valid and secondly that it can be viewed by any visitor to the site. But the likelihood of your address falling into the hands of spammers there seems to be very low, because the address I used to register with them, I’m using exclusively for access to the KDE bug tracking system and have not had a single spam mail in my mailbox in the years I have been registered there.

You can read what a bug report should look like under Reporting Bugs in the Krita manual (the input mask looks slightly different today), or the User Guide on KDE.ORG, which I like less. Please use the drop-down menus to select the software, i.e. Krita, the version number, the operating system and try to narrow everything down as much as possible using the drop-down menus available there.

Here you’ll find the mask to report bugs in Krita:

https://bugs.kde.org/enter_bug.cgi?product=krita

It might be a good idea to include the link to this topic in your bug report so that the developers can read your findings here.

And after completing the bug report, i.e. after you have sent it, please publish the link to the bug report here in this topic.

Michelist

¹ so to speak, when this threshold value of three or four curves is reached

2 Likes

After playing around a bit with 5.2.6 on Windows 11 Pro, I’d say this is buggy as heck! Even just switching between the sensors, with only 1 activated, will cause some curves to flip wildly.

Some sensors seem to be more prone to error than others, sometimes it seems to depend on the sequence of switching between them and sometimes only editing one curve will cause some other to go out off wack. Overall it’s very erratic and pretty much impossible to find any reliable patterns here.

Because of that erratic behaviour, I also do not think, that there are even differences between systems or versions - or maybe only minor ones.

I haven’t worked with the brush editor for quite a while now, and so only found out about this issue due to this thread. And a very serious issue it is for sure. Guess that this bug was introduced when porting the brush editor to the new framework (forgot how it’s called) a while ago. Obviously the bug wasn’t caught because of its very erratic nature.

Developers: Back to the drawing board!

1 Like

Hi

I have reported the weird behaviour as a bug. Thanks for suggesting it!

The bug report number is 497367 and I have called it “Using multiple sensors for a single brush characteristic can produce weird results”.

2 Likes

Congratulations @MikeAndrews, and thank you for creating your first Krita bug-report.

The link to this report is:

https://bugs.kde.org/show_bug.cgi?id=497367

I added my comment to your report and confirmed that this does not only happen to you, additionally I added a link to this topic in my comment, this way the developers can easily read up what was discussed so far.

Michelist

2 Likes

Thank you for making the bug report @MikeAndrews.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.