Jump to content


  • Posts

  • Joined

Everything posted by Gabe

  1. @Luis Fernando please create a new post in here> https://forum.affinity.serif.com/index.php?/forum/5-affinity-on-desktop-questions-macos-and-windows/
  2. Judging by the error message, it sounds like it lost the connection to your external drive while you were working on it. If all was fine working locally, that's most likely what's happened. Private relay has nothing to do with this. It's a form of VPN > https://support.apple.com/en-gb/HT212614
  3. Hi @AtlSteve902, I doubt this would be a macOS Ventura issue. Where was your file originally stored? (before the save-as)
  4. We cannot come back to every single thread to mark issues as fixed. Instead, we have a fix list with every new release. So this would have been listed as fixed in 1.8 I believe.
  5. Back in 2019 there was indeed a problem when inner bleed was 0, but it had been fixed a couple years ago. @Customer Feedbackhave you tried it and still have an issue when innerBleed = 0?
  6. Those EPS files are very complex and have thousands of nodes. Because of the way assets work, they load up in memory, which may slow down lower end machines (or iPads). We decided to supply them as separate EPS files which can be placed on the canvas (rather than being "opened"), which has a much lower memory hit.
  7. No need to. I've bumped it on out end as it doesn't seem fixed in the latest version. Cheers!
  8. What happens if you export them locally and not on the network ? Any macros running?
  9. I'm afraid we can't provide a timeline for bug fixes. Sorry.
  10. You can try and generate a DMP while it's not responding. Go to Task Manager > Affinity Designer > Right click > Create dump file. You can then upload it on this link: https://www.dropbox.com/request/vqWSLSXnEwT4Yf5rljXX What you could try is reset the whole app back to default. With Designer closed, Hit Windows + R , type %appdata%\Affinity\Designer\ and hit Enter. Rename the 1.0 to 1.0.backup and re-launch Designer. This will reset everything to factory default.
  11. Hi @eldritch mouse Welcome to the forums. We are aware of this issue and it has already been logged with our developers.
  12. Hi @GregMcMahan, Can you upload a sample file on this link? https://www.dropbox.com/request/zr3j7jP2bg3wkJoFcqzx
  13. It's probably fixed in this case. Give us a shout if you can still replicate it in Pub (once it's out)
  14. Hi @Rondem, This is by design. if you group adjustment layers (or put them in a symbol) they will affect everything below them. They will only affect the group they are in if you have a pixel layer or shape inside that group.
  15. Hi @abarkalo, It's most likely the same delay issue introduced by Monterey. Can you replicate it in the latest Photo Beta?
  16. Hi @Max N, This is the excepted behaviour However, we don't have a Publisher Beta running at the moment. Going forward, please use the retail version and report bugs in the correct section and not the beta forums.
  17. Hi @EverDavila, Please create a new post following this guide: https://forum.affinity.serif.com/index.php?/forum/71-bug-reporting/
  18. Just double checking. Is this lock-up related to the autoclick action?
  19. Thanks. I will get this logged. Let us know if it happens again, as it might be a recipe to recreate it somehow.
  20. Yeah sure https://www.dropbox.com/request/qR32JNgTsSuuVzf76fr0. Is it fine on a new doc?
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.