Jump to content

LCamachoDesign

Members
  • Content Count

    211
  • Joined

  • Last visited

Everything posted by LCamachoDesign

  1. Hi! Drawing using symmetry and mirroring works fine, there's a tiny bit of slow down sometimes, but nothing too serious. But drawing using only symmetry is a lot slower, to the point is almost unusable. I find it odd since I'd presume both functions would work the same. See the attached video for a visual sample of the issue. Happens on an iPad Pro 9.7" (2016) with the latest iPadOS (13.3.1) and latest Affinity Designer (1.7.3). Thanks! RPReplay_Final1580374739.mp4
  2. You have to be kidding me... it does work! The performance goes back to Photo levels, and it also solves the first stroke delay after zooming I reported in the other topic. Thank you! This solution would have never crossed my mind... this does happen frequently with Affinity applications though. More than once I come across "issues" for which the solutions are already on the app, they're just sort of hidden away. For this situation I think a UX tweak would help users a lot, especially in lower performance devices. First there should be an application-wide option saying something like this: "Change view modes to match the Persona" This option would work like this: If in Designer Persona Then View Mode is Vector Else If in Pixel Persona If Document Type is Devices (Retina) Then View Mode is Retina Pixel Else View Mode is Pixel End If Else If in Export Persona I'm not quite sure? Perhaps Vector view mode again? Or Retina Pixel if the document is Devices (Retina)? End If Then, upon the first time a user switches to the Pixel Persona a popup or something should ask the user if they'd like to enable this option for a more accurate preview of the pixel artwork and enhanced performance. Another alternative would be to have an option to make the view modes sticky in regards to the persona being used. So if I change the view mode on the Pixel Persona to Pixel, then it will always change to that whenever I return to that Persona on that document. If I set the view mode to Vector in the Designer Persona, then it will change to that mode whenever I return to it. This way you can seamlessly switch between high precision vectors and high performance pixel whenever needed. I still think the performance difference is so large that by default Designer Persona should be Vector view, and Pixel Persona should be pixel view. Let the user change it if they want, but let this be the out of box experience so the optimal performance is not hidden away! You can say my iPad is old, which is very true, and on a brand new 3rd gen iPad Pro you can barely tell the difference (not sure if that's the case, but let's go with it). The thing is Apple keeps selling iPads with low processor power even right now, so this is not an issue that will go away on it's own anytime soon. Implementing something along this lines will help these people achieve maximum performance on their brand new, albeit slower, iPads. Thanks!
  3. 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
  4. I came here to post a request precisely because of this situation. MrDoodlezz explained the issue I'm having word by word. +1 from me, a new field with a running clock is needed.
  5. Came here to report just this. I'm having this issue as well. Fortunately, on this particular document I only have 1 link in this situation, but it would be quite a hassle if I had many more. Thanks!
  6. I've noticed something related to this. When you pan/zoom somewhere, the first pixel brush stroke is slow, but subsequent ones are reasonably faster. Don't know if this is already known or if it will help you. Thanks!
  7. I'm having the same issue, just 6.26 GB instead of the 70s reported by others. Still annoying since I can't control what's going on. I've closed all documents and it made no difference (I only had one open anyway).
  8. I can, it's just less noticeable. If you want the document anyway let me know where I can send it privately. Thanks!
  9. Came here to post this. Custom fields, also known as text variables on other softwares, would be a massive help in template documents. Currently I have a template (actually just a regular document I copy elsewhere whenever needed since Affinity Publisher does not have a true template function) for my design proposals, and I have to Find & Replace things like client name or project name so it changes across the whole document. If I could define, insert and later edit a field such as client name, I wouldn't have to Find & Replace all the time. Thanks!
  10. No, not really. What really works if you want to do an urgent save to work on the desktop is just save a copy (so a new file). That always works. Then you can delete the original file, work on the copy on the desktop, and rename it back to the original file name.
  11. 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
  12. No? They're in separate palettes. One of they things you can do with two folders is precisely having two files with the same name. C:\FolderA\File.txt and C:\FolderB\File.txt
  13. I just came across a most perplexing limitation: I've created two document palettes, let's call them A and B On palette A I've created a swatch named ColourPink Then I went to palette B and also tried to create a swatch called ColourPink Affinity Designer tells me the swatch name is already in use so I can't use it again... Well... I guess that's technically true, but what's the point of having two separate palettes if they're not completely independent? My request is to make palettes completely independent so we can have multiple swatches with the names. Thanks!
  14. I'm going to start by saying that I don't fully know if this is a Designer error, an error on OneDrive, or it's just that Files app work on a weird way. Looking forward to some clarification on this, and now onto the problem: Open an Affinity Designer file stored in OneDrive by using the Open from Cloud command, notice the document's Modified date/time Do some changes, doesn't really matter what they are, just enough to warrant a file save Save the file by using the Document > Save command, or by going into the home hub and choosing Save on the document's hamburger menu Go iOS's Files app, notice the file Modified date/time Sometimes the file will be updated and show a new Modified time/date, other times it won't update at all and will show the old time, like the file was never changed/saved If I open the OneDrive itself, or check the OneDrive folder on my desktop, I can confirm no file saves happened, so it's not just a visual glitch Closing the file within Designer and then closing the app itself sometimes triggers a file update, other times not so much... I don't really have anything else more specific to say about this issue. I can't reproduce it consistently, but it does happen very frequently. I also can't trigger the upload consistently, but closing the file & Designer works a significant amount of times. I'm using the latest stable versions of iOS 12, OneDrive and Designer, so no beta software here. Any ideas at all about what's going on?
  15. Yes, really. Right now if you want to edit a swatch name you have to right click it, choose Rename, and then you are shown a dialog box. If you have to be presented with a dialog box, you might as well be shown all options, so you have the opportunity to do further edits to the swatch. This is how Illustrator does it and I've never seen anyone complain about it. About the swatches names, Affinity (and Illustrator) only show the name in the tooltip. Like you said, the name should auto update when you change the value, the best way to do this is by copying InDesign swatch dialog. Also showing the value in the tooltip if it differs from the name is an interesting idea!
  16. Hi! I've recently got access to an iPad Pro and I've been dabbling with Affinity Designer. Great stuff, but I've ran into limitations that break my colouring workflow. First let me explain how I do it on the desktop: Draw a vector shape Apply a global colour to this shape Create a pixel layer inside the shape Apply a Colour Overlay effect to the pixel layer Attribute a global colour to the above effect Draw on this layer, the pixel brush colour doesn't matter since the Overlay effect always overrides it Repeat steps 3. to 6. for every colour I want to draw inside the shape Move on to the next shape and start from 2. again This way if I want to change any colour after the fact, all I have to do is edit the global colours and all parts of the illustration respond accordingly, even the pixel layers. The iPad version of Affinity Designer does not have global colours, nor it does not support attributing swatches to layer effects... this fundamentally breaks the method of controlling colours described above... I've already requested both features on the appropriate forum, but until they get implemented I'd need an alternative method. My question is, what alternative methods of recolouring the artwork should I use? What do you use when you want to recolour the artwork after you're done? Thanks in advance!
  17. I've searched this topic but couldn't find anything going into the point I'd like to make, at least not directly. I feel the development cycle of Affinity products is unreasonably long. Version 1.6 was released on November 2017, version 1.7 was released June 2019. That's 1 year and 7 months! I think it's a lot more reasonable and useful to everyone involved to release one new feature or improvement every month or two months at latest. I understand that larger features take a lot of time to develop and sometimes require changes to the underlying architecture, these can't be pushed out monthly obviously. But a lot of the pain points of Affinity suite are often small naggy things that could be fixed/changed/added within a month. Take the Swatches panel for example. Renaming, editing colour value, changing global/overprint/spot status, are all done with different right click menus and dialogs... but Affinity already has a near perfect unified dialog for this, just go to Swatches > Add Global Colour. The finish dialog would need a toggle defining the colour as global/regular at the bottom, and a toggle to name with swatch with the colour value at the top. Then a very quick fix for this pain point would be showing this dialog when double clicking a swatch and get rid of all other menus and dialogs. Let's say Affinity replies "great idea, we'll do it!" … right next to "we'll show it to you in a year and half! Talk to you in 2021!"... Thanks I guess? I'm pretty sure this feature could be pushed in a 1.7.2 release instead since most of the work is already in place, it's just a tweak to the interface. Another confusing choice in the Swatches panel is this, create a global colour then right click it and do Add Chord to Swatches > Tints. All tints added are regular colours... if I right clicked a global colour and asked for tints, there's a very good chance I actually want all these as global colours too... I now have to right click and Make Global each and every single swatch... The fix for this is making the chord swatches the same type as the origin right clicked swatch. Again an easy fix. Affinity might think I'm some sort of brilliant UI engineer (as if...) and implement this, but if it takes waiting until 2021 to see it then it's not so great. This could be included on 1.7.3 instead. And so on with all the small fixes and changes here and there. This does not stop big features coming out as major point releases, these can still happen obviously. But bringing QOL improvements every month is a much better approach to deal with issues and difficulties that manifest on day to day work. Thanks!
  18. I'm going to bump this topic with my +1 I've recently tried the iPad version of Affinity Designer and the touch interaction is much better! I disagree with bringing the whole iPad UI to the desktop, mostly because there's some key features missing in the iPad (global colours, swatches on layer styles...), but I do agree in bringing the Windows touch interaction to the iPad level. Thanks!
  19. When you select a path with a vector brush already applied, the Brushes Panel should show which brush that is. Right now it's impossible to know for sure which brush have you applied to a path once you deselect it. If you look at the attached image the applied brush is clearly not the brush shown in the Panel. When you select the path the Panel should automatically select the correct brush (which is a few brushes up in this particular case). I'm requesting this under the desktop section of feedback, but this same request is equally valid for the iPad. Thanks!
  20. Ability to apply colour swatches to layer effects, such as the pictured Colour Overlay. Right now you can only use sliders and wheels on these. This is particular useful when used in conjunction with global colours. You can apply a global colour to a large number of layer effects, and change every single of them instance just by editing the global colour. I use this a lot in illustration, rather than paint any drawing in it's 'final colour', I have the brush set to black and the layer with a colour overlay effect attached to a global colour. If I later want to change the illustration colour I just edit the swatch. Thanks!
  21. I've searched around and while I see people asking about this, doesn't seem like there's any kind of formal request for this feature so here's one. Essentially it's what the title says, please add the ability to create, edit and apply global colour swatches in illustrations and designs done on the iPad. Global colours are a fundamental part of vector design and illustration, the need for this is vital! Right now the only workaround is to create them on the desktop and then open the file on the iPad, but this has limitations besides not being able to edit the swatches on the device itself. For example if you apply a global to an object, the swatches panel will not indicate in any way that the colour is apply to the object, unlike in the desktop where you can see the swatch highlighted. Thanks!
  22. +1 on the ability to create, use and modify global colours. I've recently got a hold of an iPad and discovered this issue. Kind of a show stopper since I use them extensively... I also noticed you can't use swatches, even the normal kind, in layer effects such as Colour Overlay... I honestly think the swatches panel needs a big overhaul, both desktop and iPad. I mean just have a look at the how the Swatches panel works on Illustrator and copy it, then sprinkle a bit of InDesign features into it and you have a perfect panel. No need to reinvent the wheel. I'm always puzzled on how these things happen, Adobe's swatches panels are widely known, there's no way the team didn't know them. It's almost like they decide on a meeting that "we know these panels works great, so instead let's make something similar, but that works worse!"
  23. This bug is rather tricky to explain in words, so you'll just have to look at the attached documents and images. Pay attention to items circled in red on these images. Open the attached Test.afdesign file Notice how the blue rectangle looks like and how the effect was achieved in the attached Affinity.png image Export the Affinity file to a PDF/X4, default settings Open the PDF in Adobe Reader (or any PDF reader), notice how the white texture is almost invisible as seen in Acrobat.png image Open the PDF in Illustrator CC 2019 Examine the clipping mask and group structures, notice the group containing the white brush texture has 20% opacity applied as shown in Illustrator-1.png Set the said group opacity to 100%, as shown in Illustrator-2.png, notice how the brush texture looks correct now Affinity Designer is rasterizing the opacity of the brush texture layer, then applying the opacity again to this rasterized layer. So the final transparency is 20% of 20%, that's 4% transparency at the end. Strangely this bug does not happen if the Colour Overlay effect is not used, check the Test-NoColourOverlay.pdf file. Moreover, this bug is transversal to all Affinity apps. You can trigger it in any of the apps. Even more interesting, this bug shows even if the file is not directly exported, you can trigger it in Publisher by linking to the file. This one is easy to explain in words: Open Affinity Publisher and create a new document Use File -> Place… and place the Test.afdesign into the document anywhere visible Export the Publisher document using the default PDF/X4 settings The same bug will show up in the exported PDF The only work around I've found so far is to disable "Allow advanced feature" under "More..." PDF export. This flattens all transparency. Or use other presets (X3 or X1a) that don't support live transparency anyway. The issue with this is these presets don't output that good results in Affinity... X4 is the best to keep fidelity to the original file. Thanks! Test.afdesign Test-NoColourOverlay.pdf
  24. If you change the displayed/active artboard of a multi artboard Designer file placed on a master page, this change won't be reflected on regular pages. It always shows the artboard that was first visible upon placing the file. It's possible this also happens with other types of multipage documents (Affinity Photo, PDFs) but I only tested with Designer files. Steps to reproduce: Open Affinity Designer Create a new document with 2 Artboards Draw a purple circle on the first artboard and a blue square in the second, just so they're instantly recognizable Save it somewhere, you can now close Designer, it won't be used anymore Create a new Publisher file, check Default Master so a master page is already applied to any pages added Add a few pages to the document, let's say 6, just so the issue is more evident Double click Master A in the Pages panel so you can add elements to it Place the Designer document you saved on step 4, by default it should show the first artboard, the purple circle Notice the purple circle is correctly displayed on all pages where the Master A is applied Back on the Master A, select the placed file and use the context toolbar to change to the second artboard You should now see the blue square on the master page as expected Notice that the blue square is not being shown on the pages where the master is applied, instead you continue to see the purple circle This is not just a visual bug, if you export a PDF all pages will indeed have the purple circle instead of the blue square Thanks!
×
×
  • 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.