![]() ![]() I continued by changing the donut a bit by making it a Half donut, Fragments are now a real problem: Fragments are now really annoying at this point and happen a lot more often: When scaling the image now my CPU level is. So let's stress it a little more shall we? Masking is something I do every time I fire up Photoshop and Affinity, so I created a donut shape and but it as a mask on the box image, I also put an inner shadow effect on the image (something I use a lot as well). Photoshop has no issue with scaling the same box whatsoever. As before the CPU usage jumps to 100%, but you can also see fragments in the image from areas that still need to be computed. I continued by scaling the image with shift-down (so no ratio lock). As I rotated the image you can see CPU usage jumped to 100% with a whopping 80% going to Affinity, If I do this on the same machine in Photoshop, CPU usage only jumps to 12% max. I started by creating a simple 512 X 512 document and loading a 512 X 512 PNG of a box in it. Note that the issue is just as bad in Affinity Photo.Īs you can see, Affinity is recognizing my GPU as the renderer and has permission to use all of my 16 GB RAM. To illustrate the severity of the problem I tested the following situation on Affinity Designer on my desktop with the following specs: I am having performance issue with both Designer and Photo on all 3 machines I have tested it on (Desktop, Laptop, Surface). I want to know if this is happening to just me or others as well. I wanted to illustrate the severity of the performance issue with a very simple situation. ![]()
0 Comments
Leave a Reply. |