Panorama, crash on Rendering four images

[Woodkopf]

Beta Release                                                                                                      1.9.0.780

File>New Panorama

Add four JPG images to create a Panorama, adds OK., (see 001)

Click Stitch Panorama, looks OK

Click OK, starts to Render Panorama, then Crashes. (see 002)

 

Unchecked Hardware Acceleration in Edit>Preferences, (see 003)

Restarted and carried out same Panorama

Carried out the Stitch OK., (see 004)

Created and exported final jpg

 

Repeatable

 

 

Re-checked Hardware Acceleration in Edit>Preferences

Restarted and carried out same Panorama

Carried out the Stitch OK.

Click OK, starts to Render Panorama, then Crashes (2)., (see 005)

 

Does not create the problem in the current customer release, 1.8.5.703

[Chris B]

Hey Woodkopf,

Thanks for the brilliant report.

We have seen crashes stitching with Nvidia GPU's but AMD is ususally fine. Luckily, I have a desktop with an AMD card but I cannot reproduce the crash.

Would you mind attaching the crash report please?

Go to %AppData%\Affinity\Photo\1.0 (Beta) and rename 1.0 to 1.1

You can acccess the AppData folder by pressing the Windows key + R on your keyboard and then just type %AppData%

It is possible that the panorama function is affected by discrete GPU's and this is why changing the renderer to WARP would also work.

[Woodkopf]

Hi Chris,

Thanks for your prompt reply and sorry for the delay, first chance to get at my emails!

I reset name of folder as requested.  Made sure Affinity Photo Beta had the Hardware Acceleration checked.

Followed the same same procedure with the same jpg files, as previous.   Likewise the render crashed part way through.

Slight difference in the render representation at the crash, please see 006.

Attached todays crash report "ff5bfabe-9579-404c-9309-3438fb4634d8.dmp".

 

ff5bfabe-9579-404c-9309-3438fb4634d8.dmp

[Woodkopf]

3 hours ago, Chris B said:

It is possible that the panorama function is affected by discrete GPU's and this is why changing the renderer to WARP would also work.

I tried changing to Warp, leaving the "Hardware Acceleration box still checked but that failed in the same place.  With Warp but no tick in the box it worked OK and finished the render, giving me access to modify the photo as required.

[Woodkopf]

Sorry Chris,

That crash dump is not relevant.  I have made an incorrect assumption.  It has not crashed, I can still "Apply" the unfinished render, please see "008 Full screen copy of Render problem-20201012.jpg", so as far as Affinity is concerned it is OK?  There is no crash dump.  I can still apply layer adjustments to the partial render?

[Chris B]

Weird. So OpenCL is causing a partial render? Can you attach the .afphoto file that has the partial render please?

[AiDon]

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

[Woodkopf]

29 minutes ago, Chris B said:

Weird. So OpenCL is causing a partial render? Can you attach the .afphoto file that has the partial render please?

As requested, attached "009 Unfinished Render.afphoto"

009 Unfinished Render.afphoto

[Woodkopf]

Hi Again Chris,

I have tried twice more, using the same procedure, this time it has captured some render, I turned on history, hoping it may be of some use?

 

011_Unfinished_Render_(with_History).afphoto

[Chris B]

18 hours ago, AiDon said:

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 3.66 MB · 0 downloads

The cursed nvwgf2umx.dll crash! I can't recall if we've spoke about this before but WARP from Preferences > Performance will solve this (as a workaround). 

[AiDon]

1 hour ago, Chris B said:

The cursed nvwgf2umx.dll crash! I can't recall if we've spoke about this before but WARP from Preferences > Performance will solve this (as a workaround). 

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. 😉

[Woodkopf]

On 10/12/2020 at 3:26 PM, Chris B said:

Weird. So OpenCL is causing a partial render? Can you attach the .afphoto file that has the partial render please?

Hi Chris,

I installed the updated beta - 1.9.0.791, I have checked I have the latest Drivers for my graphics card – ASUS (AMD) R9280-DC2T-3GD5.

I Still have the same problem of partial render when "Hardware Acceleration" is enabled, I have attached another .afphoto file of the failed render.

When "Hardware Acceleration" is not enabled and the Renderer is Default (ASUS R9 280 series)" the panorama render functions normally.

With Warp enabled instead of the ASUS (AMD) R9280 and "Hardware Acceleration" not enabled, the panorama render also functions normally.

What is the difference when using Warp & the default Asus against "Hardware Acceleration", please?

Is it likely I will forfeit "Hardware Acceleration" when 1.9 becomes a customer release?

 

 

012_Unfinished_Render.afphoto

[Chris B]

Can you attach the source files so I can try the render myself? I think we've only see the failed afphoto renders so far! 

[Woodkopf]

