SUMMARY I often use lot of postprocessing layers on top of painting, such as levels, collor correction, vignetting, textures on blending modes. These do not display correctly wnen I turn on/off visibility. STEPS TO REPRODUCE 1. Create basic drawing on bottom of layers hierarchy 2. Create group of layers above - set them to passthrough 3. Create some filter layers inside group, use multiple blending modes with opacity masks 4. Turn them off 5. Save file 6. Restart system 7. Open file again OBSERVED RESULT Filter layers do not show correctly, bottom image is unaffected EXPECTED RESULT Filter layers should affect bottom image SOFTWARE/OS VERSIONS Windows: 10 Procesor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2601 MHz, Rdzenie: 4, Procesory logiczne: 8 16GB ram NVIDIA GeForce GTX 960M Bottom line: This is fricken great software! I'm professional with 10 years of experience, and I just started to switching from Photoshop, which became unusable due to increasing number of issues with performance. Keep up great work!
Hi Sewer, Thanks for your report. But I'm not sure I understand you correctly. If the filter layers are both turned off, why should they affect the layer on the bottom? If I try to reproduce this issue, the image is correct again once I turn the filter layers on?
If they are turned off, they should not affect anything. I often toggle them on / off to paint on bottom layer, then preview how it looks with filter layer on top. That is when bug happens - if I turn on filter layers again, they do not show. Would it be easier is I record this behavior on video? Can't do it until next week though.
Hm... It might be best to first try with a nightly build: https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ -- to see whether it's already fixed, because for me the image is correctly recalculated after reloading and re-enabling the filter layers. If it's still broken, a screen recording could be very helpful. And there's no hurry, there's plenty to do for me :-)
Hi, please check with a nightly build if it still happens, then we know whether it is a bug that might only happen on certain computers :)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!