NotMyFault

Users of Affinity apps would like to get an official statement if Affinity is able to implement a workaround avoiding to trigger a bug, and when this happens. The lack of information from Affinity leads users to the conclusion that Affinity doesn’t care and simply waits for NVIDIA to fix the driver bug. This happened before when latest AMD drivers had a performance issue, Affinity just disabled HW acceleration completely.

Can you upload the afdesign file, and a screenshot of printer settings. please make more tests: export as raster/bitmap format, and print that bitmap file. export as PDF, print PDF from Affinity and from OS (PDF viewing app).

https://affinity.help/designer2/en-US.lproj/pages/ObjectControl/layerStates.html

The function is available, only hidden by default. You must customize the toolbar to make it visible. please search for older topics to avoid creating duplicates.

I see the issue. Carefully review the video, at 0:40 when you try to move the origin point, Affinity mistakes this as selection gesture, as the touch point is in the middle between 2 curves. Consequently, all layers get deselected, this is what seemingly vanish the origin point. I rate this as bug, too, and suffered multiple times. it can only be avoided by zooming in, but this is often impractical when you need to be more zoomed out to be able to see or reach other parts of the objects like bounding box nodes.

We don’t know if the current behavior is by design or not. I would raise a bug report, but more as a question than a fact.

The file is 70k x 9k pixel size. A single bitmap layer in full size would require 640.000.000x5 or 320 Mbyte (uncompressed)

If you edit a file, then deleted all layers, it will still contain lots of data unless you use „save as“. There is no „garbage collection“ when you delete layers. Similar to a file system, deleted blocks are only marked as deleted in metadata, but still contain the old data.

It seems to work like this: Select same works no matter if layer opacity is modified, or parent layer like groups have reduced opacity inherited down to child layers. Select same includes layers with same color and color opacity. Any difference in one or both parameters will exclude.

global colors allow to change no matter if color or layer transparency. Need to check if same applies for tint. Select same color is strange, as you observed won’t match if layer or color transparency is changed.

What exactly do you mean by context change? Switching apps, or doing something specific in Affinity apps?

For the edges, you can use a custom made vector image brush in Designer, or some layer fx.. This allows to use a simple gradient for the fill of the shape.

Please activate „show touches“ in settings. next, include the layer panel in recording (open it when issue happens) the most likely cause is touching the canvas (maybe unintentionally), thus the layer gets deselected.

I‘ve lost all hope long time ago Affinity will ever become a mature product. Number of newly raised bugs outperform number of fixed bugs tenfold - every release cycle.

Or save one 256x256 px grey gradient as png. Then create fill layer or shape as needed, use fill, set to bitmap, allows repeated patterns similar to pattern layer.

A procedural texture filter creates this, can be saves as preset. if interested I will look up the formulas.

See And

I‘m affected with 2 M1 devices and mildly unhappy, too. Switched from Windows to leave some Windows specific bugs behind only to find more (severe) bugs on Mac side.

Thumbnails seem 2nd class citizens, similar to histogram or scope panel. They get updates when Affinity feels ready, or not. In some cases never. Toggling layer visibility sometimes help, but not always.

Yes. In Designer you may use symbols instead. But symbols are a bit tricky and may be unusable as compound shape. In Designer, it is easier to just copy the shape (without linking) and select both copies when using move tool.

Nothing will happen. NathanC already gave and official answer. Affinity will only (try to) fix bugs which are at least reproducible on PC types already in possession of the Affinity team, and affect many users. There are many more CPU/GPU types which don’t harmonize with HW acceleration, and will never get fixed. We have currently multiple long lasting rendering bugs Designer on M1 Mac (zoom level rendering bugs) all M1 based iPads (navigator thumbnail shows artifacts) last gen NVIDIA 59xx (crashes) in some cases Affinity states it is a driver issue, one affected AMD high end GPUs and lasted for more than a year, Affinity even disabled HW acceleration on their side when detecting such GPU.

There are far less relevant in Publisher. Performance options differ between Apps. Normally you will to the heavy lifting in Photo, export as bitmap file, and import in Publisher, sparing Publisher from the GPU relevant workloads. Text are mostly vectors, and scaling bitmap images (without heavy filters) can be done on CPU.

It is in the Layer Menu, one below „duplicate“. my videos show iPad which looks a bit different, but Desktop has the same functions. Please consider using the Online Help. https://affinity.help/photo2/en-US.lproj/pages/LayerOperations/linking.html

The PT filter is quite slow on my PCs.