Affinity photo quits on panorama

[ntemis]

When i try to stitch panorama with 3 or more photos after the new update, affinity photo quits. I didn't have any problems before. I have attached a dmp file from crash report.

Thank you in advance.

a6146e61-a6eb-40d7-9a61-751c75b26309.dmp

[Abelnt]

same here

5 cr2 (canon raw photos) , affinity makes panorama and go to persona revelado -raw- (in spanish) all is fine . . . but if i move window crash. (old nvidia gt 730 4gb with 2 monitors on udated windows 10)
If i do not move the window and after develop, save the image, nothins happen. If i move the window, crash again.

If i close the program and open the saved image, then no problems and again can move the program window with no bugs. 

[Chris B]

Hey @ntemis - welcome to the Affinity Forums.

You are seeing the nvwgf2umx.dll which is an Nvidia related crash. We have been getting a lot of reports however nobody internally has been able to reproduce this.

Advice is to try updating your drivers or even better, remove and install fresh ones. Or to use WARP when doing a panoarma. WARP is found in Preferences > Performance.

Also, do you have Capture One installed? And more specifically, is Explorer Integration enabled?

[ntemis]

Thank you for your info. I already have the latest drivers of nvidia, so i tried with WARP and it worked. I also have Capture one installed without explorer integration enabled. Do i have to enable it?

[AiDon]

8 hours ago, Chris B said:

Hey @ntemis - welcome to the Affinity Forums.

You are seeing the nvwgf2umx.dll which is an Nvidia related crash. We have been getting a lot of reports however nobody internally has been able to reproduce this.

Advice is to try updating your drivers or even better, remove and install fresh ones. Or to use WARP when doing a panoarma. WARP is found in Preferences > Performance.

Also, do you have Capture One installed? And more specifically, is Explorer Integration enabled?

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

[Chris B]

Well we only seemed to find the link when it was enabled but it may not be necessary. All the Nvidia crashes seem to happen when the user has Capture One installed. We will keep testing.

[samayou]

I'm running into the same problem.  I just installed Capture One and a trial version of Affinity on a new machine (NVIDIA GeForce RTX 2060 Super, i9-10900, 16GB RAM, all drivers are up to date) and it crashed every time I tried to stitch photos together (it didn't matter how many, all .NEF files [RAW files from Nikon]).  I changed the settings to WARP and it's working now.  Not sure how much of a performance loss this causes, but it's much, much faster than the 10-year-old iMac I'm transitioning from so I can't complain too much!  If there's any data I can contribute to the troubleshooting cause, just let me know.

[mamik77777]

Hi, I have a similar crash with 6 DNG images from nikon d3100, affinity crash after panorama creation. It work only changing the GPU acceleration from nvidia geforce gxt 950m to the internal integrated Intel GPU (is a laptop with 2 graphic cards).

Thanks

[Chris B]

@samayou - The issue is with Capture One for you, by the sounds of it. We believe it might be related to their Explorer integration. Did you check this? WARP is considerably slower so you might want to toggle it on/off for now until a proper solution is found. 

@mamik77777 - Do you also have capture One?

[mamik77777]

Yes, capture one 20 pro. But I have disabled the right click integration.

[samayou]

Explorer integration is turned off for me.  I double checked and the box was unchecked, so it's been off since I installed the software.

[Chris B]

I'm not suggesting you do this if it will take too much time, but what if you uninstall Capture One? 

The only link we've found so far is having that software installed.

[mamik77777]

Well, I can deal with the intel gpu or the other stitching method they are fast the same. If you want to test for the fix you can download the 30 day trial. Or install the sony/fuji free version.

[samayou]

14 hours ago, Chris B said:

I'm not suggesting you do this if it will take too much time, but what if you uninstall Capture One?

I uninstalled Capture One, selected the NVIDIA card and panorama worked without any issues.  However, I reinstalled Capture One and it's still working just fine with the NVIDIA selected, so not sure what's going on there.  As a side note, the GPU never gets touched during this process.  I tried the same panorama stitch (25 .NEF files, each about 27 to 30 MB in size) using three different settings: WARP, internal Intel GPU, and the NVIDIA GPU.  All stitched and rendered in the same amount of time, give or a take a second.  The only resources getting used were memory and the CPU.  I'm surprised the GPU isn't be utilized, but maybe this process doesn't require it?

[Chris B]

I think it was using some Nvidia dll's—not necessarily the GPU itself.

That's some interesting feedback though. I wonder why it's working now. I'm off to install the Capture One trial/new beta to see what we can come up with!