NathanC

Welcome to the forums @MoCoMade, If the app freezes on opening existing documents or creating new files this is normally an indication of a GPU/Driver based issue on your device which is causing Affinity to freeze when rendering the canvas. I've provided some potential solutions to run through below in order: Disable Hardware Acceleration Within the apps under Edit > Preferences > Performance try disabling Hardware Acceleration (The last tickbox) and then close the interface and restart the app when prompted to and try again. Update your GPU Drivers Make sure that you have the latest available drivers installed for your GPU, i've linked the AMD and Nvidia and Intel driver search tools below, dependant on your GPU. If possible, perform a clean installation of your drivers if given the option. https://www.nvidia.com/download/find.aspx https://www.amd.com/en/support https://www.intel.co.uk/content/www/uk/en/download-center/home.html Reset drivers via DDU If it still freezes/crashes, try doing a complete uninstall of your graphics card drivers using a dedicated tool for this purpose (Such as DDU linked below) and then restart and install your graphics card drivers (using the links above to search) to completely refresh them. https://www.guru3d.com/files-details/display-driver-uninstaller-download.html ------------------------------ @ShaneB could you describe at what point the app crashes, does it get as far as the app splash/start screen, or are you able to get into the app first and try and open a document? If so I'd suggest following the above, if you're not getting as far as creating a new document can you confirm if the app is outright crashing or is it just freezing? If it's crashing if you could send us some crash reports that would be great. Crash reports FAQ:

Hi @Alexis Trappist, I would've suggested using the Filters > Colours > Erase white paper filter to remove the white background, but this also removes the white background on the product label, so another easy way is to use the flood select tool, if you set it to 'Contiguous' and then a very low tolerance value (~4%), you can then click to select the white background and then delete it. Amandes Transparent.tiff

Hey @AlanPickup, This has come up before but isn't a bug, the hyperlink dialog won't detect and dynamically change the 'Type' dependant on the text content highlighted, but rather it will just default the type to what the previous hyperlink was inserted as, for example if I inserted a 'Page' hyperlink when I next go to insert another hyperlink the dialog will default to 'Page' as that's what I last inserted. This does exist as a feature request however which I've linked below for reference. The email field type won't automatically insert the text content highlighted into the email box, but there is a dropdown in the field in which previously inserted emails will be listed for selection.

Vielen Dank für die Zusendung der Datei und die Klarstellung. Ich hatte bisher keine Probleme mit der App oder Abstürze beim Speichern als PDF über den Druckdialog. Ich habe die verlinkte Ressource, die Sie verwenden, nicht in der Datei. Um sicherzugehen, dass es nicht damit zusammenhängt, würde ich zunächst vorschlagen, sie einfach zu löschen und dann zu prüfen, ob das irgendeine Wirkung hat; es ist zwar unwahrscheinlich, dass es die Ursache ist, aber es lohnt sich, es auszuschließen. Wenn es nur der Druckdialog ist, der einfriert, und die normalen Exporte funktionieren, würde ich vorschlagen, die Druckertreiber wie folgt zurückzusetzen: Öffnen Sie die Systemeinstellungen von MacOS > Drucker und entfernen Sie die hier aufgeführten Drucker. Starten Sie dann Ihren Mac neu und laden Sie eine neue Version der Druckertreiber direkt von der Website des Herstellers herunter. Installieren Sie den Drucker mit diesen neuen Treibern neu und starten Sie Ihren Mac erneut. Starten Sie abschließend Publisher und versuchen Sie dann erneut, in PDF zu drucken. Wenn es immer noch nicht klappt, könnten Sie überprüfen, ob das Problem mit Ihrem Dokument zusammenhängt, indem Sie das Drucken in PDF mit einem neuen Dokument versuchen.

Hi @Hangman, I've now replicated and logged this with the Developers. 👍

Welcome to the forums @acdi_1, Does the activation window look like the below screenshot by any chance? If so, it's caused by having Windows in High contrast mode, you can turn this off in Windows Settings > High contrast. You should still be able to type into the field boxes even with it turned on, however. If it's not, could you perhaps share a screenshot of the activation Window and advise which version of Windows you're running?

Hallo @rb67, Besteht die Möglichkeit, dass wir einen Blick auf die problematische .afpub-Datei werfen können? Ich habe unten einen privaten Upload-Link angegeben, falls Sie die Datei nicht öffentlich zugänglich machen möchten. Wenn Sie auch einen Screenshot Ihrer PDF-Exporteinstellungen zur Verfügung stellen könnten, wäre das großartig. Link zum Hochladen: https://www.dropbox.com/request/cCyFBiVIk6Q9zxCkeEpK Vielen Dank!

Welcome to the forums @haichao, It's possible the app is having trouble with a resource in the document, I've provided a private upload link for the file below so we can take a look, if you're using any external linked resources within please also provide them. Upload link: https://www.dropbox.com/request/4B8x3z1aEXWeDRWwwA4Y Let me know when the document has been uploaded.

