Jump to content
You must now use your email address to sign in [click for more info] ×

Leigh

Staff
  • Posts

    3,221
  • Joined

Everything posted by Leigh

  1. I have logged your document with our developers to see if they can figure out what's causing the issue. When I have an update, I will let you know.
  2. Pruned and locked. William has provided his feature request but as others have pointed out, it's been requested before. No need for another thread on this.
  3. Hi @Hilltop - Just wanted to let you know that I can replicate this on Windows using both 2.4.2 and the 2.5 beta. I'm just waiting to hear back from our QA team to see if they have any idea what this issue could be or if the document needs logging with our developers. Will get back to you as soon as possible.
  4. @Hangman I'm being lazy, so here's a link to @Lee D response in another thread that relates to this one
  5. Sorry about this - I will get someone to look into this ASAP and get back to you with an update.
  6. Thanks for your patience @Granddaddy you'll understand we've had a much higher volume of contacts to respond to since the announcement but to answer your question, things will remain the same i.e the forums and Technical Support will remain free.
  7. Thank you for the PM and Link - will have a look and get back to you ASAP.
  8. Thanks for posting and sorry for the delayed response. I think i've found the post you're referring to and you're right, there's no real outcome. So that I can look into this further and hopefully get some answers, can you send me an example Publisher document showing this on export? If you require a dropbox link, just let me know.
  9. That's disappointing to hear. If you haven't already, can you update to 2.4 and send me a Crash Report from this version? Is it also possible to send me your Log.txt from %APPDATA%\Affinity\Publisher\2.0\
  10. Just wanted to let you know that I've logged this with our developers.
  11. Sorry to hear that you're having these issues when making changes. Can you check to see if you have OpenCL enabled in Edit > Settings > Performance. If you have, please disable it and try again.
  12. Welcome to forum @Feystag - I don't have much experience with FontForge but I've just created a crude font with it and wasn't able to replicate the issue on macOS. After updating my font, exporting and importing in Font Book, it's still detected in my AFD document correctly and the characters remain. If you could provide more details of the steps you're taking or some example files we can investigate this further for you.
  13. @NotMyFault Just wanted to let you know that we've not forgotten about this post - we're trying to get some clarification on this issue for you. When we have an update, we'll let you know.
  14. A small number of users are running our x64 (64 bit) apps on Windows ARM with an ARM CPU. After updating to 2.4 they have noticed that documents fail to render when loaded into the app. This is a known issue and appears to be related to OpenCL being enabled in the 2.4 update. Turning off OpenCL should resolve this issue for now. To do this, go to Edit > Settings > Performance and untick Enable OpenCL This has been logged with our developers to be fixed.
  15. We've had several reports of RAW files having Artefacts or Green Lines after updating to 2.4 on Windows. This is a known issue and appears to be related to OpenCL. Turning off OpenCL should resolve this issue for now. To do this, go to Edit > Settings > Performance and untick Enable OpenCL This has been logged with our developers to be fixed.
  16. Thanks for the update @Demys - Is it possible to install the 2.4 update and see if the issue sill persists?
  17. I completely understand your frustration @rikkarlo2 I have bumped this logged issue with our developers.
  18. Not yet, sorry. I've bumped the bug report with our developers.
  19. I understand you're frustration and if we knew what was causing your issue, we would provide a fix but unfortunately, your issues appear to be isolated to your setup or workflow. All of the advice we have given so far would normally get us to a point where we can replicate or find the cause of the issue but that's not the case for you, sorry. We will continue to investigate but without us being able to replicate the issue or get any meaningful information from your crash reports, it's proving tricky. Did you manage to try the advice from @debraspicher posted above? If so, what was the outcome? Can you provide a copy of your latest logs from EventViewer (steps on how to do that can be found here) and will get a developer to have another look to see if anything springs to mind.
  20. I've removed the files from your post but i've made them available to our support team.
  21. Thanks for your patience. I've had a look at your Log.txt and it looks like the drivers for your GTX 1650 SUPER are 31.0.15.3619 but the latest version is 31.0.15.4609. It also looks like your UHD Graphics 630 drivers are 27.20.100.9664 but the latest version is 31.0.101.2125. Is it possible to try and update to latest version for both to see if that improves things? Also, have you been able to try the 2.4 beta to see if that provides better stability?
  22. Can you try the steps mentioned in this post to see if that improves your situation?
  23. Just wanted to post a quick update on this. Our developers have confirmed that it's a bug and will be fixed in an upcoming update. Thanks for letting us know.
  24. Thanks for log file and the additional information. Sorry to be a pain but would it be possible to delete the Log.txt that's currently in %AppData%\Affinity\Publisher\2.0\ and then launch the app again to generate a new one. Once you've done this can you send this again to me and also include a screenshot of the devices listed in Edit > Settings > Performance > Renderer?
×
×
  • Create New...

Important Information

Terms of Use | 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.