Jump to content
You must now use your email address to sign in [click for more info] ×

masks and opacity issue


Recommended Posts

when using a mask, and reducing the opacity of the mask, this will always recude the opacity of the underlying layers, instead of increasing. This behaivior does not make any sense to me.

Masks are used to filter out unwanted parts. When you reduce the mask's opacity, you want to (temporary) reveil the hidden parts again. You can disable a mask only completely, but in many cases you want to reduce only the power of the mask by e.g. 50%, meaning black pixels in the mask should act like 50% gray when the mask's opacity is set to 50%.

 

In the moment, i found only a complex workaround: adding a curves adjustment to the mask, select the "alpha" channel, and lift the left node from 0 to e.g. 50%. This requires several mouse clicks, and works only if the mask is not nested, because Photo does not allow to add layers to masks when a mask are already nested.

 

To summarize: If i set the opacity of a mask layer to 50%, this should show an effect equivalent to an alpha channel curve layer to the mask, where the lower left node is set to 100% minus opacity.

 

The attached file shows the results of Affinity Photo when setting the opacity of the mask, or the underlying layer to 100% or 50%, and the simulated result i would expect. To be honest, the reults are really confusing to me.

 

Same results with AP 1.7 and 1.8 beta.

mask opacity bug 2020.afphoto

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

  • 2 months later...
  • Staff

Sorry.

Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script.

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build.

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.