NathanC

This issue is logged as a priority so it should hopefully be fixed come the next beta/release, but it's not something that I'd be able to provide a timeframe for I'm afraid.

Hi @k_au, Thanks for the test documents and detailed explanation. The PDF/X1a and PDF/X3 standards prohibit transparency, therefore these images are getting rasterised/flattened on export to opaque images and are upscaled to the DPI set on export similar to if you had rasterised all the image layers and then exported. As a result of this rasterization, they have been converted to CMYK in line with your document profile. PDF/X3 allows for RGB images, whereas PDF/X1a does not, which is why all the images are converted to CMYK in the PDFX1a document. However, in your test document you appear to have found a bug with regards to the Transparent GIF export as this transparency has been maintained despite it being prohibited by these two PDF/X standards, so I'll be getting this issue logged with the developers.

Provided that my footnote body is >2 lines before it splits onto the next I'm seeing that the footnote text flow is updating to the Widow flow option similar to if I did this between two standard text frames on Windows, although it evidently doesn't touch the note reference/text body. The only situation where it doesn't do this is when the line count is 1 as what's shown in OP's screenshot. Disregarding notes If I were to setup two standard text frames, one containing a singular line which flows onto the next If I enable 'Prevent Widowed' nothing happens in this scenario either, I believe this would be a feature request. Before Widowed: After Widowed:

Welcome to the forums @whoanders, Looks like a couple of users have ran into this problem before with it getting stuck at this load stage (Thread below). Here's what I'd suggest doing first to reset your local user settings folder: Close all affinity apps Press Win + R to bring up run and enter the following: %APPDATA% Dependant on how you originally installed the app (.MSIX or .EXE) there will be an .Affinity or Affinity folder in here, rename this folder and append it to have 'OLD' on the end of the folder name, E.G '.Affinity.old' Try launching the app regularly again If it still fails, try the following to clear the account data and re-activate: Close all affinity apps Hold down CTRL and launch Photo 2 while still holding CTRL A 'Clear user data' menu should appear, tick 'Reset account data' and 'De-activate affinity 2 apps' at the bottom The app will now hopefully launch, sign in with your credentials to activate it again and then see if the app can be launched normally. Hopefully you'll then be able to activate to sign in, but if it fails try the above again, but instead run it as admin while holding down CTRL and repeat the steps, and then try opening it normally again. If you're still having trouble, dependant on how you installed the app originally uninstall it and then re-install it using the alternative installer method from the link below (Large Blue download button is for the MSIX, smaller link below it is for .EXE installer) as it looked like this resolved it in the previous thread, but it had to be launched as admin initially. https://store.serif.com/en-gb/update/windows/photo/2/ Let me know how it goes. Old thread:

Hi @NicoftheDogs, Sorry to hear that, I'd initially suggest following the below to reset the app's account data: Close all Affinity apps Hold down CTRL and launch Photo 2 while still holding CTRL A 'Clear user data' menu will appear, tick 'Reset Account Data' and 'De-activate Affinity 2 apps' at the bottom Press 'Clear' and the app will now launch, try activating again. If the above fails, Could you confirm which OS version you're running? Many thanks

Hi @Artworkzzz, Could you possibly send me a copy of your document and provide the full crash report files from your screenshots? I can then confirm if these crashes can be replicated with the Save History function enabled. I've provided a private upload link below. https://www.dropbox.com/request/5qVim3c1r5JqahrnIFiE Many thanks

Willkommen in den Foren @kreativekiste.de Ausgehend von Ihrer Beschreibung nehme ich an, dass Sie sich auf die Kontrollpunkte vom Typ Bezier-Knoten beziehen, die angezeigt werden, wenn Sie den Knoten auswählen, der zur Bestimmung der Länge/Steigung des Liniensegments verwendet wird? Diese Kontrollpunkte können einzeln verschoben werden, aber mir ist keine Funktion bekannt, mit der beide Punkte gleichzeitig verschoben werden können. Diese Funktion wurde bereits angefordert, so dass sie möglicherweise noch hinzugefügt wird. Nachdem Sie einen der Griffe in der gewünschten Entfernung platziert und dann die UMSCHALTTASTE gedrückt haben, können Sie den anderen Griff verschieben und ihn in derselben Entfernung wie den ersten vom Zentrum einrasten lassen, aber die UMSCHALTTASTE schränkt den Griffwinkel ein. Eine kleine vertikale Linie zeigt an, dass die beiden Griffe den gleichen Abstand haben.

