Mark Ingram

I'm not sure why it's skipping the device ("(Skipping unsupported device)" in the log file). There are several reasons for this. I'm actually improving this as we speak, so keep an eye on beta updates. For ref: The Intel 620 should be supported.

Hi, thanks for that. I believe it'll be a false positive.

New version available.

Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Changes Many performance improvements for large documents Fixed Trotec JobControl no longer working in 1.9.2 Fixed PDF Import using wrong widths for some accented characters in Helvetica Fixed being unable to type decimals / rational numbers for regions that use commas instead of fullstops Fixed updating a PDF via resource manager resetting Interpret/Passthrough Fixed some font weights remaining in All Caps after toggling them off using the Character Panel Previous release notes

New version available.

Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Many performance improvements for large documents Open FITS files in the main persona and show a Develop FITS panel for single channel FITS files Fixed ISO speed not reported for some images Fixed PDF Import using wrong widths for some accented characters in Helvetica Fixed being unable to type decimals / rational numbers for regions that use commas instead of full stops Added support for Xtrans sensors in Astro Stacking Fixed updating a PDF via resource manager resetting Interpret/Passthrough Fixed some font weights remaining in All Caps after toggling them off using the Character Panel Fixed Sigma 18-300mm F3.5-6.3 DC not being identified Fixed Sony DT 18-135mm F3.5-5.6 SAM (SAL18135) Lens profile not being found automatically Previous release notes

Do you have mouse drivers or software installed?

Your crash is caused by Capture One and the NVIDIA driver. NVIDIA are aware of the issue. The solution is to disable the Windows Explorer integration in Capture One. See here for further details:

@Carbon, try the tool @Komatös has suggested. A BSOD can't be caused by an (user-mode) application, only a faulty driver.

Oh sorry, I saw your comment about an "Nvidia GeForce GTX 1050Ti" and assumed that was the same machine.

Capture One causes crashes in the NVIDIA driver, see the following post for more information:

Ah I can understand how that happens... please file a bug in the Windows beta forum.

New version is available.

Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Changes Added 'Limit Initial Zoom to 100%' preferences option (defaulted to off) Fixed crash on document load when the OpenCLOn12 compatibility pack has been installed Implemented GPOS Cursive rule (used by "Charis SIL" font) Fixed PDF Export group opacity potentially being applied twice Previous release notes

Next version is now available.

Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Added 'Limit Initial Zoom to 100%' preferences option (defaulted to off) Fixed crash on document load when the OpenCLOn12 compatibility pack has been installed Added hardware acceleration to Gradient Map adjustment Fixed renaming a LUT preset to also change the name of the underlying ColourCubeRGB (so it manifests as expected in the LUT adjustment dialog) Fixed F-number always showing in the UI as "f/0" for Leica M-series cameras (and likely others) Render EXIF exposure time as decimal (rather than fractional) if above one Implemented GPOS Cursive rule (used by "Charis SIL" font) Fixed PDF Export group opacity potentially being applied twice Previous release notes

Coming soon... (Keep an eye on the beta forums to try it out when it's available)

That OpenCL kernels compile ~10X slower than in previous drivers.

Changing the renderer to WARP is a work around (WARP is a software renderer, so we recommend using a hardware renderer). If you disable the Capture One Windows Explorer Integration that will also fix it. NVIDIA are aware of the crash.

As I mentioned, there are 2 issues here. One that only affects only AMD Radeon RX 5000 series and later (and as such, we disable hardware acceleration in the application if we detect this card). Any other issue with hardware acceleration is unrelated to this one specific issue (in this thread). I'm not sure what leads to that impression, we develop for both OSes at the same time (and iOS too). Yes, hardware acceleration was available in the macOS builds earlier, but as you mentioned, Windows is more tricky in this regard due to a wider pool of available hardware and drivers. In my previous post I asked you to post a new thread, with some extra information to help us diagnose your specific issue, so we definitely welcome the discussions and the bug reports.

This thread is about AMD drivers, and you're posting an issue about an NVIDIA card, which hopefully you can understand, are two separate things (and off-topic for this thread). AMD have acknowledged the bug I've reported, and are working to fix it. As you're experiencing a different problem, please can you make a new thread so that we can investigate effectively. Please attach your log file (%APPDATA%\Affinity\Photo\1.0\Log.txt) in this new thread. RE: Designer vs Photo. They use hardware acceleration in different ways, so you will likely see differences like this. Finally, if hardware acceleration isn't working, you can disable it in Preferences while we investigate.

Thanks - I've added this info to the following post:

Yes, I use one everyday. I have ASUS ROG Swift PG27U with NVIDIA RTX 2080 SUPER.

Have a look in %APPDATA%\Affinity\Photo\1.0\CrashReports and %APPDATA%\Affinity\Photo\1.0\CrashReports\reports to see if there are any crashes stored. If so, can you upload to the forum? Also, check you aren't using any of the third party software that is known to cause problems: