REVENTOR

Grafical Glitch in the Software remains. On several zoom levels there is a visual seperation, even if its a pixel perfect connection. Not an real issue, but irritating. Photo_IDRrLgwD7Z.mp4

if those 2 options are active the problem can be mitigated. the issue is that objects that you scale without this option enabled can get incremental pixel values like 100.25px then things just dont snap perfectly anymore.

Whenever you try to snap 2 objects perfectly togehter there remains a small distance which can be seen on screen and exports. Why? I Would expect elements to truly touch and have no gap in between. Photo_cYi5ureJgs.mp4

Affinity Photo 2.5.6 is exporting with slightly off values compared to what the elements actually have: Here we see that the selection is a black rectangle with the dimensions of 500x200px. So when i export this selection i would expect to get the exact same values, but i get 501px instead. Why?

I found another issue, this time just with the vector elements: They get rendered wrong. (Affinity 2.5.3) This means the export also looks wrong, effectively meaning that PDFs can not be editited with Affinity in this version. File: Affinity Vector Issue.pdf As you can see there is a difference in how the background looks. Just open it in Affinity and in any PDF viewer.

I feel missunderstood here. Let me clarify: A) I intend to edit a PDF file (even a conversion to PNG is a form of editing, as its more than viewing). B) If Affinity offers a button labeled "replace missing fonts" having it deactivated would logically mean there is no replacement happening. C) If no replacement should happen, i would expect the subset embedded Font of the PDF to remain in its "original" non editable, vectorized state. That's all. My reasoning? Because you can edit more than just text in a PDF and if the text doesn't need to be changed, why would the app do any kind of operation on it and not just leave it as is?

Ok thanks for your explaination. I can adopt the workflow of Placing files for now. But what if i want to edit another part of this file. Anything, just not the text. Let's say the Lines in the Background need to have a different color. Technically, Affinity requires me to have every used Font bought / licened / installed just be able to edit anything and keep the text elements untouched? I can't agree that replacing every non-existing font with a fall-back font should be the normal expected behavior, because other programs are not doing that either, for example PhotoShop. The font should simply be rendered as any browser would do it, without the need of having the actual font installed. When i open the PDF in Photoshop i see the correct design: and the export looks like this: Now lets try to do a minimal edit on this PDF in Photoshop compared to Affinity. We add a black box and a text to it and export it as PNG: We can see that the photoshop result looks just like the original PDF, but with the new elements included. When opening the file in Affinity, i already see a wrong preview because the missing Font gets replaced, even though "replace missing fonts" is disabled: then i create a box and textlement and export the file: now this result looks nothing like the original anmore. Even a PDF editor can do simple edit without destroying the original design, while not having the fonts installed: We can look at more editing examples in differnt tools, but my point is.......Affinity should be able to open and edit the file keeping the font the same, without the need of having the font installed. There is no reason for having the font installed on the system, if you are not editing the actual text, but other elements in the file. As a last example, lets sai we want to edit those corner elements and give them a new color. In this case, Placing the PDF wont help, because we can't edit those corners in a placed element, therefor opening is necessary. And when we open, we are back to the replacement font issue: Hence im pretty certain the occuring forced font replacement is not expected nor wanted standard behavior and must be considered a bug.

Thanks, thats a work around, but Affinity should only replace the missing font when the tickbox for this behavior is ticked, or not? I remember in older versions it would open the file without doing any operations on it, and the preview would be correct, just like in any other PDF program. I mean why would Affinity always replace the font, if no editing is needed? That would make the option of having this tickbox obsolete during the opening process. In this particular case it would also increase the workload a lot. There are many pages in the original PDF. If i open the document and export it as PNG with a certain resolution, its a matter of a few seconds, but if i need to place every page indivually on a prepared export sheet, its going to take hours. So from my point of view opening and replacing a font even tough this tickbox is off, is not expected behavior. I expect the PDF to look the same, as long as i dont request a replacement of fonts. Also, when the PDF is opened, the user has no idea that this replacement is happening, since the text replacement options are presented as "grayed out" and inactive.

I attached the 2 test files. They were saved via FOXIT PDF EDITOR and Brave Browser. The Filesize is slighly different but the behavior of Affinity is the same with both files. Hence the origin of the file doesn't seem to be of importance, the PDF should be saved in a "standard" way. The Lust Font is not installed. If it is installed it will be displayed correctly. But the point is, there should not be any changes to the existing design in this file, i just need to save it as a PNG image. Since Affinity is always replacing the fonts in PDFs in this version, this simple task can not be done at the moment with Affinity. Affinity Bug Test File Foxit Export.pdfAffinity Bug Test File Brave Export.pdf

I think the error is that the "replacement" is forced in the 2.5.2. version even if the tick "replace missing fonts" is not set: The original, then openend in the PDF viewer looks clearly different. So fonts get replaced all the time.

It seems that the issue is connected to the Hardware Acceleration. Once disabled, the program works fine on both grafics cards without crashing.

Whenever i edit something Affinity (Photo / Publisher / Designer) is crashing. I don't need to do anything complicated, just roate an image for example. I recorded the behavior in the attached video. What can be the cause for this? Any ideas how to solve it? System: Windows 11 Pro Build 22621.105, Intel(R) Core(TM) i7-8550U CPU with UHD 620 integrated grafics and additional Nvidia Geforce MX150, all drivers installed to their latest versions as of today. Affinity Bug.mp4

That makes sense! Because no matter what settings you use for export, the file will keep a certain minimum file size - this indeed has to be because of the ICC profile attached to it. Thanks! Learnt something new!

Yes i know it's not in related to the Publisher Software, but i think it needs to be adressed ASAP. I have been shown those 3 Images with the red arrows, which i NEVER uploaded to the forum! Meaning that uploads from other people are getting mixed up by the forum and can be deleted by other users. please look into this. it happes when i try to edit my existing post: when i look at all of my existing attachments, it's correct:

True! Thanks for the info! Still it's not really clear to me why RGB exports and CMYK exports behave that differently.