Jon P

@JenJen77 Is it possible for you to upload the IDML here? I'll see if it's the same issue

Is the file still crashing on open? If so we will need the file The missing font error is likely because of a missing font inside a document in your file, if you go to the Preflight options and untick to look inside embedded documents for the missing font check it should disappear

It has for previous customers, but it's still a nuisance as there's definitely an issue here, but even with your settings I'm still unable to reproduce it, so it's quite hard for us to fix what has happened. There are a good few crash reports there for us to look at which may shed some light. Can you also clarify for me if your default input language is English (UK)? If the above doesn't fix it for any of you let me know as it will need more troubleshooting.

I can't say as unfortunately we've never been able to reproduce it, and from what I've seen before resetting the application normally seems to work. Can you both navigate to %AppData%\Affinity\Publisher and rename the 1.0 folder to 1.0backup. Can you then zip up and send me this folder? The next time to run the app up it will re-create this folder (it contains a lot of user settings). It's a similar step to resetting the program but does a couple of extra things, so curious if that helps. The folder will hopefully contain crash dumps or better yet allow me to reproduce it if I use the same user settings

It's possible to enable logging for PDF export, we have an FAQ on enabling it here. It pointed to the profile on the embedded EPS but changing it would just change the profile it was pointing to. It does sound odd to me, so it's with development to look into a bit further.

Hi @kai2, It's generating an error due to the colour profiles used ["ICC profile for CMYK color space must not be identical to ICC profile of CMYK output intent in PDF/X-4/5"]. I've struggled to work around it for now (the EPS is the cause from what I can see, as thomaso mentions), it doesn't seem to be as simple as switching colour spaces in the document or EPS. It needs looking at further so I've passed it on to development. I'll let you know if we get more information.

Hi @RM f/g, Have you changed the DPI in your document at any point? We have an issue logged where changed document DPI can affect some text styles which can cause behavior like this to happen

Hi @dr_d, welcome to the forums! Does this happen even if you simply create a new blank document? Do you have any issues printing in any other applications? Do you have a crash report you can attach? Thanks

Hi @Deviation, We've had a couple of reports of this previously, resetting the application should resole the issue for you, to do this hold CTRL whilst running up the application.

Hi @Ed Lyons, This seems to work for me, can you upload your file here and I'll take a look Thanks

@Alan Douglas If you want to upload it to the above link I'll take a look

I'm curious if the program straight up crashes for you or just freezes for a long time? I'm not getting a crash but it does take a lot of resources to apply the gradient as it's applying it across a much larger area than it should be.

Apologies @rpnfan we didn't get chance to look at this before the linked has expired, can you re-upload it here and we'll take a look. Thanks

Thanks for providing a file, I've reproduced that and passed it on

Can you both attach some crash reports?

If it happens again let us know!

The crash was in code related to Metal from what I could see so it may help. If you disable that and still get it let me know. I'm still seeing if we can get any information from the crash report specifically.

You weren't wrong in your thinking. I've logged it as a bug, glad that's all it was!

Metal is the best if the device you are on supports it correctly (which it should looking at the specs). There's still a bug here but it will be quite hard to track down, I'll ask the developers to glance over this crash report and see if there's anything we can go off

Do you have any information or steps on how these frames were created and linked together? The linking of the those frames has gone a bit wrong behind the scenes which is the cause. We are looking at if we can fix the file but we would like to know how the file got into this state, so any information to help me reproduce this would be useful!

When entering in the print range have you pressed tab to ensure this change is committed before printing? If you change values then just press "Print" sometimes those values aren't actually saved. If that's not the case can you let me know what printer you are using

@Suvi Can you just confirm for me if you get this only in your current document, or if you start a new one and just start drawing?

Can you upload it here and we will see what we can do. Thanks

Hi @ZorbasDance, Can you navigate to %AppData%\Affinity\Publisher\ and rename the "1.0" folder to "1.0 backup" and let me know if that resolves your issue. If it does can you zip up and send me the 1.0 backup folder. Thanks

Hi @Tim Nikischin, I'm curious if you use a different renderer in Edit > Preferences if you get the same behavior?