Jump to content

Recommended Posts

Posted

I have some outline lettering in a project. The "S" (font Lato Black) shows up correctly if exported as a PNG, but if exported as PDF it is missing. This is also the case if I convert to curves, and for a whole range of stroke widths. For very thin or thick line widths it shows up, but for the reasonable range I want, it is missing in pdf exports.

image.png.842e289a4e1821e2ac55e4c6212fc0fb.png

image.png.382ec887e3cec5e9ae3c00d48869778a.png

 

This behaviour is exhibited in both Designer and Publisher

Posted
19 minutes ago, Freddie Poser said:

font Lato Black

Is it specific to this font only?

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted
34 minutes ago, Return said:

No problem here on win11

Note that the OP's version has a Fill that matches the background, and a White Stroke that disappears, which is quite different from your example.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted

Hi @Freddie Poser and welcome to the forums,

I've likewise not had any issues using Lato Black mirroring your file. Would you be able to upload your Affinity File so we can see if we see the same issue on export and work out what might be causing the issue for you...

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Hi @Freddie Poser,

I'm slightly stumped as your file exports without issue for me...

Are there any specific PDF export settings you're using that we should be aware of?

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
Affinity Designer 2.6.2 (3213) Beta | Affinity Photo 2.6.2 (3213) Beta | Affinity Publisher 2.6.2 (3213) Beta

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Welcome to the Affinity Forums @Freddie Poser :)

Thanks for providing a copy of your file once the object has been converted to curves - with the above document I'm able to replicate this issue.

Interestingly, it appears very similar to a report we've had recently:

As shown in the above thread, the users curve object was not exporting/printing until the Node Handle had been moved for the Curve, or the object had been Flip Transformed.

I'm seeing the same behaviour in your file, therefore in order to resolve this I'd recommend simply moving the Node Handle for the end node of the object slightly, and it should then export -

In the meantime I will be updating the development log I submitted against the above thread to include your file, as this should help our developers identify the cause of this and stop it from happening in the future.

I hope this helps :)

  • 2 weeks later...
  • Staff
Posted

The issue "[User File] Curve objects do not export to PDF / print until node has been edited or object Flipped" (REF: AF-640) has been fixed by the developers in internal build "2.3.0.2106".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.