Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

  • Last visited

Everything posted by Hangman

  1. @Coziosco, could you upload a sample file where in V1 the exported pdf exports without a transparent background but with a transparent background in V2. Also, could you clarify which pdf viewer you are using to view your pdf files, e.g., Preview, Acrobat etc.,
  2. Spot colours in EPS files have never been supported in the Affinity Suite. There have been many feature requests to add spot colour support for EPS files over the years but to date this hasn't been implemented and I don't know if it will be moving forward. The colour shift you are seeing is unfortunately a regression, basically any 4c colour eps file where either the C, M, Y or K value is specified as 100% appears as 50% in V2 when the file is opened and it also affects a second colour in the CMYK group as well, i.e., Y100 results in Y50 and C50 C100 results in C50 and M50 M100 results in M50 and Y50 This has been reported previously but I've been unable to locate the original bug report. Edit: I see @Pauls has already linked to the bug report above. CMYK Representation for EPS files opened in Designer V1 Left | Designer V2 Right
  3. I guess this should appear in the Photo forum but regardless, I totally agree about the lack of correct tab functionality in the context toolbar (this needs to be fixed across all panels and all apps). With regards the crop tool icons... When selecting the crop tool in Photo you will see one of five icons, all have a purpose... A horizontal, vertical or 45° straight double headed arrow - to set the crop size using any of the eight perimeter drag handles A bent double headed arrow - to rotate the canvas A double headed arrow in the form of a cross - to move the current crop area A cross hair (with no arrows) - to click and drag a new crop area A cross hair with a spirit level (when selecting straighten from the context menu) - to straighten the image In Designer there are three crop icons... A horizontal, vertical or 45° straight double headed arrow - to set the crop size using any of the eight perimeter drag handles A double headed arrow in the form of a cross - to move the current crop area A white arrow with a crop symbol attached - to move the object within the crop
  4. @Thomahawk, you definitely need to choose the same colour profile for both Designer, the PDF export and Acrobat otherwise you won’t see consistent results… Using Fogra 39 in your source document but checking using Fogra 27 in Acrobat will result in the issue you’re experiencing. Assuming you also embedded the colour profile in your exported PDF?
  5. @ItIsWhatItIs, this is unfortunately a known Publisher bug that has been reported and will hopefully be fixed soon. I'm assuming you're seeing this in Publisher rather than with Designer Artboards?
  6. @Coziosco, welcome to the forums... You need to add a physical background layer to your artwork, otherwise your exported PDF will have a transparent background. This is the same behvaiour as V1 and when viewed in Acrobat Reader it also has a transparent background. If you turn on 'Show Transparency Grid' in the Acrobat Page Display Preferences (which is off by default) you will see the file has a transparent background.
  7. @euronesia, a couple of observations... firstly, the makeup of the graphic elements in your file use a mix of RGB, HSL and CMYK colour specs as shown below... while this isn't the cause of the issue, all the elements should ideally use an RGB colour space... It looks to me as though there is a bug here with the rendering of shadows that have Gaussian Blur applied to them. According to the Affinity Designer Guide... Allow advanced features When selected, all design features supported by the PDF file format are exported as vectors. If this option is off, depending on the nature of these features, they are rasterised or converted to curves on export. These features include: Artistic text which has been horizontally or vertically stretched. Text which has an applied stroke. Linear and radial gradients. Non-solid transparencies. By Default, when selecting either PDF Digital (high - quality), PDF Digital (small - size) or PDF (for export), Allow Advanced Features is off by Default, so by Affinity's definition this means the Gaussian Blur Shadows are rasterised. When you take a look at the exported PDF files using either of these export options, the 'shadow' layers are indeed, as expected, rasterised, however, when you check Allow Advanced Features for any of these three default PDF export options, you notice that the rasterised shadow elements are nested in their own Group layer, separate from the overlying Gradient Layer as shown below... Allow Advanced Features Off - Left | Allow Advanced Features On - Right So, as a quick test, in the original source Affinity Publisher file, I simply grouped all the Shadow layers to mirror the layer structure shown on the right above, including the Shadow layer on Master A and then exported the file using the default PDF Digital (high - quality), PDF Digital (small - size) and PDF (for export) settings and lo and behold they export correctly. So it looks like a bug relating to how linear and radial gradients are rasterised when Allow Advanced Features is off, which it is by default for these three PDF Export settings...
  8. @SDJ63 and @Thomahawk, this appears to be a PDF Passthrough bug in the Affinity Suite. If you change PDF Passthrough to Interpret for any placed PDF files it should resolve the issue. @Thomahawk does the file you are working on use placed PDF's and if so, is this where you are seeing this specific problem when viewing the colour separations in Acrobat? If so I'd be interested to see whether changing PDF Passthrough to Interpret for any related Placed PDF's works with the file you are working on.
  9. Well, it's in their list of most commonly used Blend Modes along with Normal, Multiply, Screen, Overlay and Colour Burn but I'm not aware of this bug being previously reported so you could be right, it could be that people just happen to like the odd effect it creates but I'm not convinced Divide is used a great deal, I think if it were for serious work, as in, for it's intended purpose we would have seen plenty of bug reports, but then again, who knows... It would be nice to see it fixed in V1 so we have compatibility when files are opened in V2 but I have no idea whether there are plans for any further V1 bug fixes at this stage, one for Serif to clarify I think.
  10. @Entrepreneur, so basically the image of the van is corrupt and this is causing the Affinity Designer file to freeze when exporting to PDF. There are two instances of the van image in your file, so I've replaced both instances with an Affinity Photo file (both layers are now highlighted in green in the Layers Panel) which is Placed in your document so you can still edit it, if required, by selecting the Placed image layer and clicking Edit Document in the Context Toolbar. See if the attached file now works for you when exporting to PDF... ARVONTALAPPU.afdesignVan.afphoto
  11. @Entrepreneur, any file/s you are able to upload would be extremely helpful in trying to track down the cause of the issue, so if you do have time to do that prior to going on vacation that would be perfect... If there are images, then please embed them or provide these as well as part of the upload so we can rule those in or out. I think reinstalling the software will not make any difference and is unlikely to be the cause of the issues you are experiencing.
  12. @Entrepreneur, it would be helpful to have some more information and if possible a sample file where you are experiencing the freeze along with a screen recording demonstrating the crash (if possible) so we can see your set up and PDF Export settings. If the work is of a sensitive nature the Mod team can provide a secure Dropbox link for you to upload any files with issues so they can investigate further... Without being able to see or test the file/s it is impossible to provide any practical help...
  13. This, unfortunately, is a bug in V1, the Divide Blend Mode in the FX panel is showing the incorrect result, the result in V2 is correct, i.e., "lower layers are lightened by luminance on the upper layer, white has no effect and lightness is increased progressively by grey through to black". When the Divide Blend Mode is used in conjunction with an elliptical gradient the correct result is the lower image below... You can test this in V1 (if you like) by applying the Divide Blend Mode to the circles using the Layers Panel in place of the FX panel, again using an elliptical gradient, and you will see the results are as per the lower image... If you also make a like for like comparison between V1 and V2 of all the FX Blend Modes, they are all identical with the exception of Divide which, in V1, gives the upper image. V1 FX Divide Blend Mode Top (Incorrect) | V2 FX Divide Blend Mode Bottom (Correct) It is possible to create a workaround by using the interesting pattern incorrectly created using the FX Divide Blend Mode in V1, exporting it and then using this as a clipping mask, this then 'effectively' means it appears in V2 as per V1 though it no longer uses the FX Blend Mode (see attached)... Perlen Neu.afdesign
  14. Apologies, my bad, yes it is... I was fooled because it happened twice after the initial install prior to a reboot but yes, on 2nd launch after reboot all is good again, phew... thanks.
  15. Perhaps not a bug per se, but just updated to the latest versions of all thee apps and all three, even after a reboot, now have 37 dock bounces prior to launching, way slower than 2.0.3 which was two bounces at most.
  16. Apologies if this has been mentioned already but the link to the release notes in Photo's Software Update panel takes you to the Affinity Website... https://affinity.serif.com/en-gb/ rather than the Forum listing the actual release notes... It's fine for both the Designer and Publisher 2.0.4 updates.
  17. @Callum, the bug relates specifically to grouped lines when using both 'Scale with Object'. and 'Scale Override'.. Steps to Reproduce Create two A4 documents with the units set to mm - Doc 1 - 72 dpi - Doc 2 - 300 dpi On the 72 dpi document draw a series of 2pt lines Create a duplicate set of 2pt lines and group the second set Select both the grouped and ungrouped lines and Copy Ensure 'Scale with Object' is selected in either the 'Stroke Panel' or the 'Scale Override' panel Go to the 300 dpi, A4 document and Paste Result The grouped lines incorrectly maintain their line weight at 2pt, i.e., they don't 'Scale with Object' when pasted to the 300 dpi document, the ungrouped lines do correctly 'Scale with Object' and their line weight is scaled by 316.67% from 2pt to 8.33pt. However, Positionally... This is further complicated by the positioning of grouped and non grouped lines and depends on whether the grouped lines Appear to the left or the right of the non grouped lines on the canvas Appear above or below the non grouped lines in the layers panel When the grouped lines appear below the non grouped lines in the layers panel then the pasted position of the lines in the 300 dpi document is relative to the grouped lines, i.e., the X, Y pixel position of the grouped lines is the same in both the 72 dpi and 300 dpi documents. When the grouped lines appear above the non grouped lines in the layers panel then the pasted position of the lines in the 300 dpi document is relative to the bottom most, non grouped line in the layers panel i.e., the X, Y pixel position of the bottom most non grouped lines is the same in both the 72 dpi and 300 dpi documents. This results in one of four different pasted positions when the combined grouped and non grouped lines are pasted between documents. Note: This is the same behaviour in V1. Line Weight and Position.mp4
  18. @JTM, welcome to the forums... possibly a silly question but what specifically isn't working, i.e., I'm assuming you are clicking the green 'Make window full screen' button to the left of the AD icon to enter full screen mode... Once you are in fullscreen mode what happens when you move your mouse to the top of the screen, does the Affinity Menu appear along with the red, orange and green buttons allowing to to click the green button again to escape full screen mode or does nothing happen at all. Have you tried the keyboard shortcut, Command + Control + F (on Big Sur and earlier) or Fn + F on Monterey or later.
  19. @Callum, I don't want to cross contaminate posts but the issue experienced by @Hanjo sounds very much related to this issue recently reported, though possibly not identical. There is also a report in the Photo forum of another issue relating to Transform Origin which could also be related...
  20. That is a very valid point, in which case my previous assumption is clearly wrong and I agree this is indeed a bug that needs fixing...
  21. I'm not sure of the full extent of what you are creating so may be talking out of turn, but would the approach @N.P.M. suggested, i.e., using a clipping path rather than a mask not provide the solution?
  22. Agreed, it would be good to get clarification... but my take is that Selection Only refers to the bounding box of the parent element, i.e., the selected layer in the layers panel. That is both logical and results in the outcomes we are seeing in both cases based on the physical selection made.
  23. I'm sure I will likely be castigated for this but I'm not convinced this is a bug for the following reasons... When you group the two images, as shown in the original post and then apply a mask to the group, which in the example shown is smaller and contained within the bounding box of the two grouped images, by selecting the Group in the layers panel, exporting and then choosing Selection Only your physical selection is still effectively the two images and not the mask you just so happened to have applied, so to me what is exported is correct, it is your physical selection, i.e., in this example, the two images. If the mask happened to be the same size as the two images or smaller than currently shown, then Selection Only exports exactly the same size image only it shows either more or less of the two images because the mask is now either larger or smaller. When you do the reverse and you clip the two grouped images inside the square and you select the Square in the layers panel, export and choose Selection Only, your physical selection in the layers panel is no longer the two grouped images, it is now the square, hence it again correctly exports the physical selection, i.e., in this example, the square. I think what is perhaps confusing here is that when using the mask option and selecting the group in the layers panel, the physical selection's bounding box is shown on the canvas as that of the mask rather than that of the actual physical selection which in this example is infact the two images.
  24. Not quite sure what is the expected behaviour re this but while we can select from 8-bit, 16-bit or percentage when working with RGB colour and between 8-bit and percentage when working with CMYK colour, reflecting the Document Setup options for both, selecting 16-bit as the default when working in RGB, this, as expected displays 16-bit RGB values in both the colour palette and colour chooser sliders. Switch to CMYK in the colour palette and CMYK colour values are now also displayed using 16-bit values in both the colour palette and the colour chooser sliders, should they be? Change back to 8-bit from the drop-down menu in the colour palette and the CMYK values in the colour palette are now correctly displayed in 8-bit but still show as 16-bit values in the colour chooser sliders and it appears impossible to change these back to 8-bit in the colour chooser even if changing to RGB 8-bit or percentage from the colour palette drop-down, the values are now stuck in 16-bit. Same issue across all three apps....
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.