Daniel Mikolajcak Posted October 17, 2020 Share Posted October 17, 2020 Hello, why does masked adjustment layer yields different result depending on whether mask is applied directly (correct result) or on the group that adjustment is nested inside. Could it be because I work in 32 bit mode? Quote Link to comment Share on other sites More sharing options...
lepr Posted October 17, 2020 Share Posted October 17, 2020 One of many ancient bugs which appear to be permanent "features". Quote Link to comment Share on other sites More sharing options...
Daniel Mikolajcak Posted October 17, 2020 Author Share Posted October 17, 2020 Hi Anon, weird thing is mine does not get fixed if I change blending mode to normal. Quote Link to comment Share on other sites More sharing options...
lepr Posted October 17, 2020 Share Posted October 17, 2020 30 minutes ago, Daniel Mikolajcak said: Hi Anon, weird thing is mine does not get fixed if I change blending mode to normal. Changing the blend mode from Passthrough to Normal is not a solution. It happened to work for the particular example in that linked thread, where a Pixel object was the member of the group, but it won't help in general. Quote Link to comment Share on other sites More sharing options...
Daniel Mikolajcak Posted October 17, 2020 Author Share Posted October 17, 2020 Do you think it is related to the bit depth? I don't get this artefacts in 8 bit workflow. Quote Link to comment Share on other sites More sharing options...
lepr Posted October 17, 2020 Share Posted October 17, 2020 7 minutes ago, Daniel Mikolajcak said: Do you think it is related to the bit depth? I don't get this artefacts in 8 bit workflow. Are you sure about that? The problem happens in 8, 16 and 32 bpc documents, so I don't understand why bit depth would be making a difference for you. Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted October 20, 2020 Staff Share Posted October 20, 2020 This bug was reported, logged and incorrectly closed as fixed a while ago. I have reopened it and updated it with a new file to display the issue. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
lepr Posted October 20, 2020 Share Posted October 20, 2020 25 minutes ago, Chris B said: This bug was reported, logged and incorrectly closed as fixed a while ago. That could explain the persistence of many ancient bugs. So, do we need to re-report every bug we notice and hope someone at Serif will investigate whether the bug has been mistakenly closed as fixed? Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted October 21, 2020 Staff Share Posted October 21, 2020 18 hours ago, anon2 said: So, do we need to re-report every bug we notice and hope someone at Serif will investigate whether the bug has been mistakenly closed as No. This is not a common occurance. I honestly do not think this is something you need to concern yourself with. Most, if not all ancient bugs just simply have not been addressed. I would argue this was a one-off. lepr 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
PaulEC Posted October 21, 2020 Share Posted October 21, 2020 3 minutes ago, Chris B said: Most, if not all ancient bugs just simply have not been addressed. Maybe, when they are old enough, they will become collector's items! 🤣 Chris B, Old Bruce and lepr 2 1 Quote Acer XC-895 : Core i5-10400 Hexa-core 2.90 GHz : 32GB RAM : Intel UHD Graphics 630 : Windows 10 Home Affinity Publisher 2 : Affinity Photo 2 : Affinity Designer 2 : (latest release versions) on desktop and iPad Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.