Leigh

It seems you're having a different issue than that detailed in this thread. Please start a new topic and we'll investigate

Out of date Graphics Card Drivers: Another reason why our apps fail to start or crash on startup is because the drivers for your Graphics Card are out of date. Please make sure that you always have the latest Graphics Card drivers installed for your integrated Graphics Card and any Dedicated Graphics Card you may have installed in your machine. If your machine has both an Integrated Graphics Card and a Dedicated Graphics Card, you can choose which one is used within our apps by going to Edit > Preferences > Performance and selecting the relevant Graphics Card (GPU) from the Renderer dropdown menu. However, if there's a problem with the drivers for the selected Graphics Card (GPU) when you next run Affinity, the app will crash or fail to start. If Affinity is failing to start or crashes on startup and you don't know which Graphics Card (GPU) was last used by the app, press the Windows Key + R to launch the Run dialog and enter the relevant app path: %AppData%\Affinity\Designer\1.0\ %AppData%\Affinity\Photo\1.0\ %AppData%\Affinity\Publisher\1.0\ In this folder you will find a Log.txt file. If you open this file in Notepad you will notice under the Monitors section that the last used Adapter is listed. This is the Graphics Card (GPU) our app is trying to use. Luckily, within Windows it's possible to force our apps to use either your Integrated Graphics Card or Dedicated Graphics Card when you next run the app. Please read our How can I force Affinity to use my dedicated GPU? FAQ for more information.

Even though it's possible to specify which Graphics Card (GPU) is used within our apps by going to Edit > Preferences > Performance and selecting the relevant Graphics Card (GPU) from the Renderer dropdown menu. Sometimes, you may need to use Window's Graphic Performance Preference to force Affinity to use your Integrated Graphics Card (GPU) or Dedicated Integrated Graphics Card (GPU) if Affinity is crashing or failing to start because of out of date Graphics Card drivers. More information can be found here. You can use Window's Graphic Performance Preference in Graphics Settings to force a specific app to use your Integrated or Dedicated GPU. To do this: Open the Settings app and go to System > Display Under the Multiple displays section, click Graphics Settings If you've purchased the Affinity Store version: Select Classic App from the Choose an app to set preference dropdown menu Browse to the location of the Affinity .exe file. For example: C:\Program Files\Affinity\Photo.exe and click Add If you've purchased the Windows Store version: Select Universal App from the Choose an app to set preference dropdown menu Now select the relevant Affinity app from the list and click Add Now select the Affinity app and click Options Your Integrated GPU ( Power Saving GPU ) and Dedicated GPU ( High Performance GPU ) will be listed Select High Performance and click Save When you next run your Affinity app it will use the GPU you've just set within Window's Graphics Settings.

We've had a few users report that when opening RAW files into Affinity Photo on a Surface Pro they appear darker than expected. This issue is resolved by running the Colour Calibration tool within Windows. For instructions on how to do this, please read the following article on Windows Central: https://www.windowscentral.com/how-calibrate-your-pcs-monitor-windows-10

I can only make sure your feedback is passed on to the relevant team, which I will do

Still the same I'm afraid.

Welcome to the forum tromarov Unfortunately, I can't think of way without using a Fill, Boolean operation, transparent mask layer or breaking the path to achieve the effect you require, sorry.

Thanks for trying @ssystem and it's sad to learn that it didn't make any difference, sorry. I completely understand your frustration with our app and that you want to spend some time getting work done but if you have any spare time in the future it would be interesting to know if you get the same issue if you change the default language of Windows to English. I'm also tagging our @Affinity QA team for them to have a fresh look over this thread to see if they have any other ideas or suggestions as I can see you reported this issue with the 1.7 beta too.

Thanks for trying - it's disappointing to hear that you're still having the issue with the latest beta build. Our QA team have also tried to recreate your issue using a Korean version of Windows. They tried using the default Windows fonts and your fonts but was unable to replicate the crash. Happy New Year to you too. I completely understand how frustrating it can be when you've purchased an app to get work done but it's not working as expected. We've had other users with similar issues but removing a particular font would normally resolve the issue. You could perhaps try creating a new user account on your machine and see if you get the same issue when logged into the new account. I will see if our QA team have an other ideas and I'm sorry that it's taking a long time to get your issue resolved.

