A-Photo running Slow and Nor Responding,

[Dangerous]

I have an issue with A-Photo where it starts to run slow and at time will stop responding. I upgraded the memory from 16gig to 32gig and the graphics card from a 2 gig to a faster 4gig. It improved things but it is still happening. It is mainly happening with vectors layers or mixed vector/pixel. I have seen others reporting similar issues.

It seem that the longer I use AP the worse it gets and closing & reopening AP seems to speed it up again. Setting AP to use OpenCL makes it worse. Windows 10 i5 6th gen fully up to date and was no problems 6 months ago. It is as if the memory is 'clogging up' with temporary data that should be deleted when no longer needed but isn't filling up the memory cache. I does not appear to happen with other programs, just AP. A couple of people have said they have AD & APub as well and no problems with them just AP.

[Millhouse]

I have similar issue with the latest Windows version.

I run 50+ layers and even the UI becomes really unresponsive. Restarting the app makes everyting run smooth again - but only for a while.

Only solution I found was to revert back to an older version..

I'm running Ryzen 3950x with 64 gigs of memory with two Geforce 2070s cards. The openCL has always crashed on me, so I typically disable it. This bug happens both with and without OpenCL.

 

[DWright]

Hi @Dangerouscan you please let me know the model of GPU you are using and the driver version and can you please provide more information on your workflow when this occurs.

 

@MillhouseWhich Nvidia drivers are you using and which older version of Affinity Photo did you revert back too.

[Millhouse]

5 hours ago, DWright said:

@MillhouseWhich Nvidia drivers are you using and which older version of Affinity Photo did you revert back too.

Nvidia Studio Driver 512.59 I had the previous one installed when I started noticing the slowdowns so I updated the Nvidia driver to this latest one.

I reverted back to AP 1.10.3.1191 - Didn't try the 1.10.4.xxxx.

Atleast the UI lag seems to be gone now.

Edited May 2, 2022 by Millhouse

[Dangerous]

On 4/29/2022 at 7:03 PM, Dangerous said:

I have an issue with A-Photo where it starts to run slow and at time will stop responding. I upgraded the memory from 16gig to 32gig and the graphics card from a 2 gig to a faster 4gig. It improved things but it is still happening. It is mainly happening with vectors layers or mixed vector/pixel. I have seen others reporting similar issues.

It seem that the longer I use AP the worse it gets and closing & reopening AP seems to speed it up again. Setting AP to use OpenCL makes it worse. Windows 10 i5 6th gen fully up to date and was no problems 6 months ago. It is as if the memory is 'clogging up' with temporary data that should be deleted when no longer needed but isn't filling up the memory cache. I does not appear to happen with other programs, just AP. A couple of people have said they have AD & APub as well and no problems with them just AP.

I have speeded things up and it now work well. I went on to the Nvidia site to upload the latest driver (which I had previously installed with the card 3 weeks earlier) and found there was a Studio Driver designed for graphical programs (I had the Games Ready Driver). That has made a big difference to the speed and no issue with OpenCL so that is a plus.

 

3 hours ago, DWright said:

Hi @Dangerouscan you please let me know the model of GPU you are using and the driver version and can you please provide more information on your workflow when this occurs.

 

@MillhouseWhich Nvidia drivers are you using and which older version of Affinity Photo did you revert back too.

Nvidia GTX 1650 4 gig and as above now have the Studio Driver instead of the GRD. I had reverted back to the 1.9.??? but have seen a suggestion the I should have tried 1.8.5. Back using 1.10.5.1342

 

It seems to work fine now even with 50-70 25meg plus 320x RAW files so I'm happy.

[Dangerous]

On 5/2/2022 at 3:50 PM, DWright said:

Hi @Dangerouscan you please let me know the model of GPU you are using and the driver version and can you please provide more information on your workflow when this occurs.

 

@MillhouseWhich Nvidia drivers are you using and which older version of Affinity Photo did you revert back too.

Sorry for the late reply, I got no notification of you request for more info. I have the Nvidia GeForce GTX 1650 4 gig card, Intel i5 - 6400 cpu @ 2.7GHz, 32 gig ram, driver version is 30.0.15.1259 Studio Graphics. Loaded this driver because the games ready driver was worse.

. both Publisher & Designer work well without issue. It is only photo that goes Not Responding and normally only when drawing with vector graphics and seems worse if there are pixel layers as well as vector. Same files are ok in Designer. I can't remember the last time A-Photo stopped responding when only working with photos and then it would have been with a file (multiple photos) of around 200 meg or more (8 photos or more up to 30. raw files around 45megs each, 32mp).

Edited July 22, 2022 by Dangerous
include driver version

[Dangerous]

On 5/2/2022 at 3:50 PM, DWright said:

Hi @Dangerouscan you please let me know the model of GPU you are using and the driver version and can you please provide more information on your workflow when this occurs.

 

@MillhouseWhich Nvidia drivers are you using and which older version of Affinity Photo did you revert back too.

Further to my issue. I had lots of issues with one file I had lots of trouble with yesterday with it going not responding (something like 20 times in one hour) has worked perfectly today. It seems that after a shut down (windows 10) everything works fine and the problem only seem to occur after working on largeish vector file for quite a while. I did notice that yesterday A-Designer did the same with that file but I think it was because the issue was already present although I had no problems with other programs.

I still think the problem is the video memory 'clogging up' with data but don't know if this is a Windows 10 issue, Affinity Photo issue or both.