AiDon

Hi, You are right that reverting to the older drivers works fine but Affinity are saying that they cannot reproduce the problem on any of their internal PCs and it is also affecting the production version. I also believe that Capture One is a "red herring" as they have always worked side-by-side until after 442/456 versions of the driver and there are other indicators that the application is affected either by NVIDIA drivers itself or is crashing the NVIDIA drivers: 1 - One such indicator is that using the GTX 1050 as the renderer and opening 4 RAW images results in AP reporting 2 documents being opened whereas, on the same PC and on the same display, using the Intel HD630 as the renderer AP reports 4 documents being opened. 2 - Turning off OpenCL compute acceleration reports 3 documents being opened. 3 - Then drag AP onto the internal display, which is driven by the HD630, results in only 1 document reported as being opened when 4 are selected. And this is the same for both production and beta, obviously I don't have a problem because I can use OpenCL Compute Acceleration and the HD630 as the renderer even though it reports 3 documents being opened. The only issue is screen flicker with that many documents opened but I can use all Personas, Panorama, HDR Stacking etc. albeit a little slower (NOTE: the driver for the internal display is the HD630 and the GTX1050 for the external display)

@Mark Ingram Hi Mark, I know this is an ongoing issue where suggested causes are both NVIDIA and Capture One, but how is it I can open and process a single RAW image but not multiple RAW images at the same time whilst using these settings? On a single image I can use Develop, Liquify and Tone Map Personas but working with more than one image still causes a Stack overflow in nvwgf2umx.dll :

At the moment, as this has persisted since v442.xx of the NVIDIA drivers, the only options we have are to use either a integrated GPU as the renderer ... or WARP if you don't have one.

Hi Mark, I wonder if it is an issue with vRAM usage because I can now get it to work using Low Quality, or are you optimizing memory first? I have seen in other applications that using vRAM optimization can cause issues like this. Maybe we should be able to designate and allocate the amount of vRAM to use, say High, Medium or Low? A better description may be Fast Preview, Accurate Preview? Regards, Don

Hi Mark, @Mark Ingram After further investigation I have found that adjusting the Retina Rendering to Low Quality allows me to Open multiple images (except for uncompressed ARW RAW), perform Panorama and HDR merge using Hardware Acceleration, setting the Windows Settings (Graphics Settings) to the High performance NVIDIA GeForce GTX 1050, and the renderer to the same. Why should the Retina Rendering have any effect on Windows? (I thought it was Mac only) It seems there are 2 avenues to check, uncompressed Sony RAW processing and Retina Rendering.

Hi Mark, I have done that and a clean install but this is an ongoing issue since v442.xx of the drivers

Hi @Mark Ingram Just checked the latest beta (834) and no matter what image is opened (TIF, JPG, JPEG) the app crashes before the image is opened. Note I am on the latest NVIDIA driver (457.30) and the settings in my Performance sections is: The error is the standard ... Unhandled exception at 0x00007FFEFDA76CC8 (nvwgf2umx.dll): 0xC00000FD: Stack overflow (parameters: 0x0000000000000001, 0x0000003C16109000) Now, here is a description of the issues faced (Note: Hardware-accelerated GPU scheduling is set to Off): My PC has dual GPUs the symptoms are: * Setting the Windows Settings, Graphics Settings to "Let Windows decide" means an immediate crash each and every time the app is opened * Setting the Windows Settings, Graphics Settings to "High Performance, NVIDIA GeForce GTX 1050" means I can open single images only, crashes on multiple images, Panoramas and HDR * Setting the Windows Settings, Graphics Settings to "Power Saving Intel Graphics HD630" means I can open single images only, crashes on multiple images, Panoramas and HDR ** But changing the Renderer to Intel HD Graphics 630, but using setting the Windows Settings, Graphics Settings to "High Performance, NVIDIA GeForce GTX 1050" everything is OK. 1c8486e6-a097-4e77-a55f-10374539649a.dmp

Hi Chris, Just FYI I have never had Windows Explorer Integration enabled in Capture One and I have had this problem since 442.xx drivers with AP. Regards, Don

No problems, it is a Beta after all 😉

Ok, thanks Patrick.

Also resize canvas crashes...

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, The Sony FE 20mm f/1.8 G comes with an embedded lens profile in the RAW images. Is it possible that we have a option to select a embedded lens profile for camera/lens combinations that have them? It would be a lot faster to select the embedded lens profile, if one is there, than waiting for the LensFun database to update. The other thing is that the lens is identified correctly but there is no option to select a lens profile embedded in the RAW file. Note that many cameras embed lens profiles now, for example FujiFilm, 4/3rd's, Sony Canon etc. Regards, Don

Hi Gabe, 456.71 is the latest but this is still an ongoing problem.

Just check what renderer you are using, if it is a NVIDIA GPU change to an alternate one (if you have one on the PC) or set it to WARP.

Affinity is having a problem with NVIDIA GPUs, go to Edit, Preferences, Performance and click on Renderer and change that to either WARP or the iGPU if you have an integrated GPU as well as the NVIDIA GPU. Then Close and Restart.

Thanks Mark, I understand what you are saying but if I set the performance to this it is OK for rendering and hardware acceleration: But it is also interesting that using this setup the Benchmark is: But with the NVIDIA GTX1050 as the renderer the Benchmark is different, which don't really seem to add up: But I must add that I have no issues with other products using the OpenGL or OpenCL on the NVIDIA or Intel GPUs, also no problems using Hardware Acceleration but the Intel HD630 is usually way slower than the GTX1050 so there is a little difference here.

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

I think he is right as the bottom left corner which is input, in the AP case, should be (min, min) (0,0) and the top right which is output (max, max) (1,1) rather than bottom right (1,1) as it is showing (1,0) for the top right which would intimate 1 for input and 0 for output. Maybe don't use X & Y but Input & Output instead.

Thanks Chris, it was just to give you a heads up as it is a general issue with Nvidia drivers at the moment where Affinity doesn't play well except with really old ones. I have a Intel HD630 I use as the primary renderer but it would be nice to be able to use the Nvidia GPU as it has dedicated vRAM. 😉

Hi Chris, You may want this dump as this is a new error using NVIDIA GTX 1050 as a renderer on a dual GPU machine I get this error stitching a panorama, latest driver v456.71: Unhandled exception at 0x00007FFD61156418 (nvwgf2umx.dll) in dmp (0xC00000FD: Stack overflow (parameters: 0x0000000000000001, 0x0000003877829000)). 3015d475-6cb4-4565-8778-10a63cf97f70.dmp

Hi Mark, On my PC the Intel HD630 drives the internal monitor and the NVIDIA GTX1050 drives the external monitor. The crashing occurs on the external monitor with the preferences listed above but if I move AP back onto the internal monitor and set the following Preferences it does not crash ... bit of a quandary though as the external is 24" and the internal is 15" So I don't know if it is because of the Drivers or the fact that OpenCl v2.1 NEO is used by the HD 630 and OpenCL v1.2 CUDA by the GTX1050.

Hi Mark, Yes they are with the NVIDIA v456.55 and the INTEL HD630 v27.20.100.8783 ... I wonder if it is an issue with both GPUs being listed (used) as being enabled for OpenCL compute acceleration. Other apps that use Open CL tend to use the one GPU for acceleration because OpenCL is different versions on the HD630 and the GTX1050.

Hardware Acceleration still crashes with NVIDIA GPU (GTX1050) Unhandled exception at 0x00007FFBAA6653F8 (nvwgf2umx.dll) at 0xC00000FD: Stack overflow (parameters: 0x0000000000000001, 0x0000006008229000).