Dan C

No problem at all, thanks for the further information provided! I personally run Affinity full screen at both 4k 60hz and 1440p 144hz without issue, so the app certainly isn't limited to 1080p. I have also asked my colleague, who has used both a 49" Ultrawide G9 Odyssey and a 37" Ultrawide Alienware OLED with Affinity to try full screen mode, and this too has worked without issue, reaffirming the above. However, I did not check the scaling % my colleague is using (I'm personally set at 125% for my 4K monitor) - what value were you using that caused the crash to occur please? Assuming that you installed the apps from fresh on the new device, then all of your settings would have been generated from scratch. The app could only be using previous settings if you had Affinity installed on the old PC, then transferred all files & installed apps to your new PC, using third party 'transfer' software. To be certain however, we can try the following: Return Windows scaling % to the values you were using previously, when the crash occurred. Open the Affinity app, holding down the CTRL key whilst the app loads. In the 'Clear User Data' dialog that appears, enable the following options: Select Clear and the app will now open, having reset these values. Follow the same steps you used to trigger the crash in Affinity - does this still occur? If so, this would indicate that previous settings are not the cause of the issue here. Please do let me know how you get on

Many thanks for letting me know @Antonio Peregrino, I'm glad to hear this issue has been resolved for you. Absolutely, the Affinity team don't expect this issue to occur and we're investigating this further internally to be fixed as soon as possible. Thus far we have found many reports of other applications and Cloud services experiencing issues with macOS Sonoma, and we believe the issues reported here are related, for example: There are known issues with Sonoma and iCloud: Reports for OneDrive and Sonoma having sync issues, As well as issues with Dropbox and Sonoma (note the number of users 'me too-ing' the thread. According to Dropbox themselves, there were expected changes coming with a previous macOS version due to the File Provider API Apple provided - https://help.dropbox.com/installs/macos-support-for-expected-changes My current suspicion is that the 'long standing bug' mentioned in the above quote has affected this File Provider API, causing the loading delay in Affinity but this is only my best guess. This would also explain the reason that simply waiting for the app to open the document eventually resolves the issue and then no longer occurs for the user - as the time waited allowed for their files to be redownloaded/cached by macOS. Therefore this may require Apple to resolve, rather than the Affinity team as the issue appears to affect many users and applications since updating to macOS Sonoma. I hope this clears things up!

That's certainly strange, provided the logging was enabled before you tried exporting the file, this should have been generated - so I'm not entirely certain for the cause of this. If you're unable to produce this log then we will likely need to see a copy of the Publisher document, alongside any Linked images/fonts used in the file, to see if we can replicate this behaviour here. Therefore can you please create a Package for your document and upload the entire Package folder to the below link for me: https://www.dropbox.com/request/6WLn9nGXaF2xTLdRdk4B Once uploaded, please reply here to let me know. Many thanks once again

Apologies, thanks for the clarification - I certainly understand now! Does the app generate any crash reports? You can find out how to locate these here - If so, can you attach a copy of the latest 2-3 reports here for me? What location are the Publisher documents & linked files stored? Are these on an internal disk, external drive, Cloud/'syncd' location etc? Many thanks in advance

Thanks for your report and files provided! I've been able to replicate this issue and I've logged it with our development team to be resolved ASAP. I hope this helps

Welcome to the Affinity Forums @oskarbravo Sorry to see you're having trouble! This isn't like any issue I've seen being reported previously and I'm certainly surprised that disabling Hardware Acceleration / clean installing your drivers hasn't changed the experienced behaviour. Just to confirm, did you update to the latest GPU driver version available when performing this clean install? I can see from debugging the crash report provided that Avira Endpoint Protection is 'hooked into' the Affinity app, as the .dll is included with the crash report. Out of interest if you temporarily disable this on your PC, does the crash still occur? Equally, the application is crashing within "LibPersona" which could indicate an incompatibility with your app layout or display settings - we usually see this when a user transfers the Affinity apps to a new device and the previous devices display settings are used. Have you recently transferred the app from an old device, by chance? Many thanks in advance!

@NAK, The most useful file you can provide here would be the log generated with PDFLib Logging enabled, as Walt suggested above - This log file will be generated, even if the app fails to export to PDF and should provide more insight into the cause of this issue. Many thanks in advance!

Hi @Darner, Sorry to see you're having trouble! I'm unable to replicate this in a new document currently, however this may depend on how exactly you have created/synced these Symbol layers, and potentially may be related to Constraints - though I'm unsure if these have been used in your file. Can you please attach a copy of the document that shows this issue here for me? If you'd like a private upload link for the file, please don't hesitate to ask. Many thanks in advance

Thanks for verifying that for me I can use the 'Collect' option in Publisher to convert these back to Linked files on my end, hopefully allowing me to replicate your issue - assuming the embedded documents in the files provided above are the same as the linked documents that were causing this crash. I note in your report above you mention the crash occurs when you have the Parent file open (where the images/documents are linked) and you then open one of these linked files for editing in a separate tab within the Affinity app. Does this occur when opening any of the linked files from this document, or only specific ones?

Apologies I forgot to include that within my original response, but I can confirm I found this was true during my testing!

Thanks for the above Hangman, I concur that the Hue value seems to be the trigger so I'll update the development log with this now. Strangely however I'm not seeing the re-draw issue across the shape that's shown in your recording - the whole shape is coloured incorrectly for me, seemingly regardless of document/rectangle size, but I will note this with the team also

