Jump to content

relayer35

Members
  • Content count

    6
  • Joined

  • Last visited

  1. relayer35

    Brush tool very laggy

    I have also found the new version to be very sluggish with the brushes. There is a real delay that makes it hard to work with. I also have issues where the application itself does not render properly, in the section on the right with the adjustment, layers, effect tabs, etc. I used Time Machine to restore back to 1.6.7, but left 1.7 on the machine as well for now. I still have the old issue with getting the access denied message opening files which is supposedly because of too many fonts on the machine (down to 139 fonts). I was hoping 1.7 would fix that but it didn't.
  2. I cut down to 139 fonts, still having the problem. And no, I get that message regardless of if I open a file from the local hard drive or a network drive. I’m usually opening the files from my local drive.
  3. How many fonts do I have to trim down? Looks like there is 245 on my machine now.
  4. Why on earth should the number of fonts affect an image app, and why should it give a permission error? I shouldn't have to delete fonts in order to open an image file. (FWIW, I didn't go out of my way to install fonts, they either came with the OS or were installed by other programs). This is the only program I have that has this issue,
  5. I've had the problem on both High Sierra and Mojave
  6. I am having the same issue. It will open and save files for first few times, but after working on a number of files I get the "Failed to Open File" message box saying that "The file could not be opened because permission was denied". If I close Affinity Pro, and re-open it the file opens correctly. I haven't been able to figure out any sort of pattern as to how many files I can work on before getting the message, or how long the program is open. I tried the steps outlined here for cleaning the font cache but it did not solve the problem. I don't know why fonts would have anything to do this anyway. This seems like a problem that should be fixed by the developer.
×

Important Information

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.