Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'Slow'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.3 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

  1. I found some settings that have improved performance on my MacBook Pro, so I thought I'd share them in case it may be of help to someone else. I know computer configurations vary a lot, but it may be worth a try. This is with Affinity Photo v2.2.1. I have a 15 inch, 2017 MacBookPro, 16GB RAM, an Intel HD Graphics 630 with 1536 MB Metal 3, and an AMD Radeon Pro 560 with 4GB Metal 3, running Ventura 13.6.1. It is not a particularly fast or powerful machine, but it worked fine for quite a while. I'm not sure when I started having problems (sorry), but I think it may have started with v2.2. Performance has gradually gotten slower as the day progresses. Memory Pressure started out very low when the program first opened (single digits), but as I edited and closed more files during the day, Memory Pressure crept higher and performance began to suffer badly. Memory Pressure gradually climbed higher than 100% at times, and Memory Efficiency plummeted at the same time. Performance got so bad, I was forced to close the program and restart it multiple times per day if I wanted reasonable performance. At least on my computer, I found the setting that "seemed" to be causing much or all of the slowdown. The key on my system is to "Use Only Integrated GPU" for Display", as highlighted in Red in the attached screenshot. I'm still Enabling Metal Compute Acceleration, which uses both GPUs for computation. My RAM Usage Limit is set to 9500 MB, which is more than half of installed RAM of 16 GB, and higher than I've seen recommended in a few posts, but it seems to be working fine and performance is good now. As the day progresses, I no longer see slowdowns which cause me to restart Affinity Photo, and Memory Pressure stays well below 100%. Hope it helps somebody out there who has similar performance issues.
  2. Designer was open for hours yesterday, it just got slow, slower and then time to close and open. This has persisted since v2 was released. Please FIX! was taken 3 secs to select new object. Close and reopen software and problem is gone for a short while. Gary
  3. Just installed V2.1. The speed is very laggy when zoomed in still . This has persisted since v2 has been released. Its a vector file and no effects on this object. 1 object and it lags. Not happy. PLEASE FIX THIS. If you being in a more complex file , its almost grinds to a halt. Gary Designer_2023-05-18_09-50-25.mp4
  4. Photo and Designer still slow switching between brush groups. Video added. Get worse the longer you use it . Video show it just opened and no doc yet. The more you add the slower it gets. This is a V2 issue since release. V1 is fine. Gary Photo_2023-05-18_09-55-36.mp4
  5. Hello, While in Designer, switching from one brush category to another is painfully slow. Gary
  6. Hi Everybody, I've imported my custom brushes from Photoshop, but they lag a lot when using them in Affinity Photo. It takes a good 5-7 seconds before my mark appears, even just a single click. I'm not using a tablet, just a mouse. My brushes tend to be large (2000px), but nothing that PS couldn't handle. Any ideas? I thought about turning off the brush preview, but I need it to see where I'm laying down my marks. Thanks!
  7. Heya, Have anyone else noticed that Affinity Designer and Photo gets slow and laggy after couple of hours of working with the programs? I first thought that there must be something with my MacBook Pro and after some hours the RAM is somehow blocked or full and every operation, mouse click, drag, pull etc is starting to lag more and more. But now that I'm using AD with a completely different Mac I notice the same behaviour. What can cause this? Is anyone else suffering from this habit that the programs have?
  8. I put out a scream thread about Affinity Photo blushing lacking behind the pen 🤬 After some very helpful comments, and experiments I have isolated the lacking to the Wacom Intuos But it doesn't happen when working with the Older Lightroom 5 (EDIT: I have notices the pen doesn't fully work after a file has be saved from Affinity . WIN10 Pc -- plenty of power/dics sizes/ram and all that stuff I use the pen only and none of the buttons -- eye/brain/fingers too old for all the fancy stuff . But I use the pen in the right hand and mouse in left hand -- as someone said "you have got to be sick!!" 😀 My main pen use is for Dodge/burn and similar I use only a small part of the tablet --- no idea how/why some use the bigger ones (??) I find most online stuff to detailed -- for artists mostly so far more complicated than I need --- do you have any links to share ? I generally use a basic round brush very similar to the Lightroom 5 adjustment brush So the questions about setting up the Pen/Table to work with Affinity Photo How have you set up your Wacon to work with Affinity ? Is running the mouse and pen together likely to cause problems? I will do some testing myself in the meantime. How do I know if the nib needs replacing ? Have replaced it a couple of times only because I thought I should . Your open thoughts, ideas, and questions about your mouse and pen (problems) welcome
  9. I have a Macbook Pro 16 with lots of Ram. I updated to Big Sur and then latest Affinity for Big Sur. Now I sometimes have trouble selecting layers. I have to tap them several times. Also Affinity photo is much slower. Help!
  10. Best regard. 1) I have tried Affinity Designer and I liked it a lot to illustrate, but unfortunately it has a performance problem in windows 10 and 11. When I make illustrations with many objects, the program becomes very slow, when moving objects, when moving the stroke modifier bar (it is so slow that you have to enter the number otherwise it is impossible), when applying effects, when modifying figures , when moving a point. I have tested the program on two PCs: In both runs the same, slow. 2) And another problem is that it pixelates a linked element as I show it in the attached image. I have to get very close to be able to see it well. Now the problem is also that when I export it, it does it wrong, it exports it with the pixelated image and it shouldn't be like that. Thank you for your attention.
  11. When you use the brush tool and press the alt/option to switch to the Color Picker, it slows down very much. Pls fix it. It is very critical for work speed
  12. To Serif team. May we please know, in the end of 2021, why canvas rendering algorithms are still so terrible in all Affinity apps? 
