Chrismlindley

It depends on its priority. 
Ideally, we'd need to speak with DxO about stuff like this as it isn't always just us that need to change something. I'll be honest though and say the 2.5 glitches have not yet been resolved so communication has dropped off somewhere. 

Hi Chris,
Thanks for the .dmp. I've made our development team aware. I'm not sure if it's worth you dropping DxO a support ticket as well. We have worked with them in the past. 
We still have a few minor glitches that need sorting from 2.5 as well. 

You should end up at a location like this:

To guarantee we get the right one, it might be worth making it crash, then immediately going here to grab the most recent.

Hi again Chris,
I have done this and attached is the .dmp produced after the crash.
I don't know what this file does or means so I will wait for your input once again. Thanks as always.
Best wishes,
Chris
 
ea72ca19-53b6-4273-87b2-176c43876e91.dmp

Hey Chrismlindley,
Have you added Affinity Photo and DxO as safe apps in BitDefender?
My DxO apps for the most part are pretty sturdy but I don't generally use them day to day for actual production work so it's likely I wouldn't typically see the crash you are seeing.
Can you check for crash reports too? The location will depend on the place you purchased Affinity Photo (direct from us or from Microsoft).
%AppData%\Affinity\Photo\1.0\CrashReports
or 
%AppData%\Affinity\Photo\1.0 (Store)\CrashReports
You can acccess the AppData folder by pressing the Windows key + R on your keyboard and then just type %AppData%
 

Thanks Chris, I am at work and will check when I get home tonight. 
 
Best wishes,
 
Chris

Hi Chris,
Welcome to the forums.
 
As you've already created the file all you need to do is open your image and use File > Place. Now browse to your file and click Open. Using the Move Tool you can resize and position. When you're ready you can use File > Export to create a new file that has the signature included, however, during the export, everything will be rasterized.