Bug in brush options in the texture tab

[erdi12]

Changing the profile in the Texture tab for selecting the brush tips 
cannot be changed with the mouse. After starting the program it may work once, 
but no longer when you select a brush again. Affinity Photo version 2.5

[Hangman]

Hi @erdi12,

This is working for me on both Windows and Mac... I'm assuming you're using Affinity Photo 2.5.3 (just for clarification)...

A screen recording would perhaps help along with the version of Windows you're using and your system specs.

[erdi12]

I tried it on 3 computers. Win11 23H2 with Affinity version 2.5.3 AMD graphics laptop, 
with WIN11 23H2 desktop NVIDIA graphics Affinty version 2.4.2 
and desktop Win10 22H2 Affinity version 2.4.2. 
Affinty version 2.5.x is unusable for me because it contains an essential macro bug. 
The bug described above is present on all computers (version). Screen recording is included.

[Hangman]

Hi @erdi12,

Could you export and then upload that particular brush as a .afbrushes file so we can take a look...

[erdi12]

This behaviour is not Brush specific. It happens with all brushes. I attached the brush.00_Test2.afbrushes

[Hangman]

Hi @erdi12,

Many thanks for the brush... I can confirm the bug...

It is Windows only and only affects changing the profile in the texture tab when More is selected from the context menu... If instead the brush is edited either by double-clicking the brush in the Brushes panel or by selecting the brush in the Brushes panel and then clicking the Edit Brush icon to the right of the brush category the profile in the texture tab can be edited without issue, at least in my testing...

Could you confirm if this is also the case for you?

[erdi12]

Hi, yes I confirmed the behavour. The bug is present when "More" is selected and not present in the context menu. The difference of More and Context Menue is, that with "More" the adjustments are temporarly and in the context menue they are permanent.

[Hangman]

Hi @erdi12,

Exactly... this should now be picked up by someone in the moderation team and logged as a bug...

[Dan C]

Thanks for your report @erdi12!

I can confirm I've been able to replicate this issue here and I've logged it with our development team to be resolved.

I hope this helps