2.9 brushes using fuzzy load funny in 3.0.
Closed, ResolvedPublic

Description

turning fuzzy off on any given parameter, saving, and then turning it on again fixes things, but it's an odd backwards incompatability.


A 2.9 paintop with loads of fuzzy sensors.

The resaved version that loads properly...

woltherav created this task.Jan 5 2016, 3:23 PM
woltherav updated the task description. (Show Details)
woltherav raised the priority of this task from to Normal.
woltherav added a project: Krita.
woltherav moved this task to Krita 3.0 Regressions on the Krita board.
woltherav added subscribers: woltherav, rempt, dkazakov.
dkazakov reopened this task as Open.Apr 28 2016, 1:18 PM

That is a different bug it seems

No, this isn't fixed by the autospace fix, though the scatter on new brushes is fixed by it. It's really a file-reading issue.

Hi, Wolthera!

Can I ask you to attach a failing preset? I tried a couple of Deevad's fuzzy presets, but they work fine :(

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

The failing preset is those two images in the description. kpp files are pngs after all.

Hi, Wolthera!

I tried to reproduce the problem, but I cannot get the "toggle+resave = different brush" problem here :(
Is the problem still actual? Or I should compare exactly against 2.9?

I checked the XML contents of the brushes and they seem not to differ mush. There are only two differences:

  1. The Size/Fyzzy curve is different in the "fixed" preset. But it is also different in XML code
  2. Some of the old Fuzzy sensors have 'rotationModeEnabled' tag, which became deprecated after the recent fixes. But it should not cause any visual glitches...
woltherav closed this task as Resolved.Oct 21 2016, 9:40 PM
woltherav claimed this task.

Yes, this seems fixed now.