matthiasbasler Posted November 14, 2022 Share Posted November 14, 2022 Presets seem not to work as intended, at least not in the "Develop" persona where I tested them. I created presets for all kinds of RAW development settings. When I now open a new RAW file, AP shows these (last used) presets as active, but they are not. The sliders/settings are at default positions. Switch the preset to "Standard" and nothing happens. Switch back to the preset and only then the settings are applied. Attached screenshot shows an example: I enabled "Improve details", set the values to 20% each and saved the preset. On the next image I can see the preset, but the option is actually disabled, so this state is inconsistent. This irritates, it defeats the purpose of having "quick" presets and makes RAW development with AP slower than intended. Affinity Photo 2.0.0, Windows. Quote Link to comment Share on other sites More sharing options...
Ian Tompkins Posted November 14, 2022 Share Posted November 14, 2022 1 hour ago, matthiasbasler said: Presets seem not to work as intended, at least not in the "Develop" persona where I tested them. I created presets for all kinds of RAW development settings. When I now open a new RAW file, AP shows these (last used) presets as active, but they are not. The sliders/settings are at default positions. Switch the preset to "Standard" and nothing happens. Switch back to the preset and only then the settings are applied. Attached screenshot shows an example: I enabled "Improve details", set the values to 20% each and saved the preset. On the next image I can see the preset, but the option is actually disabled, so this state is inconsistent. This irritates, it defeats the purpose of having "quick" presets and makes RAW development with AP slower than intended. Affinity Photo 2.0.0, Windows. I've noticed this as well on a Mac. I found that I don't have to switch back to "Default"—I can just select the preset again even though it's already selected, and the settings are applied. It did strike me as being a bug, though. Quote Link to comment Share on other sites More sharing options...
matthiasbasler Posted November 15, 2022 Author Share Posted November 15, 2022 Can a moderator please move this ticket in the "Photo 2 Bugs found on Windows" section of the forum. I didn't find the bug reporting forum at first, so I posted it here but now I realize this is subpar. Thanks. Quote Link to comment Share on other sites More sharing options...
pgraficzny Posted November 15, 2022 Share Posted November 15, 2022 This error also occurs in Photo V1. Nathan Shirley 1 Quote Link to comment Share on other sites More sharing options...
Staff Dan C Posted February 4, 2023 Staff Share Posted February 4, 2023 Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm this issue is logged with our developers and I will be sure to 'bump' this with our team now to bring it to their attention once again. I hope this helps Quote Please note - I am currently out of the office for a short while whilst recovering from surgery (nothing serious!), therefore will not be available on the Forums during this time. Should you require a response from the team in a thread I have previously replied in - please Create a New Thread and our team will be sure to reply as soon as possible. Many thanks! 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.