NathanC

Hi @Hangman, I've now logged this with the developers. 👍

Hey @Hangman, Can confirm i've reproduced and logged this with the developers.

Willkommen im Forum @Kaddi Ich kann bestätigen, dass ich Ihr Dokument mit der Methode „Seiten aus Datei hinzufügen“ wiederherstellen konnte. Ich habe es unten angehängt. Überprüfen Sie, ob Sie das Dokument jetzt öffnen können. Wenn Sie das Dokument jetzt öffnen können, überprüfen Sie, ob die DPI- und Farbmanagementeinstellungen korrekt sind, da diese während des Wiederherstellungsprozesses möglicherweise geändert wurden. Ich werde sehen, ob ich den Absturz reproduzieren kann, da er anscheinend mit dem Textfluss zusammenhängt. Recovered File.afpub

Hi @Hangman, I've logged this with the developers. 👍

Can confirm I can still reproduce this using the file, it is already logged with the developers so i've updated the issue and bumped it with your report. ALT/OPT + Click with the move tool appears to be the best workaround for this as it cycles the z-order for objects stacked 'on top' of one-another.

Hi @dgroth72 thanks for getting back to me, Unfortunately the file can't be recovered by any standard methods available to us, so it will need logging with the development team for further investigation into what's caused this. It's possible that the developers may be able to partially the corrupt document but this isn't guaranteed and isn't something we can provide a timeframe for. So the team have as much info as possible we would be grateful if you could answer the following to the best of your knowledge: Which Affinity app and version did the file last get saved in? (ie Photo, 2.4.2) Which Operating System and version are you using? (ie Windows 10, macOS 10.15 Catalina) What error message is shown when trying to open the file? Please include a screenshot of this error if necessary. Is the folder you're saving to syncing to Google drive, OneDrive, iCloud, Dropbox or other Cloud services? Do you have any Anti-virus and/or Anti-malware software running on your machine. If so, which one(s)? Was this file a new document or are you trying to save to an existing document when the corruption occurred? Are you able to save a new document to the same location without an error? Can you remember what you were working on or the functions most recently used within the affected document before the corruption occurred? Any other information you think would help us try to find the problem? Going forward we do recommend working locally and then copying to external storage locations after, as doing so often significantly reduces the chances of encountering a corruption and also will ensure you have a local backup.

Feel free to use the link below, let me know once you've uploaded the Doc and i'll take a look. https://www.dropbox.com/request/uZ14nbk0seTGkzDVpem3

Can confirm this passthrough group mask issue is logged, I've bumped existing issue.

Not as far as i'm aware, I've just confirmed it's the same behaviour in V1.

Hi @caze, The Opacity of a symbol layer is a linked/synced attribute similar to the blend mode so all instances will be updated. You can detach that specific opacity attribute by pressing the Sync button in the symbols panel, change the opacity of the symbols layer and then press Sync again. This is a known issue currently logged with the developers, i've bumped the existing issue with your report. 🙂

Hi @Rustle, I can confirm i've replicated and logged this issue with the developers. 🙂

Hi @Artistwright, I've replicated and logged this with the developers. 🙂

Done!

Thanks for the additional Info, If you terminate this process, restart both Publisher and Fontbase and try this again does it have any impact? If not, can you confirm if its the same problem when you manually install fonts via .TTF or .OTF? Also, have you checked if this same problem restart is observed in other apps, for example Word?

See recording below which should hopefully clarify, deselecting the object or adjusting the angle just resets the radius. Just one to be aware of on Mac until it's fixed. Screen Recording 2024-08-02 at 12.46.34.mp4

Thanks @RM f/g, Initially I was unable to replicate this on an M3 Mac as previously, but as soon as i've switched over to a different M1 Mac (Both running Pub v2.5.3, Sonoma 14.5) this has now started happening. In honesty I'm not sure what's causing this or why different environments produce entirely different results so I've logged this with the developers for further investigation. I can also replicate this on a new document using the default headings so it's not anything file specific as far as I can tell.

I'm also observing the same as Walt in Fontbase on Windows 10, I'm freely able to activate and de-activate fonts which dynamically updates in Publisher's font list without a need to restart the app, this was using the MSI/EXE version. Could it possibly be related to the specific fonts you're activating? Can you provide a screen recording showing this? Thanks

Many thanks, this is a known issue with Expand stroke when a superfluous node is present on on the pressure graph, I've bumped the existing issue with your report.

Hi @dgroth72, Could you also possibly provide a copy of the linked resources? I'd like to confirm if this app hang can be replicated via the Preflight fix and subsequent export. I've added a private upload link below if you don't wish to share them publicly. https://www.dropbox.com/request/jitKWvbnynNTMXpmz8aq Also, I can see in resource manager that your resources are all linked to a location on the E:/ Drive, is this an external drive or is it local? Thanks

Quite possibly yeah as logically this does make sense. I'll leave it logged for the devs to ultimately decide but from a general user's perspective since it's possible to assign the stroke a start/end arrowhead it should appear in it's respective position on the shape when adjusting the start/end angle. Additionally, i'm not sure if you've noticed but on Mac when you start adjusting the Start/end angle the Hole radius remains at 100% but the hole just re-appears in the centre as if it's at 50%, this doesn't happen on Windows and I've also mentioned in the same report.

Based on what Ken's mentioned above and also checking Arial over in InDesign I don't think Affinity's completely at fault here. InDesign Arial Regular, exact same Glyph: I'm not certain but perhaps it's anchor position is following so it's central with 2/3/4/etc. digit values. Publisher: However, as Hangman has demonstrated it does work in Pages for individual digits, there is a similar Diacritic bug logged, but I've logged this one separately with the devs as it's possible that it's by Design.

Hi @sAnderO, Good catch, I can confirm I can reproduce this on any Publisher document I create on Windows: regardless of object, number of pages, spread setup, or masters. I'll get this logged with the developers.

Hi @Angel Luis, Just a quick FYI I've managed to replicate an app hang using the SF Pro font under very similar circumstances in the thread below. I've bumped the existing issue with your report.

The SF Symbols app simply won't let me copy the symbol and redirects me to the Apple Developer font downloads page.

Thanks, I've since confirmed that the ARM64 versions of the apps (Be it via the Microsoft store or the Affinity Store, MSIX or MSI/EXE) will trigger an app crash on startup when using a Parallels VM on a Silicon Mac, this is logged internally with the developers. I would suggest removing all existing Affinity apps and then install Photo via the MSI/EXE (x64) installer and then see how it goes. If that works repeat the same for Designer and Publisher. Link to the direct download page is below. https://store.serif.com/en-gb/update/windows/photo/2/