very large exports for printing

[grapher]

Have very large collage with many layers, and some text on top. simple A4, but on export, every single layer and puts into the final PDF resulting extremly large PDF.
i dont want to simply raster all on export, as i want to have some vector areas sharp over 300DPI (text, curves). Is there way to say "flattern all bitmap layers" on export? (dont want to flattern in editor, as i may want to edit it in future) 

I know that it is somehow possible forexample in indesign - result was always very low on data, even with multiple layers. They somehow always used some parts of data that was visible.

Another problem is, that if i use just part of the image, lets say crop large photo and use 10% of it, export will have whole photo, cropped to 10%. Or imagine A4 background photograph, and in foreground large product. In resulting PDF there is full background photo, even parts covered by product.

I know that its possible always to make second file for export and ftattered, but.......

[Fritz_H]

regarding the "crop"-issue:

Affinity is very proud of non-destructive cropping.
To get rid of the cropped parts you need to select "rasterize and trim" or wait until Affinity adds a destructive crop.

kind regards
Fritz

[Patrick Connor]

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.