Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Lee D

  • Posts

  • Joined

Everything posted by Lee D

  1. If you can come up with a recipe to reproduce the issue each time, it'll be something we can look into. Does the same occur with any files or just a particular one? Are you using macOS or Windows? Also try monitoring memory usage as this may of been the cause.
  2. Welcome @Gary M R to the forums. The Sources panel will only appear when certain tools (Healing/Patch tools )are selected after a focus merge has been completed. As using the Sources panel with these tools allows you to select the source image to use. In Affinity Photo on iPad the Sources panel isn't available as the UI doesn't have options for pop up/moving panels like the Desktop versions. This may be something that may be improved in a future release.
  3. That video from Affinity Revolution is using an older version of the app so the process has changed slightly. Instead of a two finger press hold, now just use a single tap and hold to bring up the menu. The Redo/Undo buttons have to be enabled within the apps Preferences > Interface before they will show on the apps main UI.
  4. @Geeth .afdesign files should be opening as it's our native file format, try moving the files from Google Drive as we've had issues previously with files not being recognised or corrupted. Depending on how the file was created, some elements may not be supported by the .SVG format and have to be rasterised on export.
  5. Hi @ericeric The FujiFilm X-H2 isn't officially supported by our RAW engine, so this may explain the issues you're seeing. It's also worth noting that RAW engines can develop images differently to others, and some Fuji files can have colour profiles applied. I can't give an eta on when that model will be added as we do use a third party RAW engine and have to wait for this to be updated first. We can then pull the update and add to our app.
  6. @polymath Sorry for the delay, I can confirm this is part of how the brush engine works. You can post in the Feature Requests section as a future improvement but I suspect it would require a complete rewrite of the brush engine.
  7. @Paul010156Not something I can reproduce on one of our Windows 10 test systems with that update installed, see the attached screenshot. Can you provide more information on your workflow and perhaps a screen recording.
  8. @Allison K Lynoo So far with your file I haven't experienced an issues. I can open, edit, save back to that file or use Save As to create a new version and then do the same tests with that version and still nothing. Can you check to see what else is running on your system at the same time, such as backup software. Perhaps try stopping or disabling them to see if it makes any difference? If any of the files are listed as Linked, are these stored locally?
  9. The devices listed in your Affinity account is just for reference, it doesn't actually effect anything. Our web team may add option to remove devices in the future just so it tidys the lists up.
  10. This thread is now locked. If you have a feature request please post in the dedicated Feature Request section. This allows other users to add their support to the request and should hopefully reduce the for/against as if you don't support the request there is no need to post.
  11. @Arne Drews Try renaming the 1.0 folder (C:\Users\xxx\AppData\Roaming\Affinity\Photo\1.0) to something else and restarting Windows. Once restarted open the app and check the autosave folder in the new 1.0 folder. Also do you have any backup software running, just in case?
  12. Hi @Hafizh K Welcome to the forums. Can you provide more information on the crash you experience, is this with just one document or any, even a new blank document with just some text and shapes? Which PDF preset are you selecting? Where are you exporting to, local storage or cloud/networked?
  13. Hi @marta.wojtowicz.ack Welcome to the forums. Can you expand some more on the issue you're having, how many layers are you copying in one go, have you tried reducing the amount? What type of layers are they? Does this occur just with one document or any? Can you please confirm your OS version and system spec as well, just in case.
  14. You may need to also check the file associations within your OS as well, right click on a .NEF file and check it's properties to confirm.
  15. Hi @wrandyr Welcome to the forums. Is it possible to provide me a copy of your document via DM as I would like to take a look at the layer structure. Have you tried moving them further up the layer stack?
  16. You can have multiple documents open within the app but the metadata would need to be edited manually for each and saved. You could potentially create a macro that could be run for each document, this may be a slightly quicker workflow.
  17. @SierbahnnIs it possible to upload a copy of the file here or if private send me a link in a DM. As I'd like to see how the document is setup as we do have a couple of issues logged with regards to autofit.
  18. @CrashXIf you're still having an issue perhaps upload a sample document, then visually show what's happening to it. This may give us a better idea as to what to advise.
  19. Hi @Chris_06 Welcome to the forums. Opening your file in Affinity Publisher (macOS) and printing to my Epson mirrors what's on screen, (apart from missing front) see attached screenshot. Both rectangles do seem to be setup the same, I also tested printing to a Samsung as that was the same. Have you tried exporting out as PDF? If this exports ok, then try printing from that. Another option would be on the Print windows under Rasterisation to rasterise the entire page before printing. Also try reinstalling your print drivers or check for any available updates.
  20. Can you please confirm which version of macOS you're running and a screenshot or screen recording of this happening.
  21. @Mike Steven I downloaded the ca files from Github and placed them in a folder named "ca" and placed it in C:\ProgramData\Affinity\Common\1.0\Dictionaries. I then restarted Publisher and checked the Character panel and they're available for me to select, see screenshot. I used the direct links to the ca files from the second post in this FAQ article, try these instead. They should be the same but it's worth checking, just in case.
  22. HI @Kevin Middleton Welcome to the forums. Open the apps Preferences > General, check to see if you have the option Import PSD text as text rather than bitmap enabled? If so there isn't anything else that we can do, your files would need to be opened in a newer version of PS and resaved which would update the file.
  23. @Grim72 Welcome to the forums. You should be able to use the installer without issue, please make sure you're entering the correct product key. If you continue to have an issue with the product key please DM me with a screenshot of the key entered (don't upload a screenshot of your key here) and message received and also your key as shown in your account.
  24. Our apps plugin support is designed to be as generic as possible and work with as many plugins as it can. However some may not work for various reasons such as colour modes and I believe Photo AI is still in beta testing and is primarily designed to interface with the three other Topaz plugins.
  25. It's also crashing for me, even if some/all of the steps are removed. Without knowing the exact record process it may be difficult to narrow down the cause. Can you try recording the macro again but also recording the screen at the same time so I can see the whole process. In reference to the included document, any particular reason for the layer structure?
  • 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.