Alex_M

That's a bummer. It would be way more useful if undo in these layers took just one step. This is always causing me problems and takes away from the otherwise great user experience.

Why does the undo operation in Photo undo 2 actions at once instead of one? This typically happens when doing undo operation in adjustment layers and live filters. Is this by design? Is there a way I can make it to only undo 1 step? Or maybe this a bug? Example: Create a Curves adjustment layer. Modify the left point. Then modify the right point. Undo. Both points get back to their original location instead of the last one.

It is set to 32768 mb. BTW, does Photo really need tens of gigabytes of RAM to process ~15 RAW images weighing 400mb in total? Is this normal?

Affinity Photo 1.9 hangs when I try to batch convert more than 3-4 CR2 files to JPG at a time. The circles just keep spinning forever. RAM usage also jumps through the roof - 16 gigs (I have 64 gigs so this should be fine). Photo processes them fine if I do only 2-3 CR2 images at a time. Unfortunately, I have to batch convert hundreds of CR2 files to JPG and this is going to take lots of time by the looks of it. See screenshot below.

Hi @Chris B, I appreciate your updates. Do you have new info on this or are you still unable to replicate the bug? I'm really eager to use hardware acceleration but this is a showstopper bug for me. Let me know if you need anything else from me that could help with tracking this down.

I tried a dozen times. It doesn't go any higher than the score I posted.

This dreaded problem, that I've reported in the past, has again made its way back into Affinity Photo 1.9 after being absent for the past year or two. Every now and again Affinity Photo 1.9 won't let me save my documents, thus losing work and redoing everything from scratch. Please check the screenshots below. These are only a couple of instances among several that this have occurred to me since I installed 1.9 a few days ago.

AMD Threadripper 3970X 32-core 3.70/4.50 GhzMSI RTX 3090 Suprim X 24GB + Nvidia studio driver 461.4064GB RAM @ 3800mhz CL14 Windows 10 Pro, Version 2004 Any idea why my GPU results are 10% slower than RTX 3080?

Hi, There's a bug that's been plaguing Affinity Photo for almost a couple couple of years now. I just found that it's still present in the newest version 1.9. Every time I rasterize a pixel layer, it gets blurred if there are Unsharp Mask or blur live filters in the layer stack. Here's my older thread about it.

Hi, Any progress on this issue? The bug is still present in the newest version 1.9. It's been present in Affinity Photo for almost 2 years now.

Thanks. File sent!

Hi @Chris B , Thanks for logging this with the developers. I'm not able to share the .aphoto publicly. Can I send it to you privately?

Flattening a document containing specific live filters causes artifacts when Hardware Acceleration (OpenCL compute) is turned on. The offending live filters are: Vignette, Twirl, Add Noise and Lighting. If I disable Hardware Acceleration, the problem goes away. Please see the screenshot below. I'm using the official release version of Affinity Photo 1.9.0.932. Check my signature for hardware configuration.

Thanks for the suggestion, but this is not really a solution because I want the photos to remain in their original folders. Thanks, I've got to try this out. Still not ideal though IMHO. It needs a proper drag and drop.

Any progress on this? This looks to be a highly requested feature. I do batch jobs quite frequently and it's excruciatingly slow to navigate every single folder by hand in order to collect the images. Right now I'm doing a batch job that requires sourcing 2088 images in 513 folders. This will take me at least an hour when it could be just a simple Windows search and then drag and drop the images in the program. 1 hour vs 1 minute! It's been 2 years or longer since this has been requested by myself and others and still nothing on this front. I can't image it to be THAT hard to implement, is it?

There's still this bug that blurs Image layers when I rasterize them. This happens only if I have an Unsharp Mask layer in the layers panel. Please check the attached screenshots. Notice how the Image layer's dimensions and coordinates change when I rasterize it. This doesn't happen if I delete the Unsharp Mask layer before rasterizing. I'm using Photo version 1.8.4.693.

I've just updated to Affinity Photo 1.8.4 and noticed that the brush crosshair is not centered in the middle of the circle. I could be wrong, but I don't remember this being the case before I updated. It's most noticeable when the brush size is smaller. Please see attached a photo that I snapped with my phone. You can even count the pixel

That's an interesting question. What kind of driver should we use with Affinity Photo as a rule? The gaming or the studio version?

+1 It's extremely sluggish even with a small amount of images. Today I had to batch process 165 images and on my 32-core Threadripper 3970x it took about a minute for the files to appear in the list. Doesn't make any sense. Also, it would be great if you can add a drag and drop feature. It takes ages to source the files by browsing each folder from the batch job window.

Thanks for the help. You are right, when I save a new file, the filesize goes down considerably to the same amount - 100mb. Maybe it would be helpful if there was some kind of a "purge" option that flushes the unnecessary stuff when one is with a project?

I've got not that big of a file (16 megapixels, 8-bit and a couple of raster layers) that after saving shockingly took 700 mb of my disk space. I copied all of it's contents in a fresh document with the same dimensions, saved it again and BAM! - 100mb. What causes this colossal difference in file size when the content is 100% the same? I've noticed this is a persistent problem with Affinity Photo. When I finish with a project, I always have to transfer all the contents in a new document before saving otherwise I'd have clogged up my disk by now. Any way to avoid this or is this a bug?

Still broken in the just released 1.8.3. 😕 Isn't this a major bug that should be absolute top priority? I mean, this is a photo editing program and brushes are used probably 90% of the time. The suggestion above about releasing left click first doesn't work. This bug was introduced when brush Rotation-Width-Shape mode cycling was implemented with ALT+RMB+LMB. So I think the bug stems from there. Is there a way to disable this mode cycling? Maybe this will fix it. I would rather trade this functionality that I never use for properly working brush resizing without teleporting my cursor all over the screen.

Currently, applying a macro changes the current tool to View Tool [H]. Is there a particular reason for this? I think it would be better if the tool I was using didn't change after I apply a macro. I think it's unnecessary and confusing.

Thanks, a lot, @walt.farrell , I'll give it a try! Do you think this can break anything if I restore the original value before updating/uninstalling etc.?

Thanks, but I'm not finding this checkbox. Please see attached a screenshot.