AiDon Posted June 18, 2021 Share Posted June 18, 2021 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. Chris B 1 Quote Both PC’s Win 11 x64 System with Intuos Pen & Touch PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB PC2 HP Pavilion - Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GBiPad (8th Gen) 2020 Link to comment Share on other sites More sharing options...
AiDon Posted June 18, 2021 Author Share Posted June 18, 2021 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. Chris B 1 Quote Both PC’s Win 11 x64 System with Intuos Pen & Touch PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB PC2 HP Pavilion - Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GBiPad (8th Gen) 2020 Link to comment Share on other sites More sharing options...
Staff Chris B Posted June 18, 2021 Staff Share Posted June 18, 2021 That's interesting. I know we have spoken to Nvidia recently and they we working with us to figure out the nvwgf2umx.dll crash we were seeing. Perhaps this is the solution they came up with? I will do some poking - thank you. AiDon 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.