Rahora

Unfortunately, I have not noticed the correct functionality since the release of the version ((WIN) that is supposed to be able to do this. At first I thought it was working as it should, but unfortunately it was just because I was making smaller crops and it was overlooked here. Unfortunately, there was a problem when printing, because the aspect ratio did not fit.

I'm sure your sample doesn't have the same ratio at the start and end either. When you have the crop set to the smallest, it's more like 16:9 or 2:1. Try cropping to an even smaller rectangle, that's when the inaccuracy is most visible.

Thank you for your response. I've tried all the "Move Tool Aspect Constrain" settings, but on Shift+Crop in Unconstrained mode and with the default aspect ratio of 3:2, it won't keep the aspect ratio. The only time shift+crop works in Unconstrained mode is if I set the default aspect ratio to square. Maybe I'm misunderstanding the function, maybe I'm doing something wrong, but I thought this function would be the same as in PS. I apologize for my English. Even in this samples, the current aspect ratio is definitely not maintained.

Holding down whilst cropping in the Unconstrained mode constrains the current aspect ratio - Cropping and straightening (affinity.help) Holding down whilst cropping in the Unconstrained mode constrains the current aspect ratio does not work and holding shift results in a "random" shape. Is this on purpose, is it a bug, or is it just happening on my PC?

That's annoying. Nobody wants to deal with it. Even though Affinity was the only program that had a problem in my PC (for example OpenCL in Capture One works flawlessly with ATI) , I ended up selling the ATI RX 6700 XT and buying an nVidia 3060 Ti.

I honestly agree with most of them, and in video editing (especially here) and 3D, nVidia's support is definitely better. I disagree that this is the case with photography programs. I really don't know any other program for photo editing, it was like that, except for Affinity with the latest cards, older ATIs didn't have problems (and maybe they still don't).

I am aware that you know more about the issue and I have no reason not to believe it. However, it strikes me that in other programs I don't have the slightest problem with opencI. The only problem I have is with Affinity, which I regret. For example, in Capture One, opencl functionality is better with ATI than with nvidia, where I sometimes had problems. Well, I'll probably sell the new ATI and buy nVidia again (use Google translator)

The main reason I upgraded to v2 was to trust the fixed OpenCL support with the ATI graphics card (when I upgraded my nVidia graphics card to an ATI, I didn't think how bad I would be in Affinity Photo). Really, everything that v1 can do is enough for my workflow, I would just appreciate the fluidity of the work. I was thinking about getting a refund and waiting "what will happen with the updates" when with v1 this has not been resolved even after a year. But I like Affinity programs, so I'll risk it and wait and hopefully I'll see. Now the work in Photo is acceptable only with OpenCL disabled, but even then, it is not ideal (when I compare it against the old build with an old nVidia card). Translated by Google Translate.

Photo V2... OpenCL can be activated on Radeon RX 6700 XT graphics, but the work in the program is slower than with the option disabled. Just opening a NEF file takes much longer than with the OpenCL option turned off. Likewise, work in the program, tools, brush movement... everything lags :-(. Unfortunately, with the OpenCL option disabled, the program is not fast either, but still better than with opencl enabled. It's a shame, this is the only thing missing for me to be satisfied with the upgrade.