It's just not pleasant to see at all. Lots of glitches, fps drops, screen tearing, jumping objects and visible tiling/blocky artefacts during any changes being made. While searching here on forums, I found lots of topics covering all these issues.
 Some of them are five or six years old. But some of these topics are much more recent. Various configurations, pretty good CPUs and GPUs of all sorts.
 But same screen tearing, artefacts and visible tiles. For a such long period of time. And there are still no fixes for that. In some of those topics I've found official responses, that "this is done by design", "it's the way our apps render the canvas".
 Well, it's not a good design then. And certainly not a good way to render the canvas. How you, at Serif, find it acceptable? Are you ok with seeing canvas rendering like that in your apps? How it passes QA and being shipped to your customers? Why there are headlines on Affinity website: "fast and glorious", "pan and zoom at 60fps", "handle 1000s of objects with no lag", "optimized for documents of any complexity"? When it is simply not true, but rather false statements. At least it is not true as long, as such core performance problems still persist for so many people, including myself. Why not consider implementing something like v-sync in your canvas rendering pipeline? Or something else that will prevent visible artefacts appearing during canvas updates. So it will wait for all the tiles to finish calculating their image data and then the whole visible part of the canvas will be composited and painted in a single (at least on the visible to user level) draw event. It will significantly reduce overall performance? Well, maybe, but then you'll need to find a solution for this as well.
 Now it looks like the best idea for you was to throw all these tiles at your customer's screen as fast as possible. Because who notice that mess? They'll be fine with that. But I do notice that. And I want to avoid any screen tearing and tile artefacts in my experience with apps even on the most basic and simple tasks.
So, where is mine "smooth and glorious 60fps experience"? I'm not even starting doing any serious graphic design work because I don't like your canvas in its current state. Sorry. Second, why mouse polling rate plays such significant role in your apps canvas performance? Recently I discovered this myself, and it was confirmed with your team members, that reducing mouse polling rate to default 125Hz significantly improves screen canvas performance. Significantly, but still not perfect yet. So why not restrict any user input events and sync them with dispay refresh rate / gpu redraw cycle? Just an example. The latest Safari has new option in their Debug menu: "Prefer Page Rendering Updates near 60fps". It ignores the display's refresh rate and throttle all in-window paint events down to commonly safe and achievable 60fps. So why not consider something like this and limit overall fps and user input event processing for the sake of overall performance improvement? Maybe then we'll get a better canvas? My main question is: is it an absolutely impossible to seamlessly refresh the canvas without all these tiles flickering around constantly once anything is changed in the viewport? I'm just wondering why it is still being considered as normal in Affinity apps to have a canvas behaving this way? Sorry if my post seems to be a rant or offended you in some way. I had no intent of doing that. 
I'm really wondering if Affinity suite can be made better for all of us. Or we shouldn't expect anything better being done in this direction. Maybe it's really a one big "pain in the a.s" problem for any software developers to make CPU and GPU properly talk to each other? 
Maybe there are lots of problems with major OS developers ditching OpenGL and moving towards Metal/DirectX? Also, we've seen this recent Apple's movement from separate CPU and GPU with dedicated memory to SoC solutions with unified, shared memory.
 Yes, I can understand that your apps should greatly benefit from that. Obviously, lower latencies, less memory copy operations, overall faster access to data.
 All things being done in one place. But... But at the same time I feel that it's just wrong to keep telling anyone on Twitter how good and fast your apps perform on those recent Apple SoCs, while its canvas (which is the main working and the most important area) lags and glitches in general for anyone with more traditional system configuration, even on the most simple scenarios like moving an artboard or a single layer around. I couldn't be the one who notices that. And my system is pretty powerful and it's clear that it deserves better performance and smoother visual response. What I see now is simply unacceptable for me. To be completely honest, I must say that I love your apps. Overall, they are much, much better for me than anything I've seen in this field. There are so many great features and innovative decisions, little details, that make it truly great.
 Every time I discovered these in your apps I was so excited and happy, because I remembered how bad the same thing was in Adobe's products. I remember lots of annoying, terrible things that made me leave Adobe's universe once and forever.
 Vast majority of these things remain unchanged for many years. Because they don't care about their software and customers at all. I found your company and your products to be a complete opposite. Small and passionated company with people really interested in their products. 
