Annoying behaviour in all Affinity Photo versions

[JeffreyWalther]

Hi,

I really often work on RAW pictures and I come across some annoying behaviour in Affinity, which shall be fixed in an update:

• If I want to stop working on RAW development without saving, you have to cancle the process by 2 clicks before you can close the project.
  I.e. you are asked 2 times before you can close the RAW file. This sucks. I just want to close the windows by x, say [no saving] and done.
   
• If I made my adjustments in the RAW development, I can save it as a preset. But for no reason it does not save the whitebalance checkmark.
  So I have to re-check it again. Every time after I load the preset. And in Affinity 1.7 it seems that the WB value is not properly saved as well.
  It just sticks to the last set value. This sucks.
   
• I don't like that all development settings cannot be saved in one preset.
  I.e. sharpness is separated and I have to use a second preset to load it every time for each picture. This sucks.
   
• Affinity has problems with GPU cards (Nvidia GTX). GUI is flickering while operation.

Maybe these stuff could be fixed? Thank you.
Jeff

[Gabe]

Hi @JeffreyWalther,

On 7/31/2019 at 3:57 PM, JeffreyWalther said:

If I want to stop working on RAW development without saving, you have to cancle the process by 2 clicks before you can close the project.
I.e. you are asked 2 times before you can close the RAW file. This sucks. I just want to close the windows by x, say [no saving] and done.

You only get one message when you press "Cancel", not two. 

On 7/31/2019 at 3:57 PM, JeffreyWalther said:

If I made my adjustments in the RAW development, I can save it as a preset. But for no reason it does not save the whitebalance checkmark.
So I have to re-check it again. Every time after I load the preset. And in Affinity 1.7 it seems that the WB value is not properly saved as well.
It just sticks to the last set value. This sucks.

We are aware of this issue. The white balance adjustment is not applied from the preset. If you tick it, it will apply the way it was saved, but the sliders are at the default position instead of where they should be.

On 7/31/2019 at 3:57 PM, JeffreyWalther said:

I don't like that all development settings cannot be saved in one preset.
I.e. sharpness is separated and I have to use a second preset to load it every time for each picture. This sucks.

I suggest you post this in feature requests as it's not a bug. 

 

On 7/31/2019 at 3:57 PM, JeffreyWalther said:

Affinity has problems with GPU cards (Nvidia GTX). GUI is flickering while operation.

Which GTX? What do you do when it flickers? Are you running the latest drivers? Can you attach a screen recording of this issue in action? 

Thanks,

Gabe. 

[Mark Ingram]

3 hours ago, GabrielM said:

You only get one message when you press "Cancel", not two. 

No, you get two. The first prompt asks if you want to cancel Develop, then the second click actually closes the document.

[JeffreyWalther]

On 8/2/2019 at 2:34 PM, GabrielM said:

Hi @JeffreyWalther,

You only get one message when you press "Cancel", not two. 

We are aware of this issue. The white balance adjustment is not applied from the preset. If you tick it, it will apply the way it was saved, but the sliders are at the default position instead of where they should be.

I suggest you post this in feature requests as it's not a bug. 

 

Which GTX? What do you do when it flickers? Are you running the latest drivers? Can you attach a screen recording of this issue in action? 

Thanks,

Gabe. 

Whitebalance: So, if you was a wedding photographer having 300 pics to be developed, you really would tick WB each time after loading the preset? Sounds like unneeded efforts.

GTX: It does not matter if GTX or any Quadro card or with new or the old drivers. It is a behaviour seen on notebooks having an intel graphic card and an additional GPU. If you open Affinity with the NVidia GPU you get that flickering, i.e the background color of the GUI starts flickering while working, e.g. when zooming in and out the canvas.

 

 

[Gabe]

We did have somebody fixing this issue by completely uninstalling the graphics card drivers and reinstalling the latest ones from the GPU manufacturer's website.