Affinity Photo - Crash after rotating, cropping and deselecting Pixel Layers

[ℓurié]

As per title, the app crashes after these steps when hardware acceleration is disabled. You can try it with any Pixel Layers. Notice, it doesn't always happen. When you deselect, you need to find the exact area to replicate it. This bug is also present in previous versions.

 

 

[NotMyFault]

Does the crash happen if you deactivate „automatically lock background layers“ in settings?

[Chris B]

Hey @ℓurié

I have managed to reproduce this crash. I will log it with the developers - thank you.

[GarryP]

11 hours ago, ℓurié said:

This bug is also present in previous versions.

The 2.6.2 beta was superseded by the 2.6.2 commercial release.

Since there is no current beta release, and the beta software you are using could stop working soon without warning, I would recommend using the commercial release instead.

[Affinity Info Bot]

An issue raised in this thread ("Crash after a crop rotation and then clicking away from the image") has now been reported to the developers by the testing team (Ref: AF-6783). Thank you very much for reporting this issue to us.

[ℓurié]

13 hours ago, NotMyFault said:

Does the crash happen if you deactivate „automatically lock background layers“ in settings?

I tried and yes, it makes no difference.

[ℓurié]

13 hours ago, Chris B said:

Hey @ℓurié

I have managed to reproduce this crash. I will log it with the developers - thank you.

Well, thanks to you.

[ℓurié]

13 hours ago, GarryP said:

The 2.6.2 beta was superseded by the 2.6.2 commercial release.

Since there is no current beta release, and the beta software you are using could stop working soon without warning, I would recommend using the commercial release instead.

Sorry but I don't understand what you mean. Previous Beta versions continue to work, even after new Beta versions are released. Obviously in case of bug reports I use the latest version, and the last one came out today. In any case, for now I'm stuck on version 2.4.2 commercial release, since from 2.5 there are bugs that literally prevent me from working.

[Meliora spero]

9 minutes ago, ℓurié said:

In any case, for now I'm stuck on version 2.4.2 commercial release, since from 2.5 there are bugs that literally prevent me from working.

Yes, that’s the sad reality for professional users — the beta versions are like an extra Affinity or a peek into what’s coming, but for serious and commercial work, it’s not possible to use the latest commercial releases, because Serif doesn’t deliver them in usable, stable versions.

Thanks to the terrible file format, I ended up having to move forward with 2.5.7 — no way back now — but like you, I’d much rather stick with the 2.4.2 release version. Serif and Canva can ponder what that means for their brand in the industry, and what their future looks like when serious users can’t update anymore and Affinity is always avoided in workplace discussions for that reason — and many others. A self-inflicted problem from the outskirts of Nottingham.

And are we supposed to wait until 2.7 for some of these issues to be fixed — in exchange for new catastrophic release bugs and quality problems? That’s just unprofessional.

[ℓurié]

1 hour ago, Meliora spero said:

Yes, that’s the sad reality for professional users — the beta versions are like an extra Affinity or a peek into what’s coming, but for serious and commercial work, it’s not possible to use the latest commercial releases, because Serif doesn’t deliver them in usable, stable versions.

Thanks to the terrible file format, I ended up having to move forward with 2.5.7 — no way back now — but like you, I’d much rather stick with the 2.4.2 release version. Serif and Canva can ponder what that means for their brand in the industry, and what their future looks like when serious users can’t update anymore and Affinity is always avoided in workplace discussions for that reason — and many others. A self-inflicted problem from the outskirts of Nottingham.

And are we supposed to wait until 2.7 for some of these issues to be fixed — in exchange for new catastrophic release bugs and quality problems? That’s just unprofessional.

Sad but true.

Even version 2.4.2 is not free from harmful bugs, but for now it's the least bad solution for my needs.