Hi @GT70, When converting a document from a regular canvas which had column or regular guides to an artboard, there's a known bug where even after deleting the guides on the artboard that 'ghost' guides still remain that are visible when marquee selecting. These guides aren't visible in the guides manager as they are drawn on the canvas which is no longer in focus and the only way to get rid of them is to revert the document back to a canvas by deleting the artboards, which isn't exactly feasible on multi-artboard documents. What's shown in your recording appears to be the same or a similar trigger for this bug, so I'll bump the existing issue with your report. Unfortunately I'm not aware of another workaround to remove these 'Ghost' canvas guides in an existing document, as deleting the artboard they originate from will just re-position them again. If you create a new empty artboard document, you could try copying and pasting your existing artboard layers over to the new document and hopefully the 'ghost' canvas guides won't follow as they do not exist on the hidden canvas.

Hey all, Many thanks for providing the additional info, I've now replicated and logged this with the developers.

Welkom op de forums @AvdB-Netherlands, Als de tekststroom van de 16pt introtekst niet goed loopt op de bestaande 13pt basislijn in je document, heb je dan geprobeerd een onafhankelijk basislijnraster in te stellen voor het introtekstkader? Dit kan via het paneel Venster > Tekst > Tekstkader. Zorg ervoor dat je 'Basislijnraster negeren' uitschakelt als dit is ingeschakeld op het tekstframe, anders is het niet mogelijk om er een in te stellen. Als je een onafhankelijk basislijnraster instelt voor het tekstframe, kun je de horizontale afstand van de basislijn onafhankelijk aanpassen om de tekststroom van dat specifieke frame aan te passen. Het kan helpen om een andere kleur te gebruiken voor de basislijn van het tekstframe, zodat het makkelijker te onderscheiden is van het basislijnraster van het document. Info: https://affinity.help/publisher2/English.lproj/pages/Panels/textFramePanel.html Als dit niet is wat u zoekt, kunt u dan wat meer details geven over wat u specifiek wilt bereiken met het introtekstframe en een klein voorbeeldbestand leveren waar we naar kunnen kijken? Hartelijk dank

Hi @Intuos5, Thanks for providing detail along with the recordings, I've now logged this with the developers. For comparison, on Mac invoking the Find & Replace panel via CMD + F with the UI toggled off re-reveals all studio panels and toolbars, essentially undoing the UI toggle. I'm not sure if the current Mac behaviour is the expected or what you have described is, but i'll leave that for the devs to determine.

Welcome to the forums @Ablof, Unfortunately as you've found the file is not recoverable using any standard methods available (e.g 'Add pages from file') so with the information you've provided I've now logged your file with the developers for further investigation. This is primarily for the purposes of investigating the crash and there isn't a guarantee that your document can be recovered and i wouldn't be able to provide you with a timeframe i'm afraid. As such, I would suggest reverting to the backup file if one is available. This wouldn't be possible since the corrupted document cannot be opened using any standard methods, however the apps incrementally saves a portion of your file at set intervals dependant on the 'File Recovery Interval' setting in the Performance Preferences. These are not full document backups and are used in circumstances where the app has unexpectedly closed to restore changes. If any are in the autosave directory you could try renaming them from .autosave to .afpub files and then seeing if they open in Publisher and then extract some of the text/changes, but it's not guaranteed to work. If any are available they can be found in the 'autosave' directory: ~/library/Application Support/Affinity Publisher 2/autosave/

Just as a follow up on this, I found that if I opened the .afpub file created on iPad which contained the linked resources on my Mac I would then be prompted to update the location of the resources as they are missing, but this was as expected as the file path of the resources changes in between MacOS and IOS despite it being the same SMB share, for IOS this was /private/var/mobile/library/livefiles etc. and for MacOS it was /Volumes/SMB Share/ etc, this was outside of the app's control. The iPad Files app on the SMB share appears to have issues updating any existing files I've made edits to, even outside of Affinity. For example If I edit a basic .rtf text file on desktop and then save it back to the same location on the SMB share, other MacOS devices connected to that share can almost immediately access the updated version of the document, however the iPad version on Files remains unmodified, and I can only get the .rtf file to update by ejecting and re-connecting the share, this is the same for resources i've edited in the Affinity apps. Doing this ejection and re-connection causes issues for linked resources in Publisher as the re-connected Share then has a different file smbclient path, which then causes the resources to become unlinked. I can see i'm not the only one to run into this limitation: https://talk.macpowerusers.com/t/anyone-know-how-to-force-the-files-app-to-refresh-its-view/21564 In comparison, using a cloud service like OneDrive did not present this problem editing and saving a resource on Mac updated/synced it on iPad in a relatively short duration, and I just had to simply update the resource in Publisher.

Thanks, I've checked across both V1 and V2 on a few different devices, but the result is the same with the rectangle subtract from the pie working as expected with no subsequent app crash/hang (see attached file). Is your app updated to the latest available version for V1 (V1.10.6)? Also, If you turn off Hardware Acceleration under Edit > Preferences > Performance and then restart the app and try again is the result the same? Subtracted.afdesign

