Bug 440005

Summary: Long Render Time turning Layer-visibility
Product: [Applications] krita Reporter: caeas
Component: Layer StackAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: dimula73, halla
Priority: NOR    
Version First Reported In: 4.4.5   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Animated *.gif to show the behavior
display settings
perf settings 01
perf settings 01

Description caeas 2021-07-18 12:30:38 UTC
Created attachment 140157 [details]
Animated *.gif to show the behavior

Greetings,

whenever i turn a layer visible, it takes a long time to render. It's kinda laggy.
I tried several performance settings, but nothing seems to change that behavior.

CPU: Intel I7-7700K
RAM: 16GB
Graphics: NVIDIA GeForce GTX 1070
OS: Windows 10
Comment 1 caeas 2021-07-18 12:31:51 UTC
Created attachment 140158 [details]
display settings
Comment 2 caeas 2021-07-18 12:32:06 UTC
Created attachment 140159 [details]
perf settings 01
Comment 3 caeas 2021-07-18 12:32:15 UTC
Created attachment 140160 [details]
perf settings 01
Comment 4 Dmitry Kazakov 2021-07-20 09:45:05 UTC
Hi, caeas!

Could you please attach the failing file? Or, if it should be kept private, send it to my mail: dimula73 at gmail dot com.

From a screenshot I see that you have three group layers with attached layer styles and all the groups use "pass-through" mode, which basically disables any possibility of caching. Therefore, every time when you change visibility of the topmost group, Krita has to recalculate several groups with layer styles. It just costs time.

Can you try disabling "pass-through"  of your groups? Or you use it intentionally for some reason?
Comment 5 caeas 2021-07-20 17:04:37 UTC
disabling pass-trough worked to fix that behavior. THx much for that tip.
It was an PSD import before, so it was enabled by default, i didn't done that.
What is "pass-trough" used for?
Comment 6 Bug Janitor Service 2021-07-21 04:33:44 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.
Comment 8 Dmitry Kazakov 2021-07-28 08:59:54 UTC
As far as I can tell, the bug can be considered as resolved now :)