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
  • 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 105 results

  1. I am currently layouting a photo book (330x240mm) with 500-600 pages in Affinity Publisher on my Mac. Unfortunately, the memory consumption of Publisher is huge. I set the memory limit in Publisher to 28 GB (out of 32 GB I have in total) and disk warning to 64 GB. I have 500GB free space on my SSD and Publisher takes about 351GB while saving the document. Sometimes while moving pictures it crashes (but luckily keeps a backup file) and saving the file takes ages. The pictures are all linked and do have less than 10GB in total in full resolution. Is this a common behavior or is there anything I can do to fix this. Really looks like kind of a memory leak and is not fun working at all. Maybe you do also have some performance recommendations for my 15inch 2018 MacBook Pro with Radeon Pro 560X 4 GB, 2,9 GHz 6-core i9, 36 GB RAM and 1TB SSD? Thank you so much in advance! I really would love to do this project with Publisher and not go back to InDesign.
  2. Hi! Thanks to the developer for their contribution. Merry Christmas! In most cases, the performance of affinity photo is excellent. But I noticed that in some cases it is slow I used a 100 million pixels Lab/16 canvas to create twenty layers. The save of large-area modifications is extremely slow or even horrible. This is not a bug or a computer problem. Large-size (1000+) brushes are slow. Because of the lack of hardware acceleration At the same time I use the macos version, the speed after 1.7 is amazing, the filter responds in time without any lag, and everything is attributed to metal acceleration (in macos 1.7 metal) Please consider adding Lab/8 support to provide a faster preview than lab/16, especially in the current missing gpu acceleration. I will continue to use affinity photos in macos mojave (metal2 api)
  3. Hello team, is the ARM technology of the new macs an improvement in the Affinity suite? what are the advantages of this change?
  4. Hi, I do a lot of photo editing in Affinity Photo and Capture One. I also do a lot of vector editing in Affinity Designer. Last year, to speed up workflow, I bought a new Apple iMac Pro 3 GHz 10-Core Intel Xeon W, 64GB memory, Radeon Pro Vega 64X 16 GB graphics card and 2 TB SSD. This machine did cost me 8500€! This is very very expensive for me, but previously I had a MacBook Pro (2016) that was too slow for my graphics editing. So I thought to me let's spend a little more money to get a really powerful and fast machine, so my graphics editing will be in realtime without waiting time at all. At least that was what I wished and thought. But I have to say that neither Affinity Photo nor Affinity Designer have become much faster with the new computer. Both programs often have very long waiting times when working. I always watch the CPU usage and see that no core is ever used to its maximum. Let alone that all cores are used. It is absolutely incomprehensible to me that I have waiting times in the programs if there are enough performance resources available but they are not being used. For example, I like to work with the Inpainting Brush in Affinity Photo. Sometimes I really have to wait about a minute for it to finish calculating. It is very annoying. During this time, my computer has enough resources that Affinity does not use to calculate it faster. It may take advantage of 2-3 cores in half and the GPU by a quarter. But the rest of the cores do almost nothing. And we're not talking about huge photos here. I recently edited a 12MP iPhone photo. Or I work in Affinity Designer with graphics that consist of approx. 2000 elements. It is almost impossible to select all of these elements and move them around. It is so jerky that the graphics are rendered here and there and lag behind. It is impossible to work with. Here too it can be observed that perhaps two of the CPU cores do something, but are also underutilized. The rest does nothing. The GPU doesn't do anything either. Believe me, I've tried every combination of performance settings in Affinity Photo and Designer. Because it really annoys me that everything is so slow! But it only got slower than faster. I would understand that there is a waiting period if all resources are used to the maximum and there are no resources left. But because the CPU and GPU of my machine are mostly idle while I see slow process bars and long waiting and reaction times, I wonder if something is wrong? My question is, can I do something about it e.g. use certain special settings or is Affinity Photo and Designer not developed for using the performance of my machine? I've already spoken to Apple Support who checked my machine. But everything is normal and fine. I have reinstalled macOS and every app. But it hasn't changed. I mean a year ago this machine was advertised as "Power for Pros" or as "the fastest Mac every build". It would only have been faster with the 18 cores version with 256GB memory. So I ask myself, what machine do I need to buy from Apple to have a noticeable speed advantage? Best regards, Christoph
  5. When loading generative artwork - Affinity Designer slows down to unbearable levels even with relatively easy meshes This problem seems to exist on all platforms affinity runs on - which leads me to believe basic acceleration structures are not in place. Example file: https://tilings.math.uni-bielefeld.de/img/substitution/danzers-7-fold/patch.pdf Import this, try select all/ungroup/do anything to it -> framerate down to 1fps even on the beefiest of workstations Same issue can be recreated by creating any shape and copying it about 100 times.
  6. 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.
  7. Pretty much whenever I attempt to use Brushes in pixel mode, I get major major lag in performance, like 5 or more seconds sometimes, between when I draw and when the results appear on the screen. The problem seems to be more severe when using custom brushes, or the default included brushes when the width is increased to very large. I also get performance issues when I switch the blend mode from "Normal" to something like "Multiply". As far as I know, I have a pretty good computer - I've attached a few screenshots of the specs. I've also tried changing the "Performance" configurations but have yet to improve this lag. I've also tried closing running processes and applications. Am I missing something here. My computer is super fast with regards to software development but I'm new to doing graphics related things so I'm uncertain if there's hardware that I'm lacking. Thanks, Andrew
  8. Hi, I have a PC with these specs: Core i9 CPU + 32 GB RAM + RX580 8 GB GPU + Dell 4K Display. Latest version of Affinity Designer. Every driver is up to date. I'm getting huge performance issues whenever I enable isometric grid layout. Just dragging around a single rectangle is super lagging. It's a fresh install of Affinity and just a blank Desktop artboard. I tried to record my screen but couldn't find anything that can record properly 60 fps. (open for suggestions how to record my screen. tried build in game bar but it's terrible.) Any suggestions? Thanks.
  9. 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
  10. I work on a illustration with a huge number of small dot that i start on Illustrator and i work fine ; but when i change to Affinity, everytime i duplicate an element (and i do that a lot) my computer freeze for a few second. I loose a lot a time. Then i notice that the time my computer freeze was the same for one or multiple duplicate elements. And when i move a element, my PC doesn't freeze. So all i have to do was duplicate a lot of element and move them where i want.It's save me a lot of time. Hope that can help someone in the same situation (and sorry for my bad english).
  11. Hi, I have a iMac Pro 2017 with 3 GHz 10-Core Intel Xeon W, 64 GB 2666 MHz DDR4, 2 TB SSD and Radeon Pro Vega 64X 16 GB graphic card. I use Capture One to develop my 61MP Sony A7rIV photos. Some of the photos need to be edited in Affinity Photo and I use a TIFF 8bit uncompressed AdobeRGB as format. The image has 9504x6336px size. Saving the picture after edit in Affinity Photo takes a lot of time. It takes ~14 seconds for every photo!!! Is that normal for such a high performance machine? The Activity View does not show any heavy consumption of resources while saving in that 14 seconds. Greetings, Christoph
  12. 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)
  13. With more complex Publisher documents, I sometimes experience crashes just moving about in the document.. I have a feeling that the crashes are related to settings in the Performance section of the Preferences, but I can't find anywhere a FAQ or a comprehensive discussion on what the different choices really mean for the stability and performance of the app. A few questions: In the Display section, which is more stable: Metal, OpenGL, OpenGL (Basic) or Software rendering? I suppose Metal is fastest, or am I wrong? Does clicking "Use only integrated GPU" affect anything, especially as I only have an integrated GPU in my Mac Mini. What Does "integrated" refer to: Intel integrated graphics on the chip, or Integrated, as in "internal" as opposed to an eGPU? What effect has lowering or enlarging the RAM usage limit? Is 6 GB enough for more complex documents? Is it a good idea pushing the limit way over installed physical RAM size (I have 16 GB physical RAM installed)? Shouldn't apps allocate memory dynamically, anyway? Why am supposed to fiddle around with this? Does View quality affect the stablity of the app, since one would assume better quality would be more taxing on many resources? Does hardware acceleration/Metal compute really work in any meaningful way on Intel integrated graphics, with its paltry 1,5 GB RAM, which it allocates from main memory? So many questions, I know.
  14. As I've mentioned in this post, Affinity Designer's brush performance isn't all that great, but what's surprising me is that I've found out the issue is not present in Affinity Photo at all! I've recently purchased Affinity Photo while it was on sale, and immediately the brush performance seemed better, but I've tested it and it's a very significant difference! For this I've created an identical document on both Designer and Photo: 2800 x 2800 pixels @ 300DPI CMYK colour space using the same brush on both apps using the same colour, just in case same zoom level only one pixel layer same iPad Pro 9.7" (2016) obviously both apps running simultaneously If you look at the attached video then no further explanation is needed, the brush paints smoothly and fast on Photo, while on Designer it's rendered slower and in blocks of pixels, as if it's struggling to keep up. I think that covers it, but let me know if you need or want more information. Thanks! RPReplay_Final1573724065.mp4
  15. The attached Affinity Designer project illustrates how different drawing techniques can result in pdf export files that differ is size substantially. I discovered this while developing images that are to used in an iOS app. Of course, we can expect the size of the pdf file to impact the performance of the app. The attached AD project has three artboards. Each artboard has a separate drawing of a flower - all of which look much the same: Yellow-Flower: The pdf for web file size is 282 KB. Each of the twelve petals is a separate curve object with yellow fill and a black stroke. The inner pistils is comprised of 27 brown ellipses imbedded inside a single black eclipse. Red-Flower: The pdf for web file size is 31 KB. The twelve petals is comprised four curve objects (each represent three leaves) with red fill and black stroke . The inner pistils is comprised of 27 brown ellipses imbedded inside a single black eclipse. (Same as yellow flower.) Blue-Flower: The pdf for web file size is 176 KB. The twelve petals is comprised four curve objects (each represent three leaves) with blue fill and black stroke (same as red flower). The inner pistils is comprised of a single black curve imbedded inside a single brown ellipse. Why are these file sizes so different? The yellow flower has only nine additional petal curve objects compared to the red flower. Yet, the pdf file size is also nine times the size. Note, the the pistils are the same. The blue flower uses the same petals as the red flower. However the pistils were refactored into only two objects, one complex curve and one ellipse. The complex object was created by subtracting the 27 ellipses from a single ellipse. The result of this distillation of the pistils causes the pdf file size to grow from 32 KB to 180 KB. is there a knowledge-based article that will help me understand why this occurs and how to avoid these problems during design? Flower-Yellow.pdf Flower-Blue.pdf Flower-Red.pdf Flowers.afdesign
  16. 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
  17. 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
  18. 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
  19. 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:-)
  20. 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.
  21. 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
  22. 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?
  23. 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
  24. 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!
  25. 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
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.