Constant Crash

[norbinw]

My last nerves are dying with this app. No matter what I do, I can't export the file as "PDF + bleed + convert color space" without constant crash. I have already exported this same design multiple times in different dimensions, with same recipe, and worked OK. If I unselect convert color space, it exports. Why?

TEST.afdesign

[stokerg]

Hi @norbinw,

At what point do you get the crash?  I've been able to export your file to PDF, with the Convert Colour Space option enabled and didn't get a crash on my Mac. I've attached the exported PDF, I was missing a couple of the fonts, so the text won't look exactly as you've designed.

TEST (10).pdf

[Paul Mudditt]

1 hour ago, norbinw said:

My last nerves are dying with this app. No matter what I do, I can't export the file as "PDF + bleed + convert color space" without constant crash. I have already exported this same design multiple times in different dimensions, with same recipe, and worked OK. If I unselect convert color space, it exports. Why?

TEST.afdesign 145.45 MB · 6 downloads

Seems to export ok on my M1 Mac Mini assuming I have same settings as you. I do not see a preview image though.

Something to try is to close Affinity down then start up with CONTROL pressed to show the special 'clear user data' menu and clear recent documents.

TEST.pdf

Edited July 18, 2023 by Paul Mudditt
Typo corrected

[Return]

Didn't have any problem exporting your file on windows other than missing the fonts like Stokerg.
Maybe it's where you try to export it to.
Currently no good support for external drives/lan/cloud/nas. 
There's a new saving method to tackle this in the latest beta 2.2.0.1903, explained here.

[norbinw]

Not working anymore not even with convert disabled.. You can see my recipe in the video. Also saving to desktop. Crashes even if I select save as. And only this artboard.

[Return]

Perhaps ticking the allow advanced features in the export settings will work.

[norbinw]

If you enable that, some PDF will be incompatible with other apps. When I first jumped to Designer, I had to send my print partner a lot of experimental recipes to figure out what works and what not. Advanded features was what caused the issues (files were pixelated, just when you import a stock vector image that is made in Illustrator, and it converts to raster).

But the Crash is mostly random, as the first time I managed to export the file, then a lot of crashes after that (had to move the text a little bit up), then worked when convert was off, now not working whatever I do. So it's random.

[stokerg]

3 minutes ago, norbinw said:

then a lot of crashes after that (had to move the text a little bit up)

I've been able to replicate the crash after moving the text!   

But on trying to replicate this in the beta of Designer, I wasn't able to get a crash after I'd moved that text.  Would you mind signing up for the beta and installing the Designer 2 beta and try exporting your file and see if you get a crash then? You can sign up for the beta here.  As it is a beta, please create a copy of your .afdesign file first, so you always have a copy of your original .afdesign.

[stokerg]

Hi @Paul Mudditt, I can't get this crash on my M1 MacBook Air but I can on my Intel iMac, after I've moved the text down the page and then export.  So it's possible this is an Intel issue only which would explain why you can't replicate it.  But it does appear the latest beta has resolved this.  Hopefully @norbinwwill be able to confirm they also don't get a crash using the beta.

 

[norbinw]

Not willing to mess up my files with beta, as I have a LOT of work at the moment.. But yes, I still use the last Intel Mac so it may be intel related. Will wait out the 2.2 and see, as (luckily) this only happened with this artboard. Was sweating a bit, as I had to send the file ASAP and couldn't do anything about it to export.

[walt.farrell]

5 minutes ago, norbinw said:

Not willing to mess up my files with beta,

In case you're not aware, the beta installs separately, so you could run a test on a copy of your file to verify the problem is fixed, but continue to use the retail release for your actual work.