I just installed the 2.9.7.3.msi and am getting the MD5 mismatch dialog listing out all of the pre-built brushes at each program launch. Also all of my custom brushes have lost their associated tags, tagging in generally has always seemed to be a bit buggy though and usually taken a multiple tries to actual stick.

I am also getting the crash if the single snap is turned on with assistants.

the MD5 check failures were for the Concept Art and Illustration brush pack by Pyteo re-downloading the pack didn't resolve the issue but removing the two associated bundles and deleting them from the app data folder resolved that one.

Tagging still takes a few tries before the tag actually gets applied permanently rather than for just the current session.

The single snapping feature check box causes consistent crashing on my end with 1 to 4 linear assistants on the page, usually have a vertical and horizontal assistant and occasionally 45 degree assistants.

I narrowed down the crashing it happens to loaded files that contain assistants deleting the assistants and redrawing then gets rid of the crashing. Same behavior for files created with this version as well assistants not created in the current session crash Krita if single snapping is turned on.

For the MD5 issue, I just worked with someone else with that same brush pack. There is something with that bundle that is giving issues. I tried another bundle (David Revoy's) and that appears to work fine. There have been some changes recently with how bundles are created and managed. The developer that worked on it is aware of this issue. That bundle cannot be used right now.

We (developers) either need to figure out why that bundle is giving an issue, or the creator of that bundle needs to create a new one with the new version of Krita.

Good catch with the assistants loading and crashing. I have heard of that before, but did not know it also has to do with loading of assistants. Thanks for the information.

Can you try with the latest build? We're at .5 now...

donnieb wrote:I narrowed down the crashing it happens to loaded files that contain assistants deleting the assistants and redrawing then gets rid of the crashing. Same behavior for files created with this version as well assistants not created in the current session crash Krita if single snapping is turned on.

I fixed this one just now.

TheraHedwig wrote:"...." I fixed this one just now.

you all are awesome

boudewijn wrote:Can you try with the latest build? We're at .5 now...

installing it now. So far so good custom brush tags made prior to the upgrade are still applied after the upgrade. Opening files that contain assistants no longer crash with the snap single option selected.

For wolthera's fix, I need to make yet another build, but I'll wait a day for that, maybe we'll accumulate some more fixes in the meantime

i'm getting strange stepping when i make quick or slow strokes, i didn't notice this happening before i updated. I thought it might be the spacing but its not.

I have used default block and default basic_circle , but its on all brushes. and yet again, all my tags got messed up.



edit: oops, forgive me, it appeared to relate to "stabilize sensors" checkbox being turned off. Brushes being missing from tags still an issue here though.

Good day. If I move or scale the tab, color picker bugging right away. Version 2.9.7, Win7,gforce560Ti, i5

I've fixed that last Saturday. I'll make new builds this evening.

Thank you for your hard work, mates.

2.9.7.6 is up now with the following fixes:

* BUG:352238 Re-enable the color picker in the palette docker
* BUG:352253 Resize the color selector triangle's cache so the repaint error is gone
* Fix a crash in the painting assistants with certain files.
* BUG:352261 Don't crash in the box filter when scaling down to small sizes
* BUG:352283 Enable the anti-aliasing option for contiguous selection: If you switch anti-aliasing off, it will threshold the selection, so every pixel that's even a little bit selected will get fully selected, making for a 'hard' edge.
* The general options are now in tabs because the dialog was getting way too big.

On Kubuntu opening a RAW file (cr2) causes a RAW plug-in to pop up.

Not so on Windows ... not sure if this is by design or due to OS limitations.

Using Windows 64 and latest build (2.9.7.6 - have also tried 2.9.7.3 and 2.9.7.5).

There seems to be an issue with either libraw or libdcraw or libkdcraw (not sure which).

The RAW decoder on Windows 'digikam' pops up okay, but not with the latest demazing
algorithms (DCB, Amaze, etc).

I could probably be tempted into trying to buld on Windows x64 if that might help?

No, we don't build the raw import filter on Windows. It needs some extra libraries that I haven't built yet. And our raw import filter is so old and unmaintained, that I am sort of hesitant to put in the time. It's better to use another tool to process raw files.