![]() ![]() so i got that going for me, which is nice. the msi version seems to be quite a bit faster than the msix version and the scores in the affinity photo benchmark are also higher. msi version and wiping the appdata of the msix version of the affinity suite and while I still have issues with the print upload with this particular printer (I am in contact with their technical support to nail down the issue, will report back) I noticed a jump in performance. So I decided to try installing the regular. it exported fine before and i didnt touch that line of text and apparently working on other areas on the document triggered something that breaks it. ![]() until, like i said, i resize the stroke, and then it exports fine, at least visually. I tried all export profiles and export settings, only fully rasterized works, any vector based output is borked. before "refreshing" the stroke, the issue would be on All exported PDFs unless its a fully rasterized one. once fixed, i cannot replicate it anymore. which clearly hints towards a bug or application issue. I didnt do anything except resizing the stroke a few times and it came back in the export. everything is affinity created vectors and the line of text that errored out last time was a simple white text with a 0.3pt 100k stroke applied with the last letter not getting its stroke on export all of a sudden. In those documents that i run into issues i dont use any raster layers nor vector incompatible content, all same color space and color profile. I only strictly work in one single cmyk color profile (eci300%, because its required for the printers). ![]() I never place vector graphics in the document because this always causes issues, i always convert it to affinity file format and copy the Layers/elements into the target document so they are a "native" element in the document. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |