Weird offset squares on images

[MutantPixel]

Excuse me if there is a known fix for this problem, but this is my first time using Affinity Photo (after 30+ years with Adobe) and my images appear to be getting corrupted with odd squares over the images. I am processing ARW raw files from my Sony A7 camera and once processed, if I zoom in or out, the images become corrupted with these weird offset squares. I thought maybe it was just a screen artifact, but they are actually written to any saved files, making the app completely useless. I started with version 2.0 yesterday and upgraded to v2.6.2 when I saw this happening, but it hasn't resolved the issue. I am on Windows 11, latest version, with an AMZ Ryzen 9 9950x and an RTX 2080ti video card. I've attached a video to show what is going on when zooming in and out and then exporting the image as a PNG.

Video file--
https://drive.google.com/file/d/1MMaO5MtKwGQu1WHU9F0IeQB2ZoqxZPBp/view?usp=sharing

[Hangman]

Hi @MutantPixel and welcome to the forums,

If you turn Hardware Acceleration off in the Affinity Photo Performance Settings (which will require you to reboot Affinity Photo), do you still see the same issue when zooming in and out and exporting your files?

[MutantPixel]

If I disable the acceleration, it appears to no longer be a problem. BUT I have not tested it extensively.

[Hangman]

Hopefully, that will prove to have been the issue, but please do report back if you see a recurrence of the problem.

[MutantPixel]

I hope this isn't the solution, to just disable acceleration. After 30 years using Photoshop, I'm betting my future on this app, and I know it doesn't do everything Photoshop does; but I need it to at least work as advertised. I spend $$$ on my system, so it can be the fastest thing around. I'm happy to help try to zero in on the problem so it can get fixed, but just disabling important functionality so the app can work as expected doesn't seem right. 

[walt.farrell]

20 hours ago, MutantPixel said:

I hope this isn't the solution, to just disable acceleration

You might also check whether you're on the latest driver version for your GPU. Many of these problems seem to come from the drivers not implementing the OpenCL functions correctly, rather than from the application. 

[walt.farrell]

1 hour ago, HCl said:

It should support previous version imo.

When the problem is with the code in the driver, not the application, I think it's unrealistic to expect the application to change its code to work around a buggy driver.

And we know that the problem is sometimes in the driver code, because in some cases a driver update has caused problems that users have resolved by reinstalling an older driver version.