Lee D

@NotMyFault I've logged this with the developers. When you say "Affects all platforms" can you confirm, as I can only reproduce this on iPadOS using your file.

@noxdiurna Could I get a copy of your .afphoto file as I'm not getting the same kind of results you are on the images and adjustments I'm using. If I can confirm an issue I can get it logged with the developers.

@JohnnyV Welcome to the forums. If you switch the Develop persona's raw engine from using Apple CORE image to SerifLABS, does the image look any different when reopened? Can you provide a sample file?

@JulieR Once the app is open, can you see documents on the Live Docs screen? If you can I recommend tapping the icon for each document and saving them first. Once saved, swipe up to return to OS, then swipe up again and make sure the app is fully closed. Now tap the app icon, when you see the splash screen, double tap to open the Clear User Data options and tap Reset and when prompted tap OK. Does the app now open quicker? If not do you have a lot of fonts installed within the app at all? If you start a new document and try Placing an image, are you selecting from Files or Photos? Can you now see them to select? If not can you please do a screen recording showing this workflow.

@Archangel Thanks for the update, I'll do some more testing on Windows to see if I can get a crash to occur.

I asked the developers to confirm if this workflow/process is a bug but they confirmed it's working as expected. As the commands on the menu are independent of the Move tool, so it won't be using the current selection box, just the base box of each selected item. But it may be something that they look at improving in the future.

I've logged this to be confirmed if by design or a bug.

@Hanjo Does this occur for you regardless of the file you have open or have started? Have you tried resetting the app to default settings, just in case? To reset: Hold down the CTRL key and open the app, when the options appear, release the key and click Clear.

@TaurusGirl Welcome to the forums. Your file is giving the same message when I try opening it on my system. I've logged it with our developers for them to investigate further. However I can't give you an eta on when this may be and if the file can be recovered. If you can it's best to save/load files locally as using networked or cloud based storage can potentially cause issues as the connection to the file can be lost/dropped.

@WolfyAU82 Welcome to the forums. You can purchase our Affinity V2 apps from the Windows store, as well as direct from our Affinity store. From checking our system I can see a purchase for our V2 apps from our store. So you can login to your account and download the latest version (2.4.2) to install if you are having issues with the update process.

@Pure! Can you expand more on the issue you're having. Is this only happening when you have used data merged with a particular file or any? Can you create/save new files without issue that don't have a data merge? Where are you saving the file to, local, external or cloud storage? Can you follow the steps in this FAQ article to check for the most recent crash report that should be for this crash.

@Archangel I'm not getting any crashes on macOS or Windows using those images within the HDR Merge feature (default settings). But as @NotMyFault has suggested, they aren't the type of images usually used for HDR merging which includes having different colour profiles. Open Photos Settings > Performance if Hardware Acceleration is enabled, try turning off and restarting the app and repeating the process.

@PanGad I'm only getting a crash in Publisher V1 on macOS Sonoma if I double click into the Author field. I believe this relates to Sonoma as I also tested on Monterey and was able to click into the field and enter/edit info.

Hi @OMD Welcome to the forums. If you press TAB before opening the Save window does this make any difference? Which version of macOS are you using?

@ptr-nl Welcome to the forums. If you can provide a copy of your custom profile (Canon EF 28mm f1.8 USM), I can ask one of our developers to take a look to confirm if the data is being read correctly.

@Intuos5 If you increase the overall document size to something like 300x300 and then export to out, does this give you a better result? The blend mode on the "path6" layer will also cause it to be rasterised on export due to it not being supported, see here for little more information. Do you still have the source file used?

@TopDaryl If you open the apps Settings > Performance is Hardware Accelerations enabled? If so, please disable it and restart the app to see if that improves the situation. If not opens the settings again and try changing the Renderer to one of the other options. It may also be worth checking to make sure your graphics card drivers are fully up to date. You do have the option of also uninstalling the app and downloading a fresh version to install if the above fail.

@Niko Steensels Thanks for the files, I'll take a look to see if they narrow down a possible cause. It's also worth checking to see if Hardware Acceleration is enabled within the apps Settings > Performance. If it is, disable it and restart the app and see how it behaves.

@pfi Are the crashes only occurring with images processed through Focus Merge? If you just open an image and switch the colour profile does a crash occur? After the Focus Merge completes can you use File > Save and if you then reopen and try changing the profiles does the app still crash? If you can save to a .afphoto file, can you provide a download link to one of them? What's the format of the source images and how many are part of the focus merge?

@Vladu11 I've been able to recover and save to a new file, please download and see if it opens for you. Light NEW V1.afphoto

@cherielegs11 Welcome to the forums. It will depend on what you're wanting to "clean up" within your image. What workflows did you use in the other platform, as some may be similar. You can find our available online videos on our YouTube channel here.

@certifries Welcome to the forums. If you can provide a copy of your document and confirm your workflow I'll take a look.

@Hangman Some fixes should be added to the next beta to resolve this.

@Darner I've setup a test document (150x225cm/300DPI) with some shapes, brush strokes, placed TIFF file. It's exporting out to PDF without any crashes occurring. Can you provide any other info on your document itself or a copy of it and your export settings?

@design punch Can you do a full screen recording showing the issue occur? My basic workflow: Created a design in Designer and saved. Opened Publisher, confirmed "Automatically update linked resources when external changes are made" is enabled within apps Settings. Started a new doc (Placement: Linked) File > Place, inserted Designer file from 1. Save Pub file Reopened Designer and edit file, saved closed Reopened Publisher file, changes to placed Designer file are shown. You do reference a book file, which I didn't include in my basic workflow, so this could be related. But just in case I created a new book, added the Pub file as a chapter and saved. Edited the Designer file again and saved, then reopened everything in Publisher and the linked file is updated. A screen recording will help to confirm your workflow.