totjoss

I disabled hardware acceleration and tried multiple exports, and didn't get any freeze... for now? Not sure if it actually fixed the issue or if it is just luck. 👀

I don't remember exactly, since the beginning of using my new PC setup, which was in January.

Hello everyone, I'm glad to see that I'm not the only one having this issue. 😅 System totally crashes, only the mouse moving (slowly). In my case it only occurs while I try to export an image. Big or small, one or multiple layers, I can't find any real reason as it happens pretty randomly (1 out of 10). It seems that the preview makes it happen, but I'm not sure. Affinity Photo 2.6.0 (happened on previous versions as well) Windows 11 24H2 Intel Core Ultra 7 265K NVidia RTX 4060 Ti 16GB ----------------------------------------- Edit: I should mention that I also use Affinity Photo 2.6 on a Surface Pro X SQ2 ARM version (Win 11 24H2) and never had this issue.

Alright, I got some news ! I didn't notice that the OpenCL acceleration was turned on, and this is making the UI broken. Not sure if SQ processors support OpenCL or not, but once disabled Affinity Photo gets back to normal. 👍 I did reset everything before trying this just in case.

Oh, I've picked the ARM64 version.

I was unable to update either from 2.3 to 2.4 and from 2.3 to 2.5, after clicking the "install" button an error message showed up. So I've downloaded it from the downloads section of my account.

Hi everyone ! I've been using Affinity Photo on my Surface Pro X (Windows 11 ARM SQ2 16GB) for some time and it actually works pretty well ! At least until version 2.3.1. I had try to update it to 2.4.0/2.4.1 but it resulted to a broken UI (see screenshot below). At that time I thought this newer version wasn't compatible with ARM yet, so I switched back to Photo 2.3.1. The colors, brushes preview, main canvas and navigator preview are all displaying wrong stuff. I supposed Affinity Photo wasn't ready yet — When an update was available, after clicking the "install" button, an error message was displayed telling it was unable to install the update. Thus I downloaded and installed the 2.4.1 then 2.4.2 versions manually but none of them worked. Greatfully when I switched back to 2.3.1 manually, everything got back to normal. Thus it doesn't look like a compromised file on my system. And finally I've seen the announcement of the 2.5 version being optimised to ARM, and thought it was great ! Unfortunately I have the same broken UI as with 2.4.x versions. 😮 I'd like to know if it's supposed to work on an SQ1 or SQ2 chipsets. If not I'd rather go back to 2.3 rather than a fresh install where I have to redo all my workspace settings and reimport all my assets. 😅

Sorry for the late reply, I've downloaded the version 2.1.1 and it is fixed ! 👍 Thanks again !

This is really insane. 😅 @RichardMH I've reset everything, but unfortunately the issue is still there. @Ron P. I agree with you, it's pointless of course. But in any case it shouldn't crash. I could have loaded a picture and resized it. The crazy part is that it only occurs with 256×256 and after a resize, or maybe around this area. I tried bigger or smaller or even not squared and I have no issue. It looks like a floating equation makes it fail - I don't think it'd be an infinite loop as it would freeze the app and not crash instantly. I tried on other computers and I can't replicate the crash either. As it only occurs on my desktop, I tried to test again with most of my background apps killed, still the same. Thus it might be linked to my config which is very old now (13 yo, 1st gen i7 860 + GTX 780). Fortunately it seems isolated and I can use my laptop anyway. Thanks for having tested on your side, but now I don't think it's worth trying to debug it. Except if someone else get the issue someday. 😅

After testing a bit more, it has nothing to do with settings. Neither Retina Rendering nor dither gardients change anything. However, I think I know how to make it crash every single time. This is what I'm doing : - Create a new document (2048×2048 72ppp RVB/8 sRGB transparent) - Resize document to 256×256 (72dpi bilinear resample) - Add an empty pixel layer - Select the gradient tool - Mousedown on the left edge of the document - Dragging to the right edge perpendicularly until it snaps - Hold the dragging and wriggle the cursor slightly as if you were trying to unsnap - At some point it will crash. If it doesn't after 5-10 seconds, retry by making a new gradient again. Weirdly if I don't resize the document, it doesn't crash.

Hello ! Here is the dump for the crash. I'm not sure but it seems to be linked to Retina Rendering as Automatic, as this settings sometimes made my Photo app freeze at some point on the previous versions (with no GPU devices). cb79de49-80ba-4e54-9c5b-f8c44c740160-dump.dmp

Hello ! I'm trying to make a simple gradient picture, but every time I try, Photo app crashes. Step to reproduce: - Launch Photo and create a transparent document; - Create an empty canvas; - Select gradient tool; - Make a gradient, and edit break points colors, then it will crash at some point (sudden app close, no error). Actual settings: - Display quality as "Nearest Neighbor" - Dither gradients checked - Retina Rendering as "Automatic (best)" - Hardware Acceleration (OpenCL) unchecked (as my GPU isn't compatible / GTX 780)

What you're showing is not the same and is not a bug. Of course a document has to be transparent in order to be exportable as transparent. 😉 In my case, you can see on the screenshots that my document is transparent from the beginning, but the matte option doesn't work properly.

That's what I meant by When I click the transparent option, nothing happens, the matte remains white.

Hello ! I've updated Affinity Photo to version 2.1.0 and since then I'm having trouble with exporting a transparent image in PNG. By default the settings will export transparency, but whenever I change any advanced settings (fi. disabling metadata), the transparency is gone. Here is a preview of the issue : And setting "Cache" option to transparent or assigning a profile doesn't do anything. We have to use the "PNG" preset to get transparency back, but every advanced settings will be reset. I didn't have this problem in previous version 2.0.4. Thanks in advance for your help !