Jump to content


  • Content count

  • Joined

  • Last visited

About LCamachoDesign

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,033 profile views
  1. 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!
  2. 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
  3. LCamachoDesign

    Insert actual date

    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.
  4. 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!
  5. 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!
  6. 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).
  7. LCamachoDesign

    Place Randomly Changes to TXT Instead of All

    I've noticed this on Publisher as well.
  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. LCamachoDesign

    Custom Fields

    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!

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.