Thanks for your report @Luc(as) and we're sorry to hear this document was lost. I can confirm this is already logged as a bug with our development team - I'll be sure to update this log and 'bump' this with the team to bring it to their attention once again. I hope this helps

Hi @josephhansen, Sorry to see you're having trouble! Can you please open Edit > Settings > Performance and provide a screenshot of your settings here for me? I'd also like to request a copy of the apps log.txt file - to find this please open Windows Run (Windows Key + R) then paste the following string and press OK: If using MSIX - %USERPROFILE%\.affinity\Photo\2.0\ If using EXE - %appdata%\Affinity\Photo\2.0\ In the window that opens, please select log.txt, then attach this to your reply here. Many thanks in advance!

Just to confirm, this has been logged with our devs as a bug - if you first select the left or right hand page from a Spread and use this option, the view is correctly centred on the selected page, however if you have the Spread itself selected then the left page is always centred incorrectly: 2023-10-12 11-32-52.mp4 I hope this helps

Thanks for the screen recording & steps provided! Interestingly I'm unable to replicate this issue on Windows, as adding the HSL adjustment does not change the colour values in any document - however I'm seeing this same behaviour on macOS and this certainly isn't correct, so I'm logging this as a new issue with our team now. In further testing, on macOS I can only replicate this when selecting the Red Swatch from the 'Colours' Palette, if I select a Red Swatch from any other Palette, or manually input the colour values, this works as expected. This would also explain why changing the Colour Profile in use would resolve this issue, as this converts the colours in use for the object and stops using the fill from the Swatch. I don't quite understand how this only occurs with the Colour Palette, though I'm sure our dev team may have more insight here. I hope this helps

I can confirm this issue is still logged with our development team and has not yet been marked as fixed, my apologies. I'll be sure to 'bump' this with the team now to bring it to their attention once again - from our testing it appears as though the documents size is a contributing factor. Smaller/lower resolution documents do not appear to trigger this issue, though larger/higher resolution documents can cause this to occur each time when returning to 'Live Docs'. Our apologies for any inconveniences cause due to this in the meantime.

Thanks for the further testing conducted here @dlampel! Both of your files provided above have multiple embedded documents/images - can you please confirm which specific embedded resource you are referring to?

This is expected behaviour with Artboard documents when exporting to PDF - each Artboard will be exported as a separate page within the PDF document, though the Export Dialog Preview will only show the 1st page of the multi-page document, hence the preview shown above. If you want to export all Artboards within a singular PDF page, there are 2 options. You can either use the Export Persona, setting the document slice to PDF - 2023-10-12 10-50-26.mp4 Or you can create a singular Artboard that encompasses the size of all your Artboards in your file, then nest your multiple Artboards within this and export to PDF - 2023-10-12 10-52-17.mp4 I hope this clears things up

Although possible, we haven't seen any similar reports from other Affinity/Sonoma users, and I'm not seeing the same behaviour here. Are you able to provide a copy of the Affinity document before you export to PDF, and a screenshot showing your PDF export settings please?

No problem at all - I'm still awaiting a complete investigation from our team, but in the meantime I have a few further questions regarding your system: Can you please open Windows Run (Windows Key + R) then paste the following string and press OK: msinfo32 Please take a screenshot of the window that opens (this should default to the 'System Summary' tab in the top left) and attach this here. Secondly, I can see that AVG is running on your system and is 'hooked into' the Affinity apps, in a similar way to Stardock. Depending on the aggressiveness of the Anti-virus software, it may be that the hidden ~lock~ files being generated by the Affinity apps are causing a false positive to flag with AVG, blocking the app from creating these files and subsequently crashing Affinity due to the unexpected failure. Can you please try temporarily disabling AVG for me, and let me know if this stops the Affinity apps from crashing? Many thanks one again

Thanks for providing that for me! I can see you are opening the Grid options from the Isometric Studio, therefore it is expected behaviour that the Grid settings are opened with the Isometric option enabled. If you don't wish to use the Isometric Grid option, you can enable and adjust the Grid settings through View > Grid and Axis..., which will be retained when opening and closing this dialog. I hope this clears things up

Unfortunately I'm not aware of any singular keyboard shortcut that would allow for this at this time, my apologies. I'll move this thread to the Feedback section of the forums to be considered for a future update

Welcome to the Affinity Forums @JeffKontur & thanks for your file provided! I can see that the majority of your Curve layers are using 'Sharp' nodes, which are expected not to use Bezier handles for the nodes. The 'Tank Top' layer is using Smooth nodes however, and therefore Bezier Handles are shown when selecting these with the Node Tool - 2023-10-11 11-41-26.mp4 You can select and convert your nodes to Smooth/Smart if you require these Bezier handle controls. When using the Pen Tool, please ensure you are in Pen Mode or Smart Mode to draw Curves using Smooth/Smart nodes. If your Pen Tool is set to Polygon mode, you will only see Sharp Nodes in your created curves. If I've misunderstood your report then please do provide a screen recording, as requested above, as this should help us to better understand and assist with this issue. If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks in advance

I agree - I don't expect the PDF export to be larger than the canvas shown in Affinity, and equally when using Document > Unclip Canvas in Photo with such a document causes this white border to expand ad infinitum. Both of these issues have been logged with our team

Hi @Darner, Thanks for your report! Unfortunately I'm not seeing this behaviour currently, or perhaps I am misunderstanding your report. Can you please provide a screen recording showing the exact steps you are taking to trigger this? If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks in advance!