RE4LLY

The difference you are noticing here, comes from the fact that when you add adjustment layers to a group together with other layer types, they will only affect objects inside the group, not outside. So in the first screenshot the adjustment layers affect also the base image, but in the second screenshot where they are grouped, they do not affect the base image and therefore change the end result.

To apply layer effects to a text frame or an artistic text you need to hold down CTRL while applying the style as the effect can only be applied to the whole text layer, not to the individual text itself. See the more detailed explanation below:

There is a very simple solution to your problem, namely the Fill Layer (which you can find via Layer -> New Fill Layer). When applying a gradient to a Fill Layer it stays non-destructive, so then you can apply that Fill Layer as a mask to your Gaussian Blur Live Filter Layer and still change it afterwards. You only have to make sure that your gradient is an opacity gradient to be recognized as a mask, not a black and white gradient.

These 2.6.3 beta download buttons should give you the 2.6.4 beta, as stated by Patrick in the thread above.

On the red design, the line is a visible artifact caused by antialiasing where the background color is bleeding between the shapes, even when they are perfectly aligned to each other. It is a know and logged bug. It shows up when using the Vector View Mode and also when using the Pixel View Mode while the shapes are not aligned to the pixel grid. One way of getting rid of the artifact is to turn off antialiasing for the affected shapes in their blend options, this however will affect the final output quality when exported as a raster file. For the teal design it could either be the exact same issue or possibly you can check for thin stokes applied to the white objects that make up the logo. In any case you could see if you can use the boolean operation to add all the individual parts of the logo together as one shape to avoid those gaps to show up.

I personally think it is good that Designer keeps all the Layers in because usually there is a reason why they are there, even when they are empty. They all show up when opening the file in a PDF Viewer as well, so it would be very inconsistent if they don't show up in Designer. Sure you might not want them there but for other people it could be very important to keep them and so this is definitely the better approach.

I had a look at the document and it took AD around 15 minutes to load the file as there are so many empty layers in it. The source PDF file contains over 18800 Layers but only around 3200 Objects, once all the unnecessary empty layers are removed the file loads up very quickly and suddenly is also only 400kB in size. @meridian360 These empty layers are not created by Designer, they are already part of your source PDF, so you should probably check the export settings of your GIS Software to see why it included over 18800 Place Names as Layers even though you are only really exporting about 1670 POIs.

This particular statement is generally true but not completely accurate in all cases, as merging moves top to bottom in the layer stack there is a case in which even the invisible third layer gets merged together with the two other layers but the resulting pixel layer will have its visibility turned off. It happens when the invisible layer is the lowest one of the three in the layer stack. I however would say that it probably is not intentional behavior and could be classified as a bug.

The question has been answered before, so always check before posting a new thread. It was a choice made to lessen the impact on performance, it seems like it is an arbitrary value and no you cannot increase the limit. The limit however does not exist with the node tool, so you can select your objects with that to see all of them highlighted.

That is a know bug AF-1761 when cycling the selection box on a group. In Designer and Publisher you can get around that issue by placing your objects into a Layer instead of a group, however in Photo that is not available.

I can jump in here as I faced the exact same issue as an architecture student/ graduate. Steps you want to take: - Reduce the resolution for your illustrations / renders before bringing them into your portfolio. - limit the amount of pages you have, around 20 A4 pages/ 10 A3 pages is a good length for a portfolio. Anything more is excessive. - Print your PDF, don't export it, it drastically reduces the file size as long as you don't rasterize the whole page. I always get the best and smallest results with the Microsoft Print to PDF Driver so if you are on Windows, use that. Important note for printing the pdf though is that due to a bug (at least on Windows) you need to use Affinity Version 2.4.2 when printing PDF to get sharp and selectable text. In any later version text will always get rasterized and therefore will look bad. Following these steps should definitely get you down under 10MB.

This is a known issue when bringing in png files from Procreate to Affinity, as the file is being wrongly imported as a 32bit image which makes it look less saturated. See the following thread where it's discussed in more detail with some possible workarounds:

My educated guess would be that one of your objects bounding boxes extends outside the black rectangle and as the artboard tool looks at the bounding boxes to determine its size it then ends up larger than the rectangle. Based on only seeing your screenshots my suspicion is that your circle could be the culprit. Is it rotated by any chance so that its bounding box corners extend outside the rectangle? If so you can fix it by making sure that all your objects bounding boxes stay within the rectangle before creating the artboard which you can achieve for example by clipping everything to the rectangle. Also pay attention that your rectangle layer is aligned to the pixel grid, since if it is not it sometimes can also cause issues when creating artboards. And one final note, to adapt the size of the artboard accurately, you can actually type in the desired size in the Transform panel when you have the artboard layer selected which allows for a more precise input.

Yeah you can quickly turn your Zoom 500 Layer into an Artboard. For that select it, then activate the Artboard Tool and then in the context toolbar for the size select "Selection" and then click Insert Artboard. However, for your original issue with the alignment you can also do it without an extra artboard and outside the existing artboard. For that select both your Sultan and the black rectangle layer, then in your top Toolbar click on the Alignment Button to open the alignment menu. There click on the Align Centre Option and then in the Align To dropdown choose "Selection Bounds" instead of "Artboard". That way your Sultan layer will not get centred to the existing artboard but will get centred to the black rectangle. And finally for the issue with your disappearing layer when moving a layer in the bounds of an artboard, you can simply deselect the little Button "Edit All Layers" in the lower left corner of your layer panel. That will stop the layer from becoming a child layer of the artboard.

Unfortunately there is no convenient way of making a copy of an embedded layer unique, as when you make a copy both will just get grouped in the Resource Manager as one (which sometimes is quite useful but often is a nightmare to work with) and the Resource Manager does not offer a way of separating them. The best way I have found is to essentially not make copies but first make the changes to the original embedded layer and then embed the original file again to your document, as in that case Affinity recognizes that they are different to each other and so will not group them together in the Resource Manager. @Old Bruce No, Dennison describes it quite accurately, if you duplicate an embedded file in your document (or try to embed the exact same file twice), those two copies are permanently linked together, so any change you make in one will also occur in the other, so basically they act like a symbol just that there is no way of breaking that link between the two at the moment.