@ssystem Our QA team have looked at your dmp file and as expected, they can see that it's crashing when selecting Fonts but they can't see what's causing the issue. Did you manage to try the latest beta?

@ssystem Thanks for waiting, it's much appreciated. We've not forgotten about your log file. While you wait for this to be investigated further, our QA team have advised me that the latest beta builds include changes relating to Font Loading. Can you download and install it to see if it resolves your issue? It can be found here: https://forum.affinity.serif.com/index.php?/topic/104165-affinity-photo-windows-customer-beta-180526/

@James Ritson provides a detailed explanation regarding the Workflow of RAW files in Affinity Photo in the following thread:

Hi @ssystem - thanks for the .DMP files. I have passed them to our QA team to be looked at. Unfortunately, we're about to close for Christmas, so there might be a delay at looking at your .DMP file. When I have more information for you, I will let you know.

Ok, thanks for trying @ssystem - Can you try and create a dump file from Task Manager instead. When Affinity Photo hangs could you go into Task Manager, right click the Affinity Photo process and select 'Create Dump File' - you will be given a location of that Dump File. Could you then upload that to our Dropbox account. Thank you.

Me again @ssystem Unfortunately, QA have not been unable to replicate the issue too. However, they did mention that the next beta build of Affinity Publisher has some changes to Font Loading. Do you have Affinity Publisher? If not, is it possible to try and create a dump file when the app is freezing. If so, can you please; Download ProcDump from the following link - https://docs.microsoft.com/en-gb/sysinternals/downloads/procdump Extract the files from the zip folder, then create a new folder on the root of your C:\ drive called ProcDump then move procdump64.exe into this folder. Open Command Prompt (cmd from the Run dialog) then type cd\procdump and press enter. now paste the below string into CMD and press enter, then make sure you leave CMD running: procdump64.exe -e -mm -w photo.exe Now with CMD running in the background, launch Affinity Photo and get the app to freeze when going through the fonts. Open the folder C:\ProcDump - hopefully you will have a .dmp file created here that you can upload to our Dropbox folder.

There is a known issue that causes apps purchased from the Windows Store to give the error "The data area passed to a system call is too small" when trying to launch them. This issue is caused by SQL Server and more information can be found here: https://support.microsoft.com/en-gb/help/4073393/fix-the-data-area-passed-to-a-system-call-is-too-small-error-when-you

When you have Enable Dial Support selected in Preferences > Tools you will be able to use the Surface Dial to adjust brush properties such as Width, Hardness, Opacity, etc.. It also supports Canvas Rotation, Radial Blur, and History.

Here's mine:

Thanks for uploading your fonts @ssystem Unfortunately, I've been unable to replicate the issue on my system using your fonts. However, I will pass them to our QA team to see if they can replicate the issue at their end.

It's available online here: https://affinity.help/

@ssystem Thanks for the videos, very helpful. Is it possible to send me all of your fonts so that we can try and replicate it here.

@ssystem Just to confirm, are you still getting this issue using 1.7? Is it possible to record another video of this happening in 1.7?

@tonghong The BSOD crash can resolved by installing the following Windows update: https://support.microsoft.com/en-gb/help/4530684/windows-10-update-kb4530684

Sorry to hear that Pic. We will continue to investigate.

Sometimes Affinity will stop showing results when searching for a topic within Affinity's help on macOS. This issue is caused by Apple's Help Viewer cache not being correctly indexed. To clear the Help Viewer's cache, run the following command in Terminal: killall helpd; rm -rf ~/Library/Caches/com.apple.help*; rm -rf ~/Library/Preferences/com.apple.help* Once you have ran the above command, please reboot your machine. When you next open the help within Affinity please allow some time for the Help Indexer to reindex our help.