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

Masks With Their Own Adjustment Layers Ignored When Grouped (moved)


Hangman

Recommended Posts

I'm not sure if the title is the best way to explain the issue but hopefully the screen recording will demonstrate the problem, it shows the behaviour 2.0.3.321...

Grouped Adjustment Layers v2.afphoto

 

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

Why are you comparing beta versions in the first place? Ther is no current public beta. The regular release versions are the relevant ones to check.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

39 minutes ago, loukash said:

Why are you comparing beta versions in the first place? Ther is no current public beta. The regular release versions are the relevant ones to check.

I'm not sure what you mean when you say there is no current public beta, there is, it's 2.0.3.316 and is the reason for this specific forum, i.e., the macOS Beta Forum.

I tested in 1.7.3 and 1.10.6 which are both fine, I also tested in 2.0.0 and 2.0.0.316 which both demonstrate the issue.

I'm still forced to use 1.7.3 for commercial work because there are still unfortuntatly too many bugs in 1.10.6 and 2.0.0 and subsequently my version of 1.10.6 is still the Beta version as I can't afford to formally update 1.7.3 to 1.10.6 owing to said unreliability and bugs.

I could have reported this in the v2 forum but it seemed to make more sense to report it here since it's still an issue in the latest public Beta so I'm not specifically comparing Beta Versions, I'm making a simple comparison between v1 and v2 (using the set up I have as explained above), v1 is fine, v2 there's a bug.

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

2 minutes ago, Hangman said:

I'm not sure what you mean when you say there is no current public beta

This: 

 

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

5 minutes ago, Hangman said:

I'm still forced to use 1.7.3 for commercial work because there are still unfortuntatly too many bugs in 1.10.6 and 2.0.0 and subsequently my version of 1.10.6 is still the Beta version as I can't afford to formally update 1.7.3 to 1.10.6 owing to said unreliability and bugs.

You can use both: Simply rename v1.7.3 e.g. to "Affinity Photo 173.app", download and install the regular v1.10.6, and both can live happily along. It will even share the same preferences and everything. Or instead of renaming, put v1.7.3 in a subfolder. You can even move it to another volume and launch from there.

For example, I still have v1.8.4 that I bought via MAS installed on a Mountain Lion partition, as those are the last compatible versions for Mountain Lion. From there, they will launch on any of my other bootable partitions up to Catalina just fine:

aff_v184_mountain_lion.png.ab5e25edcdab0c94c7e310d2775ed185.png

The only caveat is that you can't normally launch them with v1.10 at the same time because the executables have the same name. (I think this can be worked around by launching them via Terminal but I'd have to look up how that works.)

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

25 minutes ago, loukash said:

This:

That, I'd not seen (thanks for the link) but the point is mute, the bug existed in 2.0.0 and still exists in 2.0.3...

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

3 minutes ago, Hangman said:

the bug existed in 2.0.0 and still exists in 2.0.3...

Have you also read Patrick's post above?

Quote

[…] The purpose of this beta is to give you an opportunity to try the fixes and report on any possible regressions we may have introduced since the current release 2.0.0. This forums are not for reporting bugs found in the release builds or for telling us what is not yet fixed in this beta.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

4 minutes ago, loukash said:

You can use both: Simply rename v1.7.3 e.g. to "Affinity Photo 173.app", download and install the regular v1.10.6, and both can live happily along.

My point here is that 1.10.6 still has a lot of bugs so I wouldn't even consider using it for day to day commercial work until these bugs are fixed though my assumption is that now v2 has been released they won't be. I can't imagine Serif are going to expend valuable resources in that area.

V2 currently also suffers from far too many bugs to be reliable for commercial work, hence the reason for still using 1.7.3 as it is stil by far the most stable and reliable release to date.

Once the numerous bugs have been fixed in V2 and it proves to be reliable and stable, I will migrate accordingly but I currently have over 3,000 pieces of artwork which I rely on day to day for commercial work and I can not run the risk of issues and why would I when I have zero issues in 1.7.3...

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

6 minutes ago, loukash said:

Have you also read Patrick's post above?

Maybe @Patrick Connor or someone else can move this post then as I've clearly posted it in the wrong forum...

Regardless, the issue still exists in 2.0.3 which was the simple point I was trying to make regardless of posting it in the wrong forum. I think we're going off at a bit of a tangent here now, so enough said...

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

2 minutes ago, Hangman said:

why would I when I have zero issues in 1.7.3...

No problems with that. Why do you think I prefer running my MacBook on El Capitan…? :) 

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

Just now, loukash said:

No problems with that. Why do you think I prefer running my MacBook on El Capitan…? :) 

Well, there you go... 😜

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

  • Staff

I have moved this thread to Photo macOS bugs forum as you have said it affected 2.0.3.321 (as shown in the top right of the My Account dialog)

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

4 minutes ago, Patrick Connor said:

I have moved this thread to Photo macOS bugs forum as you have said it affected 2.0.3.321 (as shown in the top right of the My Account dialog)

Thanks @Patrick Connor, I've also updated the video and description in the initial post to better reflect the issue as it only really relates to v2.

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

Thanks @MEB

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.