Jump to content

Search the Community

Showing results for tags 'performance'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests, Suggestions & Discussions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 100 results

  1. Hello The problem: I have have had Affinity Designer for 1 year now i think, but had not used it for a while. Came back to 1.7.1 version and the program felt a bit slow. I did update to 1.7.2 and still have this issue, With slow i mean, every time i used the view tool, the screen felt like, it was moving with a 0.1sec delay (huge smoothign effect) same goes for selection tool when selecting an area or simply moving objects, Bigger files around 50-60 MB are even worse sadly. What i tried: I tried looking into the performance settings and found the cause, which is the Nvidia GPU render option. I use laptop so i tried integrated card: Intel HD 630 and it started working pretty smooth, but has weird lag spikes from time to time. What may be the cause for the software to slower down on Nvidia GPU? First i thought i may have throttling issues, but i have undervolted my CPU and the laptop never reaches more than 42* temp. My laptop specs: Dell XPS 15 9570 CPU: Intel i7 - 7850h GPU: Nvidia GTX 1050 TI - Max Q edition Ram: 32Gb In short, the Intel Graphics work better which should not be like that and any help is appriciated
  2. Doing a series of technical drawings – not complicated. Copying a few lines with arrowheads (or even just 1) into a document created in a pre-arrowhead Designer version, results in the spinning beachball of death. Is there a workaround with older documents to avoid this issue? (I have tried some of the old favourites – like saving as without success). Cheers Friatec Tee T EF Blu-ill.afdesign
  3. Affinity Designer 1.7.2 (and 1.7.1) is lagging and/or crashing/not responding when I'm scaling/moving/rotating a complex vector image which is placed in a masked layer. If the object is placed as a normal layer I can scale/move/rotate it without a hitch. it can be reproduced (at least on my laptop). Tried the same thing with version 1.6.5 - had no problems. - Working with Version 1.7.2; - Windows 10; - 16 GB RAM; - Intel i7-6600U CPU @ 2.60GHz 2.81 GHz
  4. Dazmondo77

    Slow

    I'm the first to admit, I'm a total Affinity fanboy so this is a difficult one --- I've been sitting on this problem for a week or so as I know publisher is a massive deal and a major focus for the Affinity team - but I can't work normally on my children's book illustrations as there appears to be slowdowns, the most annoying being the time it takes to open the .afdesign file which has gone from around 4 minutes to open in 1.6 (which ran nice and quick and snappy) and roughly about the same time to open in betas 1.7.0 - 1.7.0.7 (still nice and quick performance) then with the move upto beta 1.7.0.8 performance had slowed to a crawl then 1.7.0.10 refused to open the file but appeared to be fixed in beta 1.7.0.11 although it was now taking around 10 minutes to open and still with the slow performance issues (originally reported on May 6th - see below) With the 1.7.0 Appstore release I was having slightly better performance and far less beach balling but I timed the document opening at 16 minutes (WHAT!) then came the 1.7.1 update (me hopeful I'd get some performance increase) but I was left watching "Loading 1 document" for ages way more than 16 minutes before force quitting and restarting my mac (wish there was a progress bar?) so thought I'd time it opening = 46 minutes (AAAGGGHHH!) well at least it opens! - I though before bothering the forum, I'd have a go at trying to improve things with a few tricks that helped me out years ago in Illustrator and also Quark - so I went back to the first 8 pages which I put together in 1.6 which opened up in around 30 seconds in 1.7.1 and was super quick and nippy to get around then I took pages from the 1.7.1 46 minute doc and copy pasted into fresh art boards in the 8 page doc - all went really well I I was getting nippy performance compared to the 46 minute version, which was slow and choppy to get around - re-saved as 'NITN proper.afdesign' I also went through all the pages and layers and trashed anything not in use, in order to streamline the file - saved, quit Designer and re-started and re-opened the new file, thinking I'd wait maybe 5 minutes or so so at most, thought I'd time it, just in case = 1 hour 50 minutes (WTF......AAAAAAAAAAGGGGVHHHHHHHH!) + lots of beach balling - although, no more jumpy, choppy performance when getting around and zooming (between beach balls that can lock up for around 5 minutes) The artwork for the first book in the series (which uses all the same characters, textures and all that and is the same 26 page format) was having similar performance and opening issues in the last beta but now takes less than a minute to open and is nice and fast and fluent in 1.7.1 and all my smaller documents run like a dream. I'm currently at the final 'last tweaks stage' before we get PDF and hard proof copies to send out to agents and publishers along with the first book (we are down to the last 30 hard proof copies) - all flawlessly put together in publisher using rasterised linked tiffs of the art boards from the problem file. Just wondered if someone can offer help or advice - and yes, after tuning into Affinity Live the other night, I wish I had Metal compute but I need to stick with El Capitan as it's the last Mac OS that runs 32bit apps (CS5) without major issue (I only very occasionally run Illustrator to plug the gaps til' designer has all the knobs and whistles) but the main one is Acrobat pro 9 which I need for checking pdfs as theres nothing else, apart from Callas PDFtoolbox (£500!) so NO METAL (for the foreseeable future) (original forum bug report:-)
  5. Overall performance is good for me, but there is a lag when trying to use the node and move tools with a pen. The node or object selected doesn't start moving until a *long* time after the drag starts, and in that time the pen is a long way from the original touch point. After the delay, the object or node snaps to the pen position. Things are smooth after the initial delay-snap. Other features are smooth as well. Drawing with the pen for example is perfectly smooth and lag free. I am using a Surface Book 2 with maxed out memory, and the latest version of Designer. Having the base attached or not makes no difference. I tried turning off the "tap and hold to right click" feature in Windows and various settings in the performance tab. Nothing I have tried so far makes a difference. Also note that the CPU is basically idle and I am just trying this with one object. This is super annoying, especially after using my iPad for editing, where the same features are buttery smooth. Even editing over a wifi connection on the Mac with AstroPad is a better experience. Any suggestions on how to fix this with a setting somewhere? If not, are you working to improve this feature? I would like to use my Surface Book more with Designer, but this is a total buzz kill for me. Thanks for an awesome Mac and iPad version. I am really looking forward to a better experience on Windows.
  6. It's what the topic title says, the further you zoom in, the slower the brushes becomes. If you're zoomed way out brushes perform between well to acceptable, depending on their complexity. As you keep zooming in, the performance drops further and further until they're unusable. This is true even for basic round brushes, but it's more noticeable in complex brushes, such as Frankentoon's. I've also noticed it's worse if you're drawing over vector shapes, which is the whole point of these brushes. See the video for a visual reference. iPad Pro 9.7" with latest version of iOS 12.4 and Affinity Designer 1.7.1. I've tested and this also happens on Windows, the more you zoom the worse the brushes perform. But on Windows, especially on a desktop machine, the sheer processor power masks the issue. Thanks! RPReplay_Final1565346075.mp4
  7. I'm running Affinity Designer 1.5.1.43 on Windows 10 and it is freezing up constantly. About once per minute it'll freeze for maybe 3-4 seconds and then everything goes back to normal. When it freezes Designer will use about 50% of the CPU capacity for the duration of the freeze. I would assume my computer's CPU simply isn't powerful enough, but Designer regularly uses up to 90% of the CPU capacity with no problems. Also this was never a problem before (same computer, same files). It's been about a month since I last used Designer. This problem started last week when I opened it up and updated to the latest version. System specs: Windows 10 64-bit Intel Pentium G4400 3.3GHz dual core 8GB RAM Nvidia GeForce GTX 1060 6GB 256GB SSD Any ideas what might be causing this? Thanks.
  8. I've created a DIN A4 booklet about 80 pages. Before the last two updates the app works good and fast. Now when I open my file, the memory and CPU explode and the app or the whole computer works really slow. After a few minutes the CPU works normaly but the Memory is still high used. Sometimes the tool crashes when loading the file. Is that a known problem? Any Tips for a short-term solution?
  9. Under Preferences -> Performance are the two checkboxes Dither gradients and Use precise clipping. Using the help section won't help me: Dither gradients speed up the performance? So why should I leave it unchecked? Choose a clipping option implies that there is more than just a checkbox. Checked or unchecked what is the difference?
  10. Hello! I have had a few issues recently that seems to be performance related (serious lag and erratic behaviour of node tool and move tool) I have attached a video of a work session (sorry if it's long and tedious, it's a realistic snippet of how I, and probably many others, have to work) I don't know how to put subtitles on a video so I will put a list below with the issues I found. Now, I must say, as it have been pointed out multiple times a smooth and/or simplify option on path and nodes would be greatly appreciated. I know that I will receive comments on the fact that I should learn to be proficient with a pen tool before trying to smooth paths, because that what I have been reading a lot on these forum. I get that most people who answer here are "creators", but I suspect a lot of us Designer users are what we call "artworkers". Meaning we have to work on files given to us by others (who don't care if their files make sense or not - they don't give a crap, they couldn't be bothered, don't even try to talk to them ) The case I am presenting here is a 146 kb .eps file provided by the studio in charge of digitizing the assets from Schultz estate. They provide those files (take it or leave it) to those who buy the licensing rights. My work here is to smooth out the jagged lines, because the scan was probably done, digitized via livetrace (and converted to .eps) from a small/damaged/blurry line drawing. So if you have the patience to go through the video, you'll see that the file has 81 layers (which I tried to organise a bit prior to recording the video). You'll see that I really lack the availability to use a smooth tool or a simplify option. I tried to use the "smooth" function in the contextual menu, but it makes little difference to the end result. so the list of issues with the timecode are below: 0.06: trying to use the space key to pan the canvas, it's either slow or simply not working (it sometimes does) have to use the navigator instead 0.14: Same with using the zoom (Space bar + CTRL) 0.38: Trying to select a shape with the node tool (it sometimes works) end up using the layer panel (wading through 81 layers) 1.24: The node tool now has a mind of its own. At the particular moment I am not even touching the tablet with the pen. I am just hovering over the drawing after clicking the node and the node tool has now picked up the node and travels with it. I get the same behaviour with a mouse. (but who would use a mouse?). Again, I am not clicking, nor click/draging the node. I have to do a number of CTRL+Z to restore state. 3.10: Happens again. As I said, the original file is 810 KB. It's 146 kb when saved as an afdesigner file. Beyond the lag/performance issue, I would like to plea for artworkers workflow to be taken into account in the development of the software. When I do an inventory of all the features I'd like to add (select similar for example) I can see that these are features aimed at modifying shapes and paths as opposite as creating new ones. It seems to me that the project managers had "creators" in mind and not artworkers (simplifying here), meaning that if you are working on a generic .eps or .ai file created by someone else, it's infinitely easier do it in Adobe Illustrator (because those feautres exist in .ai), whereas I have no trouble using all the - very well - thought-out tools of Affinity designer if I want to create a design from scratch (I am someone who is naturally very neat with her layer stack, and I always name and group my layers, it's even a breeze if someone has to work on my files ). But if you decide that your software isn't aimed primarily at artworkers, then I think you're losing out (particularly given the price and licencing model, artworkers are AD natural customers. Apologies for the Sundays ramblings.... Hope everything makes sense... record_000001.avi
  11. First of all: Love the new features, especially the isometric grid, cant wait to use them seriously! Usually i work on my laptop and have an open browser to google stuff. I noticed that the panning/zooming drops in performance significantly when i switch back to my Affinity Designer Window (artboard). After restarting Designer it works ok for a while, but it always comes down to opening a browser window, switching back to Designer, zoom in/out - no animation or it does not zoom properly. If i want to pan - then i would need to use the navigation bar even though Space + drag is so convenient when using a tablet. In the past it was a non-issue, so i really don't know if it's my hardware. I used to do Vector/Pixel-based Artwork and Designer handled everything fluently. I panned and zoomed like crazy Now i struggle with simple Logo-Designs Could it be that Designer has become a bit resource-hungry since the update? Or is it me? Can i do something about it? My laptops' specs: i7-6700HQ 2.6GHz 16GB RAM Intel HD Graphics 530 NVIDIA GeForce GTX 960M (i switch them up sometimes) Wacom drivers are up to date (intuos pro)
  12. Input please: As a photographer I’ve been using Lightroom on my (now outdated) iPad for years, and used my wife’s Macbook Pro when I needed features, not available on my iPad (photoshop). I don’t really like Lightroom, I’m intrigued by Affinity Photo, and I need new hardware - so here’s my dilemma: Is there any difference in performance/possibilities/features/flexibility using Affinity Photo on an iPad Pro, or an iMac? Because that might decide my hardware choice (I really like my iPad cuz I travel a LOT, but the output and flexibility is far more important). I hope this makes sense! Thanks in advance for any help!
  13. Hi, I was working on someting simple when the updates came through today and after applying the update and opening the same files I was working on in AD again I noticed straight away a performance issue I had not seen before. The update felt a lot worse than my experience with AD since the start. I've attached a screen recording which show the difference clearly. I have two identical groups, the have a layer [same in each group] with fx applied to it. When the layer with the fx is turned off, the performance is fine, dragging the group around is smooth enough. When I do turn on the layer with the fx the performance is basically non-workable for me. You'll notice it in the video. The fx layer isn't antyhing heavy, just a bevel as a test, I've attached a screenshot of the fx. I've also attached the actual file if anyone would like to try. Also attached a screenshot of the peformance settings in the app preferences. System info: System Version: macOS 10.13.6 (17G5019) Model Name: MacBook Pro Model Identifier: MacBookPro13,3 Processor Name: Intel Core i7 Processor Speed: 2.7 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 8 MB Memory: 16 GB I have a Wacom Cintiq 21UX and an old 27" iMac attached as extra screens unplugging them doesn't make a difference. Bert Affinity_Designer_performance_with_layer_fx.mp4 Affinity_Designer_performance_with_layer_fx.afdesign
  14. Hello everyone, I'm having an issue where both Affinity Designer and Photo stay at "Not Responding" for about 3 minutes when starting up the program and THEN it opens fully. Basically it is super slow to open. This is a clean install as I just bought the software and there's nothing else running on the PC and the PC is still new and running well so it's clearly a problem with the software. I already tried changing the performance options (Renderer to the dedicated GPU instead of the iGPU which is the default for some reason. Also tried WARP). As for how well the program runs once it opens it's, meh, it runs jerky, zoom animations are slow and panning is super slow (This is NOT 60fps as advertised, more like 5fps) BUT if I use the touchscreen it works quite well, much better than the touchpad. I tried the software on a Mac and it was amazing but on Windows it kinda sucks so far. My Specs are: Windows 10 Home (1903 / 18362.145) Intel i7-8550U RAM 16GB iGPU: Intel UHD Graphics 620 dGPU: Nvidia MX150 EDIT: It appears that panning and zoom have improved somewhat! But sadly it still takes super long to start and still says "Not responding".
  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. With the new version 1.7.0.380 there are a some problems I did not have in any other version before. AP works slowlier. It crashes down every time I try to import or create a new category for brushes. It crashes down every time I try to import or create a new brush. It cursor freezes often when I want to change the settings of a brush. It often crashes down when I try to change the settings of a subbrush. I can't open Luminar Flex as a plugin. Colors sometimes change while exporting a JPG from a RAW. The exported JPG is more yellow and the contrast is to low.
  17. Let me first say that it was a real privilege to watch the Affinity Live presentation last night and to witness the obvious enthusiasm and vision of Serif in creating and marketing such a comprehensive suite of interactive products. I own all three and am delighted with them, though am far from being a power-user. However, one thing struck me quite forcibly last night: all the demonstrations in the presentation were running on either Mac or iPad. There was considerable time spent extolling the obvious benefits of e.g. using Metal to improve graphics speed and performance. I think I heard the word "Windows" once. It would have been very reassuring to be told that similar improvements in performance were also coming to Windows, or did I miss something??? I should add that I am also delighted that Affinity products are truly cross-platform, even though I don't own a Mac or an iPad, but it would be "helpful" to learn that we Windows users are not being forgotten in the striving to create a top-notch graphics/publishing/photo suite. Jeff
  18. Hello there, I am searching for a solution for the performance issue when I'm working with bigger vectorgraphics. My System is stable and doesn't provide any bottlenecks. CPU: AMD Ryzen 7 1700X Eight-Core Processor, 3394 MHz RAM: 16GB DDR4 GPU: AMD Radeon R9 200 Series (4095 MB) This is while working with really large vectorfiles: Affinity (big vector) just opened. ...while zooming in and out very fast. My Problem is now, that I don't know how to merge those files - they are so detailed like I never would need them. But I want them to stay vectorfiles to change their size afterwards like I need them. While working with such files, the performance is very bad, I can't copy and paste anything on realtime, or change anything without big lags (adding a new line of words - 15-30 sec). Does anybody know, how I can change those files, lower the details without changing vector to pixelgraphic? What I have tried: 1. Saving them to compressed .svg => not the best idea (poor details) 2. Merging them with boolean operators (this changes pixels to the same color) => useless Thanks mates. Have a great day! Best regards Chris
  19. Im working on a document in APub Beta 1.7.0.376 on macOS 10.12.6 (16G2016). If I use floating text over 40 pages with multiple text frames and insert some pictures and graphics with custom wrappings APub slows down extremely and the fan of my iMac27 (4 GHz Intel Core i7, 32 GB 1600 MHz DDR3, AMD Radeon R9 M295X 4096 MB) start to spin like crazy even if I only scroll. It seems to be caused by rendering the whole document on every event (scrolling, inserting text, etc.) I redesigned the document and use only text frames without floating from one page to the next. And behold... no time consuming rendering. Everything works fine. The slow document with floating text is appr. 2.2 MB the one that works fine is appr. 700 kB. All images/graphics are linked and not embedded. CPU in macs Activity Monitor App sometimes reaches over 500%. Another side effect is the slow rendering of the previews in the pages panels. Rendering-Problem.mp4 Any ideas how to use floating text without this side effect???
  20. Allright, the first thing I want to say is that I love Affinity photo. It’s range of functions is extraordinary, the interface is pleasing and the results I get are fantastic. The only complaint I had was that after a certain amount of use it began to become increasingly sluggish and performance fell off quite dramatically. I could see it was really struggling with frequent “not responding” messages , whiting out screens et cetera. Although I trawled the Internet to find a solution to this very irritating problem, nothing was convincing and the Affimity team did not seem to be taking it very seriously. I think I have finally found a solution. First of all, for all of you who are not technical geeks (like me), you should know that AP uses a lot of VRAM, the memory which is found on your graphics card. If this memory is insufficient, performance will inevitably become poor. My computer set up consists of an Intel i5 4 cores with an Nvidia GEFORCE with 3 GB of VRAM. I started to monitor what was using the VRAM. First of all, I was shocked to find that Firefox with 10 tabs open had increased VRAM usage to 70% with no other application open at all. On my computer, the base VRAM with no programs open is 19%. This means that Firefox was using something like half of all available VRAM all on its own! When I completely shut down Firefox, my VRAM use fell back to 19%. The first thing I did therefore was to jettison Firefox which is clearly a gluttonous monster when it comes to VRAM. Other browsers are much better. Edge is now my preferred choice, taking up VRAM usage by only 5% with numerous tabs open. But Chrome is also good. So, if you have Firefox installed and are having performance issues with AP you may have to look no further. My advice is to change your browser and preferably to shut your browser down completely when using AP. I also checked on how much VRAM AP uses. When I open AP, VRAM usage moves up to 23% from a base figure of 19%. If I open five photos this figure increases to 47% with no other programs operating. This is already quite a lot, and it is easy to imagine why problems arise if you have Firefox working in the background. What seems strange however is that when you shut down the photos, although VRAM use falls it does not go back to the original figure, seemingly holding on to memory it does not need. Why this occurs I have no idea. Perhaps AP engineers can offer an explanation. So the second thing I did was to experiment with using the WARP “preference” which can be found in the preferences tab within Edit. This is an alternative to relying on your own graphics card. Using WARP with no other programs open, AP with five photos open uses only 31% of VRAM, a much more reasonable number. I have found absolutely no difference in performance (speed etc.) when using WARP. AP behaves as it should. To summarise, if you are having performance issues, I recommend that imperatively you change your browser from Firefox if you use it and/or shut down your browser when using AP. Secondly, turn on the WARP preference. Also, limit the number of photos you have open at any one time to a maximum of around 5. Regularly save your photos and exit from them. I hope that the above is of some use to fellow sufferers.
  21. Hello, I’m looking to upgrade my iPad Pro 9.7 which I’ve been running Affinity on for the last couple of years. Does anyone have experiences of the performance of the iPad Air vs iPad Pro?
  22. Hello, my system: iMac, Intel Core i7, 3,1 GH, RAM: 16 GB camera: brand new Fuji X-T30 affinity photo 1.6.7 all assistant options inactive on start raw engine: serif labs It takes about 20 seconds to open a file. My Canon raw files are ready in 2 seconds... Any ideas or updates in the pipeline? Thx!
  23. Hi, after some inversigation I found out, that the new Noise Reduction algorithm increases the develoging time more than three times (on my machine): #135: 4 seconds (default setting) #243: 13.5 seconds (default setting) also the new Lens Correction and the Lens Remove Vignette increases a bit the developing time. Without any settings the developing time is nearly the same: #135: bit less than 4 seconds #243: bit more than 4 seconds Is there any chance to improve this in the future or enable to toggle between the new and old noise reduction algorithm?
  24. Hi Mark, regarding the developing performance with a 22.3 MP .CR2 of a Canon 5D M3 Load time: #135 --> 7.5 secs first time, later then 6.5 secs #240 --> 4.5 secs first time, later then 3 secs Developing time without adjustments (default settings): #135 --> 4 secs all the time #240 --> 13 sec all the time and I get a "washed" out image (btw. it's 1.5 seconds faster then the previous betas) If you need a sample file, please let me know... Thanks!
  25. It seems the performance in the newest beta is still messed up. See the movie I attached. All I did was create a new document, float the window, then drag t he window size handle around. This doesn't happen in the production version. My computer is a windows 10 machine running an i5 processor and 2 GB NVidia card. Nothing to brag about but totally sufficient for Affinity. Matt 0001-0213.mp4
×