Hi @k_au, Initially following the steps strictly in this bug report post, I created a 2x1m 40DPI document, I then placed a 2560x1440 TIFF file at 100% scale on the page (40DPI) and exported the document to PDF using 60DPI. When I used Acrobat's object inspector the image had not undergone any upscaling and honoured the same resolution as my original Publisher file. I tried a few PDF/X methods as well as 1.7 but the result was the same. However after an overview of your linked thread I am seeing the unusual upscaling as described in Lacerto's post when comparing an image that has been masked using a clipping mask to an image that has been masked via an image nested into a rectangle so it does look like this needs logging. However, your steps don't mention about a use of any type of mask and I can't replicate the problem without a mask. I've also tried this with JPEG via drag and drop into my document and then export but the result was the same as above with the correct scaling honoured. Could you possibly provide a sample .afpub document where you have experienced this scaling issue, along with the exported PDF equivalent and a screenshot of your export settings for comparison? I can provide a private upload link if needed Many thanks

Hi @Dawny70, If you're encountering crashes on open/saving files containing SVG resource files this is a priority bug currently logged with the developers which should be fixed in the next version (No ETA on a release currently). I have now bumped it with your report.

Welcome to the forums @cechandl, I'm not seeing this behaviour with endnotes in my sample document as the 'Go To' buttons work as expected, could you confirm if you're on MacOS or Windows, that your app is up to date (v2.3) and provide me with a copy of the document you're having this issue with so we can look into this further? I have provided a private upload link below if you do not wish to share it publicly. Upload: https://www.dropbox.com/request/bRLvVPlJFGLcXlPirXZV Many thanks

Hi @_Th, I've now logged this with the developers. For reference this panel close behaviour was the same in V1.

Hi @Aammppaa, Thanks for the detailed steps, I've replicated and logged this with the developers.

I've just tested this for myself with two exports of your .afphoto, one with no compression and the other with ZIP compression applied and both opened as expected in Photoshop, is it possible that you had 'Save with Affinity layers' ticked? It may be worth checking this is unticked and re-exporting again, and also confirm that the uncompressed tiff can be opened in Affinity before trying it in PS. I did notice using the ZIP compression method did significantly cut down the TIFF file size from 2.4gb to 1.2gb and with it being lossless the image quality is preserved.

Are you referring to export file formats? Each come with their own advantages and drawbacks so the best format can be subjective and also dependant on what you're exporting along with it's intended final use. I'm guessing that you were exporting to PSD as you wanted to open your document in Photoshop while preserving the existing pixel layers and adjustments? TIFF may be a good choice since it's quite versatile and lossless but you'll likely still end up with a huge final file size, and with it being a raster based file format your layers will get flattened.

Welcome to the forums @Msunagi, This issue has been previously logged with the developers so i've now updated the issue to reflect that this is still an issue as of the 2.3 release and bumped it with your reports. I'm also seeing this behaviour on the swatches so i've added this info onto the logged issue.

This issue is still outstanding internally, i've updated the issue to reflect that it's still an issue in 2.3 and bumped it with your report. If there are any further updates on the issue the Serif info bot will reply to the thread automatically.

Hi @Ryansamul, Thanks for the file, PSD files (Even in Photoshop) have a file size limitation of 2GB which cannot be exceeded, your .afphoto file is 5GB+ so when exporting your file out to PSD it's running into this size limit and therefore failing on export. In Photoshop it is possible to workaround this limitation by saving the file out as a PSB, however affinity does not currently support PSB export so this wouldn't be possible at the moment i'm afraid. The minimum doc size I can get your file exported out to PSD is when re-sizing the document down to 11000x11000.

