rkdp

AMD has had almost 2 years to correct this and has chosen not to. With their new gpus coming out, I don't think AMD is going to make last generation's gpus a high priority. And I'm saying this and yet hoping their new ones have a good showing and work properly with OpenCL!

AMD released a new driver yesterday (Oct 4, 2022) and in the notes it may seem to show a fix (though not explicit) , which Affinity would then have to test and then re-enable hardware acceleration. I switched to nVidia more than a year ago, but I am hoping that since the 4000 series is completely new that the driver issue will not exist. I've been very disappointed with AMD's seeming lack of response on this issue as it has been coming up on 2 years now!

Yes, that is a nice workaround. And I appreciate you having shared it... very helpful until they correct this... soon I hope

Note: Don't know why the red background appears different here, but in the orig and pdf, the red background appears the same before uploading them.

Attached are screenshots of the orig file, the export settings, and the exported pdf. The other workaround is to make a copy of the image (Burger text in this case) directly behind the orig image, filled black. Bring it down and to the right as a shadow; in fx, apply Gaussian Blur and click on color overlay in fx. And this will export to pdf properly.

Here's the link to the previous thread I had found. I'll upload my pix in a bit with a different workaround as well. Thanks for your time Callum.

When exporting to PDF (for print), Affinity Publisher 1.10.5.1342 converts drop shadows that overlay a solid color to an odd light-hazy drop shadow. I've seen a "workaround" listed for this issue more than a year ago, so it has been a major issue for longer than a year now. Is Affinity working on this???

Doing the same thing... exporting APub to PDF and getting light odd drop shadows. (6/25/2022 - Affinity 1.10... Windows 10.) This has been a major issue for well over a year now - Is Affinity working on a solution???

In APhoto, opening an APhoto file; no warning given for the font that is not turned on or missing. Same in APub. I thought it used to give a warning the same as PS and InD do.

Has anyone found a solution to this as I am looking at it now as well. I think there should not have to be a separate command for replacing an image... we should just be able to use the place command and it replaces an image.

Is there any way to have APhoto (or Pub) warn of missing fonts when a file is opened? Or what is the best way to do that (as opposed to selecting each font in the file)?

Hi Walt, I opened a new file to recreate it for you. Did the exact same thing, and it is working like it should. Don't know if the other one was corrupt or what. Thx for the reply though!

Unable to edit frame text. Try to reselect it with text tool (frame text tool), but it will not select.

@thomaso Thanks for the extra info, very helpful. I greatly appreciate your time and effort my friend! Our community is amazing!

That is perfect! It is exactly what I was looking for! Thank you very much for mentioning the "lock children" as I would never have known about it - And it made all the difference to make it work like I wanted - It even allows me to adjust the frame! You are magnificent!