seabirdr

Since 2016, I've been working with Affinity Designer, and it's been a constant in my professional toolkit for almost 8 years now. While Affinity Designer isn't without its flaws, it has significantly liberated me from the cumbersome Adobe suite. There's no question that it has made me more efficient in my work. I was taken aback by the unexpected announcement of Serif's acquisition by Canvas. It was quite a shock. Nevertheless, I want to offer my heartfelt best wishes to the Serif team and thank them for the substantial support that Affinity has provided me over the years.

Honestly, to get that "extrude" effect right now, we've got to manually apply a bunch of techniques to draw it out. I really believe having a built-in extrude function would be a game-changer in terms of cranking up the efficiency for crafting these kinds of graphics. So yeah, I'm all for adding this feature to the toolset.

@Alfred I appreciate you sharing that link. It appears I'm not alone in considering the batch renaming feature. However, just to set things straight, the demand for batch renaming was already there. Truth be told, renaming layers in Affinity Designer has always been a bit on the slow side. It's just that the introduction of the layer states feature recently brought my need for batch renaming to the forefront.

Layer states have been incredibly helpful. Seriously, with solid naming conventions, I feel like Superman. But here's the thing, we still can't batch edit layer names in Affinity. And since the 2.4 update has beefed up what we can do with layer names, being able to batch name or modify them has become crucial. It's all about streamlining our workflow, right? Efficiently renaming layers is key to really making the most out of layer states. Can't wait to see this implemented!

I've noticed that the CPU usage doesn't decrease, even if I wait for three to five minutes or longer. That's why I'm reporting this issue.

thank you, walt.farrell. I have recorded the screen and uploaded it here. https://we.tl/t-wiwXQv6Ta2 In the screen recording, I opened Affinity Designer three times. The first time I opened it, the panel were not enabled and the CPU usage was normal. The second time Affinity Designer crashed abnormally. The third time I opened it with the panel enabled, and the CPU usage was high. I noticed that there must be some historical files to reproduce this problem. The panel cannot be empty.

How do I reopen this panel?

The problem appeared in the official version 2.0. Now it reappeared in the 2.1 beta. Here's how it works: I close all the files, do nothing, and Affinity Designer's CPU usage stays around 10% . If I turn this off, the problem goes away, which is weird, I don't know what the connection is, but it works. Maybe it's a common problem, maybe it's only on my computer. But this is exactly what I came across, so I thought I would post it, hoping to help with the optimization of Affinity Designer.

hi @stokerg, I'm glad you care about the problem we face. As chessboard said, the stuttering does not happen with specific files. In fact, no matter what file I open, if the windows version of Affinity Designer 2.0 runs long enough (For me it is 30min~60min), I will definitely encounter the lag. If you can ask your team's designer to work with windows Affinity Designer v2 for a few days, he must be able to experience the problem we encountered.

I have upgraded to 2.0.3, but the same problem still exists. Every time I use Affinity Designer for a period of time (30min~60min), it becomes abnormally stuck. The only effective solution is to close it and then open it again. Hardware i5-12600KF 32 GB ram Nvidia GeForce GTX 1060 3GB

Thank you for your concern about this issue, but I don't agree with your point of view. The location and scope of artboard should not be expressed by the outlines. Because for designers, it interferes our judgment on the design content. Besides, there is almost no other design tools such as AI, PS, Figma work like this. Their “artboards” have no such oulines. This is definitely a bug.

Thank you for your suggestion, but your method doesn't work at all. If it works on your computer, could you show us some screenshots or videos. Thanks.

I can see the gray lines in different zoom scales. Affinity Designer 2.0.3

+1 Every time I use Affinity Designer for a period of time (30min~60min), it becomes abnormally stuck. The only effective solution is to close it and then open it again. Hardware i5-12600KF 32 GB ram Nvidia GeForce GTX 1060 3GB

+1

I encountered the same problem. I found that disabling this option can solve the problem.

I'm sure that Designer V2 can't gain focus on my computer. But yesterday I have a new discovery that if I hold down the shift key and drag a file to V2, V2 can gain focus. Here are the details of the OS:

I encountered the same performance problem. It is very easy to happen. But I have not found the cause of the bug. When running slowly, switching between Move Tool, Node Tool and Pen Tool will stuck for one or two seconds

Thank you for your concern. I recorded a screen video. It can be seen that I dragged a file to the Affinity Designer V1 to activate it, and the Affinity Designer V2 couldn't be activated. 20221113 122553106 cant drag to activate.mp4

I drag a file to the Affinity Designer icon on the taskbar, and the window cannot be activated. Windows 10 Affinity Designer 2.0.0

@randomjames I was explaining the reason why the svg to Figma will become 1px from Affinity Designer. The reason is that the Affinity Designer did not give SVG Width and Height in px. I also hope that serif can solve this problem.

After copy the graph from the Affinity Designer, you can see it in the clipboard <svg width="100%" height="100%" If Width and Height can be set to a certain value, it will not become 1px size in figma.

AffInity Designer hasn't improved for Moho Pro. Have you found a workaround?

If the development team refuses to develop this feature, please send a clear notice. Because the request keeps coming up. In order to avoid wasting forum resources and users' expectations, please give a clear answer.

This was a feature request that was repeated over and over again, with no response from the development team. I don't think it's a waste of resources to post more.