It looks like you have the MSIX version of the apps installed, these are sandboxed and as such they won't appear in a standard installation directory. I'd suggest deleting your existing desktop shortcuts and then following the guidance in the FAQ below re-create your shortcuts via the Shell:appsfolder.

Hi @GavinEadie, These 'Application Library' type folders are controlled/created via System Settings > iCloud > iCloud Drive > 'Apps syncing to iCloud drive' menu. From a clean slate if you were to set an app to sync with the iCloud drive, this won't immediately create a folder in the iCloud drive but if you were to then open the app and save a file the iCloud sidebar offers the option to save the file to the iCloud folder, at which point the folder is available on the drive. These folders are currently shared between the V1, V2 and the beta apps but it's possible that your Affinity app library folder structure has gotten into a state and created duplicate app folders at some point in time even back in V1 (E.G the 'Publisher 3' dupe folder). With the folders being shared this can also create confusion, for example I believe I had originally created my Publisher iCloud app library folder from the beta apps both my V1 and V2 release apps would still associate with this folder, and the folder itself would be called 'Affinity Publisher 2 beta'. I don't think this is expected behaviour and is incredibly confusing so i'll be getting this logged with the developers and will reference your other points on the report. As I also had the 'Publisher 2 beta' folder as my default iCloud folder for both V1 and V2 release, after removing the beta app I had installed I unsynced Publisher 2 beta from the 'Apps syncing to iCloud drive' menu which removed the folder and it's contents, and then signed out and then back into iCloud on my Mac which then fixed the App library name to 'Affinity Publisher' when my iCloud drive re-synced. Personally I don't see any real advantage to using these 'app library' folders over just creating and managing my own folders on iCloud, as they do create a-lot of unnecessary hassle and confusion currently.

Welcome to the forums @keithfishbiscuit, To clarify, are you referring to the App desktop shortcuts or a specific document/file type? Could you possibly send us a screenshot of these Icon's you're referring to that are now blank? If it's the desktop shortcuts to launch the apps, I'm not sure how the installation of another app such as Libreoffice has had any impact on the shortcut icon, but if you originally installed the apps via the .EXE/MSI installer it can be changed under the right click > properties > shortcut > change icon. It should be pointed towards the default installation folder for the app icon, shown below for Photo. If you installed via the MSIX package you could re-create the desktop shortcut via the shell:appsfolder and this should restore the original shortcut (see guide below)

Thanks for the recording, there’s an issue logged internally in relation to the app canvas area flickering with HDR enabled on certain displays, and mouse movements/clicks can also trigger it so it’s possible that you’re encountering this issue as it’s not picked up by software screen recorders as you originally described. With all the apps closed, Try disabling HDR in Windows Settings > Display and then reboot and then see if it persists. There’s also a separate screen flicker issue logged with certain displays when G-SYNC is enabled in the Nvidia Control panel, but I don’t think you’d be encountering this one unless you have a G-SYNC compatible display and a dedicated Nvidia Graphics card.

Both the Zhuyin input issue and CMD + S Save issue are both logged internally still, so as mentioned in my previous reply the Serif Info Bot will reply automatically here if there are any further updates.

Thanks, with it being as intermittent as you've described throughout your app session it's possible that one certain action is causing this, i'll keep trying a few different things but ultimately if you can capture it happening on a recording that would be great. ----- Thanks for providing further information in regards to your second point, with the current functionality of the 'none' controller removing any variance properties on any curves previously drawn being the expected behaviour currently i'd suggest posting this functionality request for profile flattening over on the feedback section of the forum. 🙂 https://forum.affinity.serif.com/index.php?/forum/122-feedback-for-the-affinity-v2-suite-of-products/

The issues are still outstanding internally, this thread is tagged with the issue references so if there are any updates to them internally the Serif info bot will automatically reply to the thread advising. Unfortunately your pointer animation issue is still not re-producible internally when following your same configuration and recording so this has not been logged as of yet.

I can see from the thread below that the print driver refresh has fixed your issue, so my reply can be disregarded 🙂