AiDon

Just as an addendum to this I also tried opening a ARW, easy culprit to make AP or AD crash with the uncompressed files, and it crashed AD. So in the GeForce Experience I hit REVERT and then Optimize again ... no more crashes.

Previously Capture One hardware acceleration optimization has seemed to make Affinity Photo crash using the NVIDIA GPUs as the primary renderer.
Recently NVIDIA, via the GeForce Experience application, provides a list of games and apps that can be optimized to run properly with the NVIDIA GPU as the primary renderer. The settings in the GeForce Experience need to be optimized and will end up looking like this:
 
After choosing to Optimize via the GeForce Experience application, note that you need to select the OPTIMIZE button and let it process, I am no longer experiencing crashes using these Performance settings.

I am not sure what the NVIDIA Optimize does but maybe the devs could look at why it no longer crashes even with capture One installed. Obviously I only have a GTX1050 but it may be worthwhile for others to see if it corrects their problems with other GPUs also.
 

Hi all,
We are aware of this issue and it has already been logged with our developers. In a nutshell, ratios are "force-rotated" to the aspect ratio of the document. 

As I mentioned it was only to let you know that AP cannot stitch it but other Apps can. No issue for me because other apps can stitch it 😊 just heads up.

OK, you can download the ZIP from here, it is just for your info as it is a small overlap although CS6 will stitch it:
DropBox: https://www.dropbox.com/s/acdgjgwmlzm708p/A7302366-A7302367.zip?dl=0
Sorry I don't have the iPad version ... I'm waiting to get it. 😉
Don.

For some reason I am no longer experiencing crashes since the v1.9 update and the latest NVIDIA driver.

I am in total agreement with you. I have bumped the improvement report I made. 

Alzheimer or Dementia?

Affinity Products have strange startup setting in combination with Alzheimer from the beginning on ...
The topic is on the list for many years ...

Hi,
One of the things that has been hanging around for a long time is that the crop tool defaults to Unconstrained each and every time. For example, if I crop an image (Develop or Photo) and set the crop to Original it looks like this before I apply the crop:

 
Then if I re-enter the Crop tool to adjust the crop it defaults to Unconstrained:

Could we please have the option to set the default for the Crop tool and that the Crop tool remember the current crop Mode used in the image.
This has been something that many have asked for since the beginning.

Please don't complain about the stability of the beta builds. They are meant for testing, and you should expect bugs. I'll paste the top paragraph that I put into every new beta forum post:
I've commented on Scanner support previously in other threads. Your scanner manufacturer will provide software to import your scans, then you can just import those images / documents. 

Closing, as this isn't a bug report 🙂

This is part of the NVIDIA driver, I assume you may already have tried this, but if not, can you uninstall and reinstall your drivers?

No problems, it is a Beta after all 😉

There's a few regressions here I'm afraid. We're on it—so sorry!

Also resize canvas crashes...

Hi Mark, Getting the following crash on Resizing the Canvas in an image this release:
"Unhandled exception at 0x00007FFB1DFB4B40 (libpersona.dll) in 8de3e970-6cdf-4063-ab18-13e39c03051a.dmp: 0xC0000005: Access violation reading location 0x0000000000000010."
Latest dump attached.
Regards, Don
2b61708c-dea8-45b6-881e-02b0ed4e3666.dmp

Hi Mark, It also seems that downloading Store content then signing out and resetting removes the store content from the application even though it says that the content will remain available in the app, seems to be that Clearing the user Data means the App is no longer registered:
Sign Out:

Clear User Data:

On Restart:

On Restart after clearing the user data this is the message again asking to sign in even though Reset Brushes (don't know it it is significant) is not selected:

 
Regards Don

Hi Mark, Getting the following crash on Resizing the Canvas in an image this release:
"Unhandled exception at 0x00007FFB1DFB4B40 (libpersona.dll) in 8de3e970-6cdf-4063-ab18-13e39c03051a.dmp: 0xC0000005: Access violation reading location 0x0000000000000010."
Latest dump attached.
Regards, Don
2b61708c-dea8-45b6-881e-02b0ed4e3666.dmp

Hi AiDon,
We don't support embedded lens profiles in RAW files. This is more an improvement request than a bug. Let me double-check this internally and i will get back to you in a moment.
[EDIT] We already took a look at this some time ago however without manufacturer's assistance (which we hardly get) it's difficult to implement properly, so for now we will have to rely on LensFun database only, sorry.

We're not Adobe 🙂
Honestly, this was designed as a something that we thought would be good (and helpful) for our users. If you don't like it, you don't have to use it, we're not forcing you to use it (and that's why it is optional).

4178 vs 4164 and 4715 vs 4702 are not statistically different enough, so they're effectively showing no change (i.e. changing your renderer made no difference).

Doesn't seem to be any improvement in the problems with NVIDIA GPUs.

Thanks, AiDon,
All's well since following your advice. Even went back to Beta. Appreciate the help.

Doesn't seem to be any improvement in the problems with NVIDIA GPUs.