I don't want to be disappointed with you guys. I believe in you. I believe in Serif. Just can't stand this canvas tiles flickering and tearing. Sorry.
  13. Hi, I'm halfway through making a graphic novel with Affinity Publisher (latest version). The images are all quite big (6000 by 6000 pixels typically - so maybe 590 mb each) and are all linked - not embedded. They are all much bigger than I need because I am only using part of each (I work in 3d and render out large images so I can choose to use them whole or just zoom in on a part - like a face or an eye). So far there is minimal text. The section I am working on at the moment is 25 spreads (each spread has around 8 images) and unfortunately Publisher is grinding to a halt and is basically unusable as a tool. I am not using any other applications simultaneously. Page sizes 9.64 by 12 inches. I've given Publisher Ram limit of from 30000mb to 59000 mb - doesn't seem to make much difference? I've tried with open Cl computer acceleration both on and off. Changed the view quality to nearest neighbour. My questions - anyway I can speed up the program? I don't want to go and drop the image sizes down as I'd still like to be able to fine tune the cropping at any time. I assumed that because the images were all linked I should be able to use large image sizes without a problem. I assume the image sizes are the problem? Am I asking too much? I've previously used Publisher for a 32 page kid's book with no problems (and not so many images}. I've noticed a few users on the forum also noting Publisher as slow. My only other experience is with indesign several years ago on a 250 page book featuring the work of 40 artists with lots of images and text. I had no problems at all but the image sizes weren't so huge. Thanks for any advice. Preferences attached in image. Processor AMD Ryzen 7 1700X Eight-Core Processor 3.69 GHz RAM 32.0 GB, Windows 10 Pro 64 bit, Nvidia GforceGtx 107 (drivers upto date) EDIT: I've dropped the Ram Usage down to 20000 mb after a kind gentleman had noted I was allocating more Ram than I had. Publisher runs faster now but still takes ages to render a spread of illustrations and when I go back to previously rendered spreads they are once again very pixelated.
  14. I have begin using Publisher to layout novels. However, speed issues are really slowing me down, especially on text that is flowing over hundreds of pages. Other aspects of the application are slow as well, not just text entry. Selecting fonts and sizes, applying styles, and changing visual options like showing/hiding baseline grid is so slow, a force quit is required. The below video shows a text entry example with a file that has virtually no graphics. It is mostly text, 503 pages long. To show the difference in performance, I first type into a single non-linked text frame. Everything works as expected. However, editing text in a linked text frame, the lag between characters appearing onscreen is almost ten seconds, per character. In fact, during that time Windows thinks the application has become unresponsive. It is really difficult to work like this. Any ideas? Is this a bug or just me? I hope it's a setting on my computer I can change. Demonstration of slow performance (Youtube Unlisted video) Affinity Publisher 1.7.2 Windows 10 Home Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz 16GB Memory 2TB HDD / 128GB SSD
  15. Hi, I have downloaded the new 1.7.0 version and followed by 1.7.1. The performance is a disaster and a real workstopper. Drawing something with any Brush tool is the worse I have encounter anytime (no matter if Healing, Brush or Clone....). I have a new top series NTB and Wacom Pro..... but I feel like working with old 486 PC :( I have been using AP for about the time of the first official release, but never saw anything like this :( This had not been a case of 1.6. version that one worked fine for me, but now I do draw something on Wacom and have to wait around 2 to 5 seconds till I see it on the screen, which makes any realtime drawing impossible I have tried restarting many times..... sometimes it works most time not...... It does not seem to be problem of Wacom as it looks the same working with touchpad or a mouse. Do not tell me I am the only one with this problem...... Please let me now ASAP as I am a professional and this makes my job unable...... Thanks Jindra
  16. Hey all, When I am using Affinity Designer and trying to draw there is a significant lag. Basically the tokes drag behind the cursor which makes it impossible to draw. My laptop: MacBook Pro 16, 2.3 8-Core Intel i9, 32GB DDR4, AMD Radeon Pro 5500M 8GB MacOS: 11.2.3 AD 1.9.3 Any ideas ? Cheers
  17. Hi, I have lots of fonts and it slows down the startup of Affinity Photo and designer, because every time it is loading all fonts. Is there anything I can do to speedup things besides deleting fonts? Regards & Thanks, David
  18. Hi there, I noticed an overall drop of performance with the newest version. Especially when liquify masks are involved (but not necessarily bound to the use of liquify masks). It will often react with huge lags even with only using the GUI (selecting tools, opening menus, switching personas etc but not doing anything to the file itself). Can someone else confirm? Update: Its not only sluggish but also a first grade battery consumer. 30% in half an hour. My device is an iPad Pro 2nd Gen 10.5" with the latest OS installed (14.4 as today).
  19. Was working fine in 1.9.0. Copy/pasting simple shapes/lines to create cut file templates. Granted they're rather large files but I had no issues in the previous version. Happens when alt-dragging to copy and paste, and also with regular copy and pasting. Tried starting a new file and bringing in a single object from the old file to create a new template from and getting the same result. Different file of similar templates of a different shape is acting fine, but it originated via save-as from the file that's having the issues. Also started a template from scratch and it is having no issues, to the problem seems to lie with how 1.9.1 is handling the curves in the file from the previous version. I'm not certain if this problematic file originated in 1.8.6 or 1.9.0. It was initially created from an opened pdf from a different software (non-Affinity) with the stickers that needed cut lines created and the sticker images/objects were deleted out after the cut lines were created. TL;DR - Program was being slow with a file from pre-1.9.1, problem revolves around the paths drawn in the file. Copy/pasting paths into new file didn't solve issue. Solution was to start new paths in new file from scratch. Willing to send along the problematic file to the Dropbox.
  20. I'm having really slow redraw on my library of my most often used assets, which I've used since the first version of Designer, and added to over the years, and it always been taken for granted that it just works, but now seems to be broken and is really slow to update when scrolling and has bombed Publisher around five times since testing 1.9.0 commercial release. I did report it below but had no response so thought the best option was to make a proper bug report detailing the assets problem alone In the above link there's a couple of crash reports I realise that some users are having slowdowns when the Paragraph panel is open so I closed all my text panels to make a screen vid grab (below) which shows how slow it is, although, the grab doesn't seem to capture the beachball - also Affinity managed to survive in the vid grab without bombing, I'm guessing if I do the same routine as in the vid another few times it will bomb. Is this common with the 1.9.0 release? as it's working great in both 1.8.6 and the last 1.9.0 beta Screen_Recording_2021-02-11_at_09_30_51.mov
  21. Hi, when using a RGB document and then a curves layer with LAB color space, affinity becomes totally slow. I added a DOF filter like James Ritson in his 1.9 Youtube today, when you mode the center it takes about 1 second to update. rainbow lab curves slow.afphoto
  22. Hello The most recent update from Microsoft, the so called fature update slows down Affinity Photo severely
  23. Hi, Try to work with Affinity Designer latest version on my iMac 2019 i5 6 core 40 gig mem Radion Pro 580 X 8 gig with Big Sur. Only a small logo but it is impossible to click the layers or do any work. Regards, David
  24. I have just bought a new iMac and have hardly any software on it. I have installed Affinity Designer, Photo and Publisher and opening files is very slow, maybe a minute! So I created a new web file, which opened very fast, but when trying to close the new empty file it look a long time to close, the wheel of death was spinning for a long time. One of the reasons I bought a new iMac was to speed up my applications but it has done nothing to speed up the Affinity software. iMac specs: iMac (Retina 4K, 21.5-inch, 2019) Processor 3 GHz 6-Core Intel Core i5 Memory 8 GB 2667 MHz DDR4 Graphics Radeon Pro 560X 4 GB
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.