I’m on Win 10, latest krita (portable) 4.4.7 release.
Issue:
Fill Layer with custom pattern loaded from a file doesn’t stay after saving krita file and restarting krita and opening the file again.
(I did not move krita, the pattern file or the kra file anywhere, this happens every time)
How to reproduce:
- Add Fill Layer
- Pattern
- Import Reference
- Load your pattern
- Select your pattern
- Ok
- Save file
- Restart Krita
- Fll Layer should still be in Layers but the pattern isn’t visible or even loaded (in patterns selection)
How to get around it:
Add fill layer and load the pattern everytim you open the file.
Does anyone have the same issues, please?
EDIT: It seesm the Krita 5.0.0 solves this issue, at least I can’t reproduce it there. Thanks to halla.
Actually I can’t reproduce it, but if I remember correctly there was such an issue, it was something with subfolders. Is your pattern-file located in a subfolder of Kritas pattern-folder? If so, put it directly in the pattern-folder and try if it solves your problem.
Michelist
No, it’s elsewhere on the HDD completely unrelated to krita itself.
Sounds similar but it’s still a bit different. In my case the pattern isn’t even in the pattern selection so it’s more like it doesn’t save with the file for some reason.
Can you look in the fill layer’s .filterconfig file as noted in Step 8 to see if the reference is malformed? Or have I misunderstood what’s happening?
I get this. the strange thing is that if I reopen it without restarting krita then it loads fine.
After a restart then the pattern isn’t showing on the fill layer.
I checked it (below I just replaced the username, the user name is correct)
<!DOCTYPE params>
<params version="1">
<param name="pattern" type="string"><![CDATA[C:/Users/USERNAME/AppData/Roaming/krita/patterns/DA_S_Oil_Primed DMF cotton mid2.pat]]></param>
<param name="transform_keep_scale_aspect" type="string"><![CDATA[true]]></param>
<param name="transform_offset_x" type="string"><![CDATA[0]]></param>
<param name="transform_offset_y" type="string"><![CDATA[0]]></param>
<param name="transform_rotation_x" type="string"><![CDATA[0]]></param>
<param name="transform_rotation_y" type="string"><![CDATA[0]]></param>
<param name="transform_rotation_z" type="string"><![CDATA[0]]></param>
<param name="transform_scale_x" type="string"><![CDATA[1]]></param>
<param name="transform_scale_y" type="string"><![CDATA[1]]></param>
<param name="transform_shear_x" type="string"><![CDATA[0]]></param>
<param name="transform_shear_y" type="string"><![CDATA[0]]></param>
</params>
I checked the path, the file is there three times now:
DA_S_Oil_Primed DMF cotton mid.pat
DA_S_Oil_Primed DMF cotton mid1.pat
DA_S_Oil_Primed DMF cotton mid2.pat
Just to be clear I’m loading the pattern png image from:
D:/Documents/Resources/PaperRefs/DA_S_Oil_Primed DMF cotton mid.png
I’m not any wiser from this, how about you please? 
I just tried adding a Fill Layer with a standard pattern and that wasn’t visible after a restart either. So yes, it’s different from the bug above.
If you give a link to a bug report I’ll go in and Confirm it - tomorrow probably.
1 Like
Yep, same for me.
I want to correct myself from previously, it seems the patterns are in the pattern menu I just didn’t notice them, there’s 3 patterns now, they just get added with an index as described above.
But the fill pattern doesn’t show up.
I’ll make the bug report but probably tomorrow, I’ll post it here for you.
Btw just now I opened the document after restart and the pattern is there. Go figure. What is going on at this point?
I’ll need to check this tomorrow through the day time, I can reproduce the problem just fine but now I don’t know what happened at the last restart so I’ll double check tomorrow how both of these work.
1 Like
There is a similarity with the bug report above:
The .filterconfig file reference has the same relative structure as the ‘bad’ pattern in the bug report.
That’s for the developers to figure out
Yeah I just found it out, if I add the pattern as I describe above it doesn’t get loaded through the full absolute path but if I open the document after the pattern doesn’t display I can just open the properties of the fill layer, select the pattern I previously loaded, then save the document and on restart everything works just fine.
Here’s the layer filterconfig when everything works just fine, prviously I posted when it doesn’t work:
<!DOCTYPE params>
<params version="1">
<param type="string" name="pattern"><![CDATA[DA_S_Oil_Primed DMF cotton mid2.pat]]></param>
<param type="string" name="transform_keep_scale_aspect"><![CDATA[true]]></param>
<param type="string" name="transform_offset_x"><![CDATA[0]]></param>
<param type="string" name="transform_offset_y"><![CDATA[0]]></param>
<param type="string" name="transform_rotation_x"><![CDATA[0]]></param>
<param type="string" name="transform_rotation_y"><![CDATA[0]]></param>
<param type="string" name="transform_rotation_z"><![CDATA[0]]></param>
<param type="string" name="transform_scale_x"><![CDATA[1]]></param>
<param type="string" name="transform_scale_y"><![CDATA[1]]></param>
<param type="string" name="transform_shear_x"><![CDATA[0]]></param>
<param type="string" name="transform_shear_y"><![CDATA[0]]></param>
</params>
The path is certainly different, for some reason the type and name are now in reverse order, I don’t think that has any influence it’s just a little bit strange if it’s generated the same way xD.
Should I make a new report or just comment to reopen the one you linked above?
It does seem related in terms of the ‘structure/cause’ of the problem.
I’d suggest a Comment with the facts as you’ve observed them then leave it up to @halla to decide how to deal with it in terms of reopening etc.
Ok, I’ll comment it in tomorrow.
Thank you.
I’ve added a comment with hopefully everything, if you want feel free to suggest any changes I hope I managed to sum it up all), if you can please add the confirmation from your side as you suggessted above when you have some spare time, thank you.
https://bugs.kde.org/show_bug.cgi?id=429883#c2
I’ll leave it as is for now and see if it catches someone’s eye at some point for now I guess.
1 Like