Performance issues, slowing down entire PC.

[danielzu]

After several months they have not released updates. I still have the problems mentioned above.
I am currently using a Ryzen 5 3600 with a GTX 980 and windows 11.

[Chris B]

On 5/13/2023 at 6:12 PM, danielzu said:

After several months they have not released updates. I still have the problems mentioned above.
I am currently using a Ryzen 5 3600 with a GTX 980 and windows 11.

We have been running a beta which has had a bunch of fixes and improvements that we have found to address many of these issues you're experiencing. 

[danielzu]

Hello, the problems that I mentioned with the vectors were solved with the last update!
Thank you

[Bango]

Although the topic is quiet old the issues mentioned still seem to exist!

After doing a fresh installation of Windows 11, I also had do reinstall the Affinity V2 apps (using the MS Store versions). Since then not only Photo, Designer and Publisher start getting slow as soon as I want to create a project or if I want to open/import an image file in one of the applications, but also my entire PC and I have to force close the application to get everything running normal again.

Unfortunately, unchecking OpenCL Compute Acceleration under Preferences > Performance didn't fix the issue.

I vaguely remember having this problem once before when I first installed the V2 suite and back then I was able to solve it somehow, but unfortunately I can't remember how anymore.
Anyway, this shouldn't happen!

 

Windows 11 24H2
AMD Ryzen 5800x
32GB Ram
RTX 3090

[KillerAJD]

On 5/29/2025 at 1:45 AM, Bango said:

Although the topic is quiet old the issues mentioned still seem to exist!

After doing a fresh installation of Windows 11, I also had do reinstall the Affinity V2 apps (using the MS Store versions). Since then not only Photo, Designer and Publisher start getting slow as soon as I want to create a project or if I want to open/import an image file in one of the applications, but also my entire PC and I have to force close the application to get everything running normal again.

Unfortunately, unchecking OpenCL Compute Acceleration under Preferences > Performance didn't fix the issue.

I vaguely remember having this problem once before when I first installed the V2 suite and back then I was able to solve it somehow, but unfortunately I can't remember how anymore.
Anyway, this shouldn't happen!

 

Windows 11 24H2
AMD Ryzen 5800x
32GB Ram
RTX 3090

I've been running into an issue that sounds EXTREMELY similar to yours, although I think, in my case, I've found out what seems to be causing it. 

First, my specs:

CPU: AMD Ryzen 5 5800X OC'd to 4.8GHz
GPU: EVGA RTX 3080 10GB, slightly undervolted for cooling boosts
Windows 11 24H2
32GB Ram @3600MHz
3x Monitors connected via Displayport (2x 1440p @144Hz, 1x UW 1440p @144Hz, both with Gsync), plus a 4K LG OLED via HDMI @120Hz with VRR, although the TV is usually disabled, and only turned on occasionally.
Affinity versions tested: 2.6.3, 2.5.3, 2.5.0, 2.2.0, 2.0.0, 1.10.6

The issue I've been having is that all of the Affinity Apps (Photo, Designer, Publisher) will open just fine, but as soon as I create a file, or open a file, the program seems to hang, and this also causes my entire system to slow to a crawl. It doesn't seem to be spiking my GPU, CPU, or storage drive usage, but just seems to cause the entire computer to run at single digit framerates. The only way to fix this is to kill the Affinity Photo/Designer/Publisher process in Task Manager. I had this issue intermittently previously, although it seemed to go away at some point. I recall it popping up when I updated to 24H2, and lots of folks were having problems with that update, so I figured something on MS's or Serif's end got updated. 

Note that a week ago I wasn't having any issues, and was able to use Affinity Photo and Designer without problems. Since then, I haven't installed any Windows, GPU driver, or Affinity updates. 

However, this time, nothing worked as far as the fixes people had posted. I tried all of this: opening in safe mode and resetting defaults, turning off OpenCL, turning on/off Windows' Hardware Accelerated GPU Scheduling, double checking and installing the newest Nvidia drivers, installing the latest Windows 11 updates, removing the .affinity folder in %UserProfiles% so it was recreated from scratch, got rid of my undervolt/OC on my GPU/CPU, set my monitors to 60Hz and turned off Gsync, uninstalled the latest version of the programs and went back multiple versions, hell, I even uninstalled all of the non-default fonts because I saw somebody report they had an issue with a funky font, and NONE of that fixed it. 

However, as a last resort, I figured I'd just use the V1 apps just to at least have SOMETHING I could use on my projects, however, when that exhibited the same exact problem, I knew there had to be some real issues elsewhere, and that while it may have something to do with the software, it's probably more likely to do with my hardware. 

One issue I occasionally have (especially with recent Nvidia drivers) is I'll get random problems with my monitors sometimes not turning on, or if they turn off, when one of them re-connects (Windows will make a little connection noise like the cable was unplugged then plugged back in), it'd cause my system to hang, requiring a reboot. No blue screens or anything like that, just a weird driver crash. Due to that, for whatever reason, my first instinct at this point was to just disconnect my 4k TV/unplug the HDMI cable at my GPU.

Did that, and the Affinity programs open up with ZERO issues. I've even had the HDMI cable plugged in, created a new file, the program slows down again, and then I unplug the HDMI cable and the program immediately recovers. Dunno if it's still some weird issue with Nvidia drivers, Windows 11 24H2, or still something funky going on with the program, but I can finally use the programs I paid for again, which is a relief. I know this post is a bit old, but after searching for near days for a fix, I wanted to share it in case somebody else ran into a similar problem. 

Edited June 25 by KillerAJD