Inpainting brush bug when some FX functions applied

[DigitalStirling]

Hi

I came across a strange behaviour and after checking everything I know and came to the conclusion that it must be a bug. 

My setup:

• Dell XPS 8920
• Intel i7-9700
• 64GB of RAM
• Windows 10 Pro on the latest patch release (22H2)
• Affinity Photo v2.3.0 (but reproduced bug on another device that is on v2.0.0)

How to reproduce (please see the mockup Affinity Photo file):

• Go to Pixel Layer
• Use Inpainting Brush
• Try to repair a bubble
• You will see a dark black spot instead of the repair (see attached screenshot)
• Now go to the top Rectangle layer
• Remove the FX Outer Shadow
• Go back to the Pixel Layer
• Try to repair a bubble
• This time, it works ok

So it appears that the issue is directly linked to some of the FX functions of the mother layer (tried a few, some don't have the issue, but Outer Shadow & Outer Glow do). 

Thanks for your help.

Kind regards

Phil

Test File Inpainting Brush Bug.afphoto

[Ron P.]

In your example file, move the Pixel Layer outside the Group and to the top of the Layer stack. The inpainting brush should work now.

[Gnobelix]

I think the layer (pexels-lumn-1028600) needs to be rasterized, then Inpainting should work.

 

Cheers

[Ron P.]

1 hour ago, Gnobelix said:

I think the layer (pexels-lumn-1028600) needs to be rasterized, then Inpainting should work.

 

Cheers

No, I tried that before I last posted. The Pixel layer needs to be at the top of the Layer stack, if the OP is using a blank pixel layer for removing items.

[Gnobelix]

5 minutes ago, Ron P. said:

No, I tried that before I last posted. The Pixel layer needs to be at the top of the Layer stack, if the OP is using a blank pixel layer for removing items.

Thanks for the explanation.

 

Cheers

[Ron P.]

Video illustrating this. I don't know why just moving the Pixel layer corrects it, or better yet why the Inpainting yields the black if it's not.

[Dan C]

Hi @DigitalStirling,

Thanks for your report!

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

[DigitalStirling]

Hi guys

Sorry for the slow response, been a bit swamped with work, but eventually found time to look into this again. 

Thanks @Ron P., @Gnobelix and @Dan C. The Affinity forum is really great, all very helpful people. 

I used Ron P's approach as a workaround, does work.

But still, it is a bug, so it is nice to get it confirmed by @Dan C. Thanks for the acknowledgement. 

Cheers guys

Happy Affinity user
Phil