AP 2.2.0: Deleting a preset from the Tones tab in Develop Persona causes crash

[KLE-France]

Affinity Photo 2.2.0

Windows 10 Home version 22H2

Reproducible: Yes

Hardware acceleration: No (graphics card incompatible with AF hardware acceleration)

Occurring using .nef raw files, .dng raw files, and .jpg files (all I'm able to test) EDIT: and with a new file (File > New... > (...) add pixel layer > Change to Develop Persona)

No unusual hardware attached to computer (no tablets, duel monitors, etc.), no unusual programs

This is a new problem that has appeared with the 2.2.0 version upgrade. No other recent changes have been done for my computer.

Trying to delete a preset from the Tones tab in the Develop Persona causes Affinity Photo version 2.2.0 to crash.

Recipe:

Open any of the above file types, go to the Develop Persona if not already there.

Go to the tones tab.

Choose a preset from the Preset dropdown menu.

From the hamburger menu, choose "Delete preset."

On the confirmation dialog, click "Yes."

Expected behavior: AP 2.2.0 deletes preset and resets tab to "Default" preset.

Observed behavior: AP 2.2.0 crashes.

 

[v_kyr]

Provide a crash report ...

 

[Dan C]

Hi @Kerwin,

Thanks for your report!

I can confirm I've been able to replicate this behaviour here (it appears to occur on Windows only) and therefore I have logged this with our dev team.

Interestingky this seems to occur for any Develop Studio preset, and when restarting the app after crashing, the Preset is actually retained.

I hope this helps

[KLE-France]

To v_kyr: In theory my AP sends crash reports automatically (a choice at Edit > Settings > General > Other)

To Dan C: Thank you, and send my pre-thanks to the development team; I know they'll have this fixed in a jiffy.

[Affinity Info Bot]

The issue "[Win] Deleting Develop Preset crashes app, preset is not actually deleted." (REF: AF-318) has been fixed by the developers in internal build "2.2.1.2052".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.