On 10/21/2020 at 4:23 PM, Chris B said:

Can you attach the source files so I can try the render myself? I think we've only see the failed afphoto renders so far! 

Yes, attached.  I have used these four files consistently for testing.  I have them in RAW as well, but only used the jpgs.

 

 

 

 

P1010075.zip

Edited October 22, 2020 by Woodkopf
Edited files uploaded, as requested by Chris B

[AlainP]

Made the panorama on Desktop and iPads without any problem. Acceleration is enabled on Desktop app.

[Chris B]

Same here, however inserting the images like this into the forum sometimes fudges them. Can you drop them in a folder and zip them up and attach that instead please?

[Chris B]

I hate to say this, but with the zipped images, I still cannot reproduce the half-rendered image 😬

[Woodkopf]

Thanks for your efforts Chris.

I was also afraid of that ☹️.  After sending those images yesterday, I decided to remove the AMD graphics drivers completely and reinstall the original 2015 drivers, still the same render problem.  Deleted again and let Windows Update pick a driver, (installed an AMD 2019 version), still same outcome.  Reinstalled latest versions 20.9.1 (WHQL); same result.

Tried the four images on my Surface Book laptop (Original Version), it worked fine!

Today I have updated the Beta version on the laptop to 1.9.0.815 and tried again.

• With OpenCL using the Nvidia GeForce GPU - Worked fine.
• With OpenCL using the Intel HD Graphics 520 - Also Worked OK.

So I have exhausted all the possibilities I can think of with the ASUS (AMD) R9280-DC2T-3GD5, but it obviously must be that.  But as it was not a cheap card I am loath to invest in another, so I am not sure where I go from here.  Obviously I can leave it without using the OpenCL, but it seems a shame not to be utilising the extra capabilities.

[Chris B]

If the card didn't support OpenCL, I'm pretty sure that it would be greyed out but what I'm not sure if the version of OpenCL.dll or the AMD_OpenCL.dll has any bearing. I'll need to escalate this to be honest.

[Woodkopf]

On 10/23/2020 at 2:32 PM, Chris B said:

If the card didn't support OpenCL, I'm pretty sure that it would be greyed out but what I'm not sure if the version of OpenCL.dll or the AMD_OpenCL.dll has any bearing. I'll need to escalate this to be honest.

Hi Chris,

Just a few comments, not sure if it helps:

I have benchmarked the system, averaged over 8 results :

Vector (Single CPU):	250
Vector (Mufti CPU):	982
Raster (Mufti CPU):	275
Raster (Single GPU):	2289
Raster (Mufti GPU):	N/A

You were going to query the support of OpenCL with respect to the ASUS Radeon R9 280 DirectCU II

I found a link to the Radeon R9 280 series, where it was benchmarked and a figure given for OpenCL:

https://www.techpowerup.com/gpu-specs/radeon-r9-280.c2405

 

[emmrecs01]

@Woodkopf @Chris B

Coming rather late to this thread, but I downloaded the zipped folder of the four images, used them to create a Panorama in beta 1.9.0.820.  No problems encountered.

My computer spec is below - I am using an AMD Radeon R7 360 GPU, with latest AMD drivers installed (just checked, Radeon Software v 20.10.1) along with Intel HD530 on my CPU.

HTH

Jeff

[Woodkopf]

20 minutes ago, emmrecs01 said:

@Woodkopf @Chris B

Coming rather late to this thread, but I downloaded the zipped folder of the four images, used them to create a Panorama in beta 1.9.0.820.  No problems encountered.

My computer spec is below - I am using an AMD Radeon R7 360 GPU, with latest AMD drivers installed (just checked, Radeon Software v 20.10.1) along with Intel HD530 on my CPU.

HTH

Jeff

Hi Jeff,  thanks for your input, it is appreciated.

Just checked the drivers to make sure they are up to date.  I really do not know what to do next.  As mentioned previously I have tried it successfully on my laptop with "Hardware Acceleration" enabled and it works fine with exactly the same four files.  Could try a rebuild, but its an awful lot of work and I have a lot of photos with mirrored disks and I really don't want to mess it up.

[Chris B]

1 hour ago, Woodkopf said:

Could try a rebuild, but its an awful lot of work and I have a lot of photos with mirrored disks and I really don't want to mess it up.

No don't do this. I don't think it will make a difference.

We are still working out which hardware should and will support OpenCL. I don't have any answers at the moment I'm afraid. This is still something we're working on in the beta.

[Woodkopf]

1 hour ago, Chris B said:

No don't do this. I don't think it will make a difference.

We are still working out which hardware should and will support OpenCL. I don't have any answers at the moment I'm afraid. This is still something we're working on in the beta.

Thanks Chris,

As stated it would be a last ditch move, so thanks for the comment.