R34V3r

I get that, but there are more forum posts that reported these issues, and eventhough I understand that ironing bugs and platform optimalisations take time, we didn't get a solid response that this serious issue is present and being investigated. Instead, they seem to work on new features and other mac optimalisations like the touchbar. To the Windows user community, this does not give the feeling that they take their multiplatform strategy very serious, but is more like a slap in the face. The least you can expect is a "we know the issue exists and are working on it" message.

so the issue is also present on OSX? what hardware are you running it on at the moment

what Nvidia GPU are you running at the moment? I tested photo on my friends pc (on a GTX 670 2GB I7 920 setup) and performance isn't an issue at all, while my much faster R9 390X 8GB I7 3770K setup is performing much worse.

Never thought about this but you may be right. My R9 390X 8GB I7 3770K setup is lagging and stuttering a lot on simple examples. I installed photo on a friends pc (who has a gtx 670 2GB and a i7 920 setup, so much slower) and he doesn't seem to have any performance issues at all. It might be Affinity is relying on CUDA acceleration at the moment (as most macs are on NVidia) for hardware acceleration.

There was someone in this thread https://forum.affinity.serif.com/index.php?/topic/33002-affinity-photo-15045-slow-and-crashes-often-on-windows-81/&page=2 Maybe Affinity is relying a lot on CUDA for hardware acceleration? As I have AMD systems only I cannot test this myself. It might be possible they are still porting to dx11 from metal or openGL (which takes time). The problem is, at least for me, as the developers haven't commented on this in their roadmap, beta forums,... (at least not in my knowledge, please correct me if I'm wrong), we don't know if this issue will be persistent (should we change our hardware setup or wait for an update, or is this an issue that isn't under investigation atm).

thanks for the response, I tried clean boot, reïnstalling the application, changed the renderer​ from my R9 390X to WARP but that didn't do much. I noticed the performance on the beta (1.5.2.56) is a bit better than the latest official release (1.5.1.43), so I hope performance will be increase further until the next official release. Porting software from one OS to another is never easy (especially when GPU acceleration is needed), so it's normal that an advanced application such as Affinity Designer and Photo have some issues regarding performance right now. I find it weird however that developers haven't acknowledged this issue yet, especially when there are other threads that are reporting unacceptable slowdowns for simple operations as well.

thanks for the reply. I just tested this without any luck, CPU usage is still high and fragments are still a thing. Can I assume Mac users are not having these issues?

so if you load in the mermaid example: and you try to move this group: you don't experience a lot of stutter and 100% CPU load? also with simple rotation and scaling of objects like a 512 X 512 png your CPU stays at a normal level?

I wanted to illustrate the severity of the performance issue with a very simple situation. I want to know if this is happening to just me or others as well. I am having performance issue with both Designer and Photo on all 3 machines I have tested it on (Desktop, Laptop, Surface). To illustrate the severity of the problem I tested the following situation on Affinity Designer on my desktop with the following specs: - i7 3770K 3.4Ghz CPU - 16 GB RAM - AMD R9 390X 8GB OC GPU note that the issue is just as bad in Affinity Photo. As you can see, Affinity is recognizing my GPU as the renderer and has permission to use all of my 16 GB RAM. I started by creating a simple 512 X 512 document and loading a 512 X 512 PNG of a box in it. 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 continued by scaling the image with shift-down (so no ratio lock). 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. Photoshop has no issue with scaling the same box whatsoever. 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). When scaling the image now my CPU level is ... you guessed it: 100%. Fragments are now really annoying at this point and happen a lot more often: I continued by changing the donut a bit by making it a Half donut, Fragments are now a real problem: Lastly, I converted the donut to curves, selected all corners with the corner tool, and rounded them all at once, In this operation there is a lot of lag present and if you wanted to reach an exact corner radius on sight, you wouldn't be able to do that: when scaling the image now, fragments are still an issue but a lot of stutter occurs now as well, this lag is on a level that isn't workable anymore. I feel like my 2816 core counting gaming GPU isn't used at all here and every pixel is calculated by my 8 threaded CPU. I feel like the only way I can have good performance would be to buy a Intel Xeon CPU with a lot of cores that costs 2K+. Note that in real life, 512 X 512 is a small size for content so the fact it has performance issues with this on a machine like this is unacceptable to say the least. I don't want to bash Affinity here to be a bad application, because it isn't. It's feature packed and in some ways it does more than Photoshop. I really want to make this my Photoshop/Illustrator replacement because the workflow is much more streamlined and more fun. But as a Windows only guy, I feel like this is a bad port of a mac application and the weak performance is really a dealbreaker for me. I don't know if mac has the same issues but if so, they can't call this the smoothest image editor on the market, not by a long shot. I really want this issue to reach the developers and judging by the response on this forum, this might not be the most efficient way to reach them.

What CPU and GPU are your running on? I find that a lot of workloads in affinity (from rotating and scaling to applying filters and curve adjustments etc.) aren't offloaded to the GPU but are instead CPU intensive (Photoshop doesn't have any extensive CPU load issues like that). My specs: i7 3770K 16GB DDR3 390X 8GB GPU When I load in the mermaid example from the welcome screen templates and move the background layer or background group for example, this is so laggy you can't even work precise anymore. Is this me pushing the system too hard? because when rotating a 2000/1000 with a Gaussian blur and perspective layer, the lag is unbearable and the program crashes afterwards.

I would also like the option to snap cropping to image boundaries. This seems like a very small detail but it is a workaround to create a new document from clipboard if you have a file with some contents in which you want to crop it to the "background image" size. With all snapping options enabled it will not snap. Is this an error from my part or is this feature just not present yet?

I am experiencing a lot of lag in both Designer and Photo. My main machine is running Windows 10 on an i7 3770K, 16GB of RAM and an AMD 390X OC with 8GB VRAM. When comparing things like rotate, curve adjustment, scaling, perspective filter, etc. with Photoshop or Illustrator, I noticed a huge CPU spike on affinity to 100% together with some lagging fragments (squares in the selection that arent updated yet to the new configuration) while photoshop and illustrator could pull it off with smoother framerates as well as less CPU usage. It's like my 390X isn't used a lot in Affinity. This is really breaks my workflow when I am working with multiple layers or bigger documents and I can't work precise anymore. I wonder if I am the only one that notices this? Is there something wrong with my pc build or software configuration or is this just how Affinity is supposed to be working?

I am currently in the exploration phase of affinity designer for windows so sorry if this question is allready asked. I am using this on my surface 3 and pinch and zoom works great while painting, but when swiping around with one finger, the program is registering it as mouse input, is there a way to make panning the canvas with one finger possible, I checked the preferences menu and searched the forum but I haven't found a solution yet. I know it is possible with 2 fingers, but it is not always that accurate and sometimes, pinch and zoom registers a brush stroke (mouse input) as well, which is really anoying.