Welcome to the forums @Peter new user, If the app fails to create a new document/open any existing files, this can be an indication of a GPU/Driver based issue on your device which is causing Affinity to crash when rendering the canvas. I've provided some potential solutions to run through below in order: Disable Hardware Acceleration Within the apps under Edit > Preferences > Performance try disabling Hardware Acceleration (The last tickbox) and then close the interface and restart the app when prompted to and try again. Update your GPU Drivers Make sure that you have the latest available drivers installed for your GPU, i've linked the AMD driver search tool below. If possible, perform a clean installation of your drivers if given the option. https://www.amd.com/en/support Reset drivers via DDU If it still freezes/crashes, try doing a complete uninstall of your graphics card drivers using a dedicated tool for this purpose (Such as DDU linked below) and then restart and install your graphics card drivers (using the link above to search) to refresh them. https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Thanks for dropping those over, I've taken a look at your .afdesign file and it looks like it's caused by the 'Tile' artboard has an imprecise pixel location (X=70.5px), when exporting the artboard this is then rounded up and an additional edge of semi opaque pixels is visible. To avoid this happening, select the 'Tile' artboard and change the X axis value to a pixel aligned value (70px) and then export again, you should then find that the export is pixel perfect with the white edge removed from the repeating bitmap pattern. Having 'Force Pixel Alignment' turned on and 'Move by whole pixels' off next to the snapping menu along the toolbar helps ensure that positioned objects are pixel aligned, but will not retrospectively fix the postion of objects that have been previously transformed. Info: https://affinity.help/designer2ipad/English.lproj/pages/DesignAids/pixelAlign.html

Welcome to the forums @ShaneB, This sounds like a slightly different problem, is the message you're getting when attempting to activate Publisher 'Please try again'? If so It's possible that you have installed the apps using the different installers available (.MSIX and .EXE), which causes app conflicts when both are opened at the same time. It can be a little difficult to tell which app version you installed, so I would recommend uninstalling both and then proceeding with the installation of the .EXE version only to see if that resolves the problem, you can find a download link to the .EXE version below. Be sure to download via 'Also available: EXE' and not the download link above it. https://store.serif.com/en-gb/update/windows/designer/2/ https://store.serif.com/en-gb/update/windows/publisher/2/ If the 'Please try again' error persists, send us an email over at affinitysupport@serif.com with your Affinity ID email and we'll be able to provide further assistance.

Welcome to the forums @bnd.lettering, As the issue outlined in this thread was in relation to a file specific problem and on MacOS i'd recommend creating your own separate forum post over on the Windows Bug section giving as much detail as possible on your issue(s) and provide any relevant screenshots and sample files, we'll then be able to investigate further. 🙂 https://forum.affinity.serif.com/index.php?/forum/128-v2-bugs-found-on-windows/

Hi @Jpburns, Thanks for raising, I'm still testing this one, as my iPad connection to the SMB shared folder i've got setup on another Mac is terrible so I can't reliably tell what's going on as it's taking a long time to update the resource when I make any changes to it from any connected devices. I'll confirm if i'm able to replicate. I'm definitely seeing this, selecting the relevant folder and file does nothing and the resource status just stays as 'missing', this was the same with having the resource kept locally or on an SMB share, I've now logged this. While testing this I did observe that in the file explorer dialog there was no 'Open' option at the top right hand corner, whereas if you long press on the resource and then select 'Re-link' and then 'Open' on the relevant folder the re-link is then successful. It doesn't appear to be respecting the placement policy of that specific resource when you opt to replace it and just defaults it to embedded if the resource is missing. However on desktop it will respect the placement policy for the replaced resource so if it was linked previously the replaced resource will also be linked, I've also now logged this. I had checked that my document policy was also set to 'prefer linked' but it doesn't appear to factor that in either.

Hey @MikeTO, I've now logged this with the developers. I've also separately logged the Windows tooltip inconsistency for correction.

Welcome to the forums @StacyE, I'd initially suggest following the below to perform a basic app reset and also disable Hardware Acceleration at the same time to see if this improves the app responsiveness on your system: Hold down CTRL and launch Designer 2 while still holding CTRL A 'Clear user data' menu should prompt with three boxes ticked, in addition tick 'Disable Hardware Acceleration' Press 'Clear' and the app will now launch. If the problem persists, could you confirm if the application freezes occur as a result of performing a specific action or using a tool within the app or if it is completely random? Also, to rule out it being a problem with an existing document, see if the same issue then persists on a new empty document.

Welcome to the forums @DGB2079, Could you possibly provide a sample .afpub file where you're encountering this index problem along with a screenshot(s) so we can investigate further? I have provided a private upload link below if you don't want to share it publicly. https://www.dropbox.com/request/baCNMJraOLfzgdx2xZqt Many thanks

Welcome to the forums @sherymon, The Affinity apps don't currently support Indic Language text/typing features unfortunately, this has been discussed and requested in previous forum threads. Feel free to voice your support for this to be added in the feedback thread linked below.

Hi @danimiracarlos, Could we also take a look at the document where you encountered the crash/app hang when using subtract to see if it can be replicated? I can provide a private upload link if needed. Many thanks