Alex_M

Thanks for the suggestions, @NotMyFault. I don't have hardware acceleration enabled. Please find attached a cropped version of the EXR. Please note that this issue appears with every 3D rendered EXR image that I've tested so far. exr2_cropped.exr

Hi, I have a 3D rendered image saved as a floating point EXR. When I convert it to 8-bit or 16-bit in Affinity Photo, I get nasty image artifacts. Please check the screenshot below. If you need it, I can send the EXR file to Affinity support staff privately.

This works flawlessly! I spent so much time trying to figure out how to export my ACEScg EXRs to 8-bit until I found your suggestion. Thanks!!! I have no idea why this process is not automated when switching from 32-bit to 8-bit in Affinity Photo.

I don't want to trim my layers when rasterizing them. I have to keep them intact. BTW, no official response from Serif?

Hi @Gabe, Any updates on this? I am still facing this issue on a daily basis, sometimes costing me a lot of work because I didn't know a layer got blurred along the way. This is a serious issue which has gone unfixed for a year and a half now. I'm astonished that this bug has not been fixed yet. Why is nothing being done on this?

I have a particular document which if I resize, AP hangs indefinitely and starts filling up my RAM and using 100% of my CPU power. The document is very simple and consists of a single layer. You can download the afphoto file here: https://we.tl/t-eOdkKecBex

I found an amazing open-source AI powered inpainting tool called LaMa. Is it possible to integrate this into Affinity Photo?

Thanks, Lee!

Hi, I can't export a photo I'm working on currently to a PSD format. I get the following error message: "An error occurred while exporting to:<my desktop path>". I can export to any other format just fine. Please see attached a simplified version of my document which still gives an error. cant_export_psd.afphoto

Sorry for the late reply. I don't have a G-sync monitor.

Alright, got it. Thanks!

Can I prevent that so that colors don't change and how? I'm not using live filters. Erase White Paper filter only applies to the selected layer.

Hi, Whenever I overlay a layer that had "Erase White Paper" filter applied on it, it changes the colors of the underlying layers. Please check the attached file. Try turning the top layer on and off and notice how the original photo changes colors. Is this normal? How can I prevent this? orange monarch butterfly.afphoto

The 3090 is used for 3D rendering so not having it driving the displays increases the performance.

I don't even know what this is. So I guess probably no? If my quick internet search findings is to be believed, I can enable/disable this through the Nvidia Control Panel through the "Configure Surround, PhysX" menu, yes? The "Span displays with Surround" checkbox is disabled. So I think it is disabled? Please see screenshot below.

Thanks for the feedback, Ron. It might be my particular hardware, software and driver configuration.

Turn on "Snap windows" in Settings in Windows 10. It's in the "Multitasking" panel. Then make sure all 3 checkboxes below are active and try again.

Hi, I would like to report a bug. When I move the Affinity Photo window from my main monitor to my 2nd monitor and then back to the main monitor, the whole Affinity Photo window goes completely black. Steps to reproduce: Connect 2 monitors. Open Affinity Photo on your main monitor and make sure it's maximized. Drag the Affinity Photo window to the 2nd display and make sure that the mouse cursor is touching the top of the 2nd display before releasing the mouse button. Repeat step 3, but on the main monitor. Affinity Photo goes completely black. This issue doesn't occur if I drag between monitors and releasing somewhere in the middle of the display. It only happens when the mouse cursor is touching the top of the display upon release. Also, this issue didn't occur with pre 1.9 versions of Affinity Photo as far as I remember.

I don't mind that it won't perfectly preserve the aspect ratio. I'm fixing it manually anyway by unlocking the pad and rounding down manually every time I resize something. However, this is only wasting my time as I have to do it every time I resize a document. Are you saying that there's no way to make it round down to whole numbers? What purpose does this fractional document size thingy serve? It only causes me problems like thin white/transparent bars on images.

Thanks for the reply. I'm using pixels. Values doen't really matter since this happens with pretty much all values I enter and with every document I want to resize. See an example below. You can clearly see that if I set the horizontal resolution to 2500 px, Photo sets the vertical resolution to 1889.6 px instead of rounding down to the closest integer which should be 1890 px. I don't want this. That's exactly what I've been doing to work around the issue. It's getting a bit tiresome though to do this over and over every time I resize.

I've noticed that Photo uses fractional pixel values when resizing a document. This creates issues with my images like thin white/transparent lines at the borders. This is not good. Can I make Photo round the values to whole/integer numbers?

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.