Affinity crashes
Hi. I'm getting fairly reproducible crashes of the latest version of Affinity Photo when merging panoramas or HDRs. I am not alone in this, and the common feature seems to be that most of us are CO users. Affinity Support are laying the blame for this at Capture One's door, as described in this Support thread, for example:
"You might be seeing the nvwgf2umx.dll crash that we have been seeing. This has been typical with HDR merging or Panorama stitching etc. Do you have Capture One installed?"
"We believe Capture One is calling some Nvidia dlls which are in use which is causing Affinity to crash. As far as I am aware, this is something we cannot fix and it's a problem with their Explorer integration."
Comments, please?
-
Just as a test I have just stitched a pano in Affinity and it worked just fine, no crashes. I do have C1 20 installed 13.1.3.13. It must be said that I do have the beta for C1 21 also installed, although I am not sure if this makes a difference. The version of Affinity I have installed is 1.8.5.703.
I do have an NVidia ti1660 graphics card installed. Running Windows 10, latest version.
As for settings in affinity I have set the Renderer to my graphics card at High quality. As for C1, I have Hardware Acceleration set to Auto for display and processing.
There may be some weird set of graphics driver settings causing an issue for some, but it does not seem to be a systematic problem for me.
If you would like to provide a list of steps you took to make Affinity crash I would be happy to try them.
Since the blame seems to be layed at C1's door, it may be worth highlighting this to C1 staff through the Submit a request button at the top of the page..
0 -
I ran into the same problem and got the same feedback from Affinity. I uninstalled CO and panorama worked correctly. I reinstalled CO and the problem seems to have disappeared, I'm not having any more problems. I had just installed the software transitioning from Mac to PC on a new machine, so it wasn't a big deal for me to go through this step. I provided Affinity with feedback from my experience a couple days ago and haven't heard anything back.
0 -
Thanks, folks.
My versions & settings are the same as Mark's in post #2, although it's a GTX1660 card.
I'll raise a support ticket later today.
This does feel like a driver issue, especially because of the instantaneous & complete loss of Affinity when it happens (in my case, after maybe 75% pano create and render operations, and sometimes at the cropping stage as I move a crop handle).
Currently I don't need to do any more panos (or any other operations in Affinity, actually) so I'm inclined to sit this out for now, especially to see if 21 cures the issues.
I've got a 'mature' CO installation (!) so I'd rather not risk disturbing it unless necessary: it's a long time since I had to reinstall - probably back around version 6, which gives an indication of how much more stable the build is these days. If I need to do a reinstall, can anyone remember if there's an option to leave all settings & files intact?
0 -
Maybe my install of the C1 Beta had the same effect as Eric's solution. I think you are right Mark, it does feel like a driver issue or some shared resource clash. I don't do Pano's that often so maybe this issue passed me by.
0 -
Just a data point:
I don't normally use Affinity Photo for Panos (PTGui) but processed a set of 15 Tifs and the used Affinity Photo with C1 still running.
Affinity photo worked without any issue.
My first suggestion whenever a GPU is used is to suggest updating the Driver from the manufacturers web site (not Win Update).
Nvidia do provide for many of their cards a "Studio" driver which is aimed at productivity rather than games. As I understand, the Studio driver allows more of the GPUs memory to be used by applications and does not contain the various tweaks and enhancements added to the gaming GPU to tweak performance in various games.
If you are not using the Studio driver I suggest you give it a try.
Ian
0 -
Yes, thanks Ian. The first thing I did was to update to the latest Studio driver, but it didn't make any difference.
0 -
I just commented on the thread at Affinity Forum about this issue. I habve got the same here on one of three computers - the one with a NVidia graphics adapter. The other machines work fine, On all three machines Capture One is also used.
So it seems it is NVidia-related, probably with their Open-GL pipeline. Lastest Studio driver is installed, doesn't make a difference. Setting hardware accelaration of in Affinity (setting it to warp) stops thoses crashes.0 -
It is supposedly associated with the explorer integration, and I have the same issue but have never had Explorer Integration turned on:
Note these issues have persisted since after the version v442.xx of the NVIDIA drivers, revert to those specific drivers and no issues.
0 -
Just tried it. You're right, Studio driver 442.92 and it also works with hardware acceleration enabled.
0 -
Thanks for the update.
The original drivers I had dated from June '20 and they certainly had the issue. I've noted the roll-back solution and will do that if I need to.
0 -
Well, I might be a bit previous here, but having just installed the latest v21 Capture One, and checked for both nVidia driver (still on the November Studio version) and Affinity updates (none), I ran a couple of the panos that reliably caused crashes previously, and everything was hunky dory.
I'll try some more torture tests tomorrow, but this might now be solved...
0
Post is closed for comments.
Comments
11 comments