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

Leigh

Staff
 View Profile  See their activity

  • Posts

    3,217

  • Joined

 Content Type 

Everything posted by Leigh

  1. Leigh
    To enable PDF logging on macOS: Quit Affinity Start Terminal Type the below (ensuring you change 'yourusername' for the name of your user folder) and press Enter to execute the command launchctl setenv PDFLIBLOGGING "filename=/Users/yourusername/Desktop/PDFLib.log" Run Affinity and export to PDF and then click OK to accept the error message Go to /Users/yourusername/Desktop and send the newly created PDFLib.log to the support team as requested. (Ensuring you change yourusername as required) To disable PDF logging on macOS: Quit Affinity Start Terminal again Type the following to stop the logging and to return your settings back to normal launchctl unsetenv PDFLIBLOGGING
  2. Leigh
    If you're having issues exporting to PDF, you may be advised by the Support team to enable PDFLogging. This will allow our developers to look into your issue further and hopefully figure out what's causing the issue. For Windows: Create a folder called temp on the root of your C:\ drive so you have folder at C:\Temp\ Run PDFLibLogging.reg - this will create a registry entry that enables logging for PDF Export Run Affinity and export to PDF and then click OK to accept the error message. Go to C:\Temp\ and send the newly created PDFlib.txt file to the support team as requested Now run PDFLibLoggingRemove.reg to return your settings back to normal PDFLibLogging.reg PDFLibLoggingRemove.reg
  3. Leigh
    Thanks for the clarification and information. If you run into similar issues after updating to 2.0.3 and are able to replicate them, please start a new thread in the bugs section and we'll take a look 👍
  4. Leigh
    Looks like you've managed to resolve the issue. Out of interest, what was it?
  5. Leigh
    After installing 1.10.6 are you still having issues scrolling fonts or just with the Resource Manager? If it's just the Resource Manager then you could have a different issue. Are you having the same issues with V2 too?
  6. Leigh
    This issue should be resolved in the 2.0.3 updates for macOS.
  7. Leigh
    This should be fixed in the 2.0.3 update released late yesterday.
  8. Leigh
    We've finally got round to replying to your email - feel free to reply there or here.
  9. Leigh
    You can follow this thread to be notified when it's available:
  10. Leigh
    We've had numerous reports of this issue and it's currently logged with our developers.
  11. Leigh
    Avez-vous toujours des problèmes pour réinstaller la V2 ? Si oui, veuillez fournir plus d'informations.
  12. Leigh
    This should help: https://forum.affinity.serif.com/index.php?/topic/169443-fixed-saving-to-an-external-drive-gives-failed-to-save-document-error-on-macos-ventura/&do=findComment&comment=1007308
  13. Leigh
    @HeyTheresTony We've been able to replicate this issue with V2 and it's logged with our developers.
  14. Leigh
    Unfortunately, this is a known issue and will be fixed in the next update. If you haven't already, please contact your account manager or send email to corpsupport@serif.com we can offer you a working solution.
  15. Leigh
    Thanks for the offer and if I think of anything else, I will let you know. I'm sorry that I couldn't find the cause of the issue but Windows can be a mystery sometimes
  16. Leigh
    Did you use the Move app option in Apps > Apps & features or did you move the folder yourself and create your own symbolic links?
  17. Leigh
    I've not forgotten about this. I've been continuing to look into this and i'm still having issues trying to move the app. I did try another MSIX app and that also had the same issue when trying to move it and gave the same error. I tried all the solutions listed here and a new user account and the same error occurred. I couldn't find much related to the error 0x80073CF6 but when I tried using Powershell to move the app, I got a more detailed error log: AppX Deployment operation failed for package SerifEuropeLtd.AffinityPhoto2_2.0.0.1640_x64__3cqzy0nppv2rt with error 0x80073CF6. The specific error text for this failure is: Authorization of capabilities for SerifEuropeLtd.AffinityPhoto2_2.0.0.1640_x64__3cqzy0nppv2rt failed with error code 0x800701C5. I've logged this with our developers to see if it's something they're aware of. If/when I get an update, I will let everyone know.
  18. Leigh
    This thread is now closed/locked. This thread has been reported several times and everything that needs to be said has been said. Here's a link to the forum guidelines for anyone needing a refresher: https://forum.affinity.serif.com/index.php?/guidelines/
  19. Leigh
    Not to be a killjoy or anything, but just wanted to reiterate what @T V mentions in his original post. Please make sure you backup your propcol files before overwriting them or messing with them, especially now that Affinity V2 shares content types such as Assets, Brushes, Swatches and Styles between Affinity apps. You may think you're only affecting one app but it could have a knock on effect to other apps and/or personas. Don't want to stop users sharing content to help others but also don't want users losing any data
  20. Leigh
    Wir planen, MSI-Dateien wieder verfügbar zu machen. Sie können diesem Thread folgen, um über Updates zu seiner Verfügbarkeit benachrichtigt zu werden.
  21. Leigh
    Okay, halte mich auf dem Laufenden 👍
  22. Leigh
    Ich bin mir leider nicht sicher, was ich als nächstes vorschlagen soll. Ich denke, das Problem wird darauf zurückzuführen sein, dass Sie auf den WindowsApps-Ordner zugreifen können - dieser Ordner ist normalerweise gesperrt und für Benutzer nicht zugänglich. Wenn Sie den Inhalt dieses Ordners anzeigen können, wurden die Berechtigungen geändert. Ich habe in einem früheren Beitrag vorgeschlagen, ein neues Benutzerkonto auszuprobieren, um zu sehen, ob das funktioniert, aber Sie sagten, es sei nicht möglich. Liegt das daran, dass es sich um eine Business-Maschine handelt?
  23. Leigh
    I'm sure it's something our QA team will test when they get their hands in the MSI builds. When we know more will let everyone know.
  24. Leigh
    No ETA yet but it's being worked on.
  25. Leigh
    We're expecting the issue saving to exFAT, FAT32 and FAT external drives to be fixed in the next update for both V1 and V2. No ETA for when that will be but hopefully not long.
×
×
  • 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.

 Accept Cookies  Reject Cookies