Jon P

I understand your expectations, but I could also argue that it's applied to the image and removing it and placing it on the frame could also be unexpected, although your use case is maybe more common.

They should probably behave like the dropdowns do and appear above the toolbar if there is no space below, I'll pass this on.

@Affinity_Newbie, I'd advise creating a new thread and attaching the idml file if possible. If you click "Yes" when you open the file and it asks to locate missing resources it will recursively try find any other images in the folder you select. It won't do this through the resource manager however, only on file open.

@Joe L, Can you create a new thread and upload the problematic file? Thanks

@Allen Romano Can you upload the file here and we can take a look Thanks

I'm afraid it's the way that resolves the crashing on load issue for now. Apologies for the inconvenience. I agree we need to find the cause, there was a previous issue where editing image sizes externally could cause this. I'll be passing the crash report on and seeing if we can get more information. If you choose to re-link, it should function recursively and gives you the name of the resource it is looking for (if you click Yes to locate resources when the file is opened) in the windows dialog. So it should pick up the subfolders automatically if you just renamed the Buch folder.

It does seem related to the pictures then. I'm afraid you will need to re-link from those low res pictures to carry on as before on that machine (if when you open the file you click "Yes" it will find other resources in the same folder, so it hopefully won't be that much time). Do you often edit pictures externally after they have been inserted?

Hi @Andreas S, It doesn't crash for me either, I suspect the machine it is not crashing on is missing some of the linked images (like I am) and that may be the cause (although I can't say why this has happened, but we have seen it before). On the machine that is crashing do you mind renaming the folder called "Buch", from what I can see that should break the links to all the images in your file. Does it then load without crashing? If so if we re-link all the images it should then behave as expected.

Hi @Andreas, Can you upload the file here, and then go to %AppData%\Affinity\Publisher\ and upload the 1.0 folder, it will contain program settings/crash reports which might shed some light on why this is happening on just one machine. After doing can you let me know if holding down CTRL whilst running up the application (to reset it) fixes it? Thanks

Thanks, I only see that one image that is 0kb and won't display, it looks like that became a bit corrupt. The other attached document has all the images displaying correctly for me, do you just see the red ?'s as in the Original Post?

We had a report a while ago that was in this area, but I can't reproduce copying/pasting that character and it causing a crash, if you encounter it again let us know and upload the file

Can you try in the 1.8.4 beta found here and let me know if you still get the issue Thanks

Hi @obeydesign, Can you attach a document that demonstrates this, I'm struggling to reproduce it from scratch Thanks

Can you upload the file here, I'll take a look Thanks

@Paolo192 If you want to upload the document here I'll attempt to export it from my end. It would help if you could embed the resources or ensure you also upload all the linked resources

Thanks, the file seems a bit different to shown in the video, I can't seem to reproduce it at the moment. Can you download the 1.8.4 beta here and let me know if that fixes your issue?

I've split this into a new thread, as if the OP of the thread you posted in comes back it gets a bit confusing. It crashed on open for me once and does indeed seem to be crashing on save, I've passed it on to development.

I've passed it on again. Crash report won't be much use if i'm honest. What will be useful if we can figure out what steps are taken that get the file into this state. Then we can fix the issue at the source and not have to repair a file. Can you give me some information about steps you were taking before this happened? Anything that you also did the last time this happen? I can then look around and hopefully find the recipe that seems to cause this happen.

I got a freeze when trying to delete a Master on 1.8.2, but it seemed alright for me on 1.8.3. There are no corruption regressions in 1.8.3 as far as I'm aware. If you want to avoid 1.8.3 you can download the 1.8.4 beta version from the forums and see if that's better for you. If you are worried about corruptions then keep regular back ups of your files, which is a good working practice anyway.

Can you attach the document with these faulty layers?

@Dleacy, Can you confirm what version of the app you are using? Some of your crash reports (one from May 11th) are on 1.8.2, the latest version is 1.8.3

I'm struggling to nail down the reason, but I can definitely reproduce it and have passed it on to development.

Hi @thetasig, If you want to use this link I'll get it passed on. When we fix these files they are done on the files themselves, so it is always important if we can get a recipe as to *how* files get into this state. I'm not sure if we did this the first time we saw your file. Can you link me to other thread where we fixed the file? Struggling to find it via the post history

Agreed, I've passed this on (although I also personally always leave it docked, but I could see how it can be annoying)

Hi @Gaunilo, Can you upload the problematic file? You can use this link if you'd like to keep it private