Lem3

Thank you for your reply.  I guess I'll have to find a new workflow. It's a shame that edits made in the Develop Persona don't get saved within the dng file or even in a side car xmp file. I'd rather not make another new file save of the edits, especially when I edit lots of photos at one time.

That may help explain why I disagree with @lepr about a pixel selection being an independent raster object. Image a 10 x 10 px document. If I select for instance 10 of its 100 pixels, I do not believe that action, in & of itself, makes those 10 pixels a new raster object. The selection just defines an area of (or marks off a boundary in, if you prefer) the document, nothing more.

My opinions...
It is true that your external hard drive is not a network drive. But in some sense it is also not local. That term really applies only to the built-in drives. And yes, it's risky to use Affinity to save or open files from it.
It is, though, much less likely for a connection problem to happen in your scenario than over a network.

But if the reflection/glare is in the same location (as @augustya seems to be saying?) couldn't they just clone onto a new pixel layer, and copy that layer to the other images?

As per the Release Notes:
Adjusted mask behaviour
From customer feedback the drop down menu when hitting the mask button in layers panel has been removed, and logic for how the assistant determines if a mask should be added as a new layer or a child altered.

If your tutorial instructed you to use the Inpainting Tool on a new layer, make certain the option in the toolbar is set to Current Layer & Below.

For Windows, there is Users > username > AppData > Roaming > Affinity > Photo > 1.0 > Workspaces > Photo > Shortcuts.xml
I created a new shortcut for Open Folder in Explorer (Ctrl-Shift-Alt-X) and found this stanza was added to that file:
<Item type="Command" command="Serif.Affinity.Commands.OpenFolderInExplorerCommand, Serif.Affinity, Version=1.10.5.1342, Culture=neutral, PublicKeyToken=null" key="X" modifierKeys="Alt, Control, Shift" />
It's left as an exercise for the user to extract that into a more user friendly format.
 

For Windows, there is Users > username > AppData > Roaming > Affinity > Photo > 1.0 > Workspaces > Photo > Shortcuts.xml
I created a new shortcut for Open Folder in Explorer (Ctrl-Shift-Alt-X) and found this stanza was added to that file:
<Item type="Command" command="Serif.Affinity.Commands.OpenFolderInExplorerCommand, Serif.Affinity, Version=1.10.5.1342, Culture=neutral, PublicKeyToken=null" key="X" modifierKeys="Alt, Control, Shift" />
It's left as an exercise for the user to extract that into a more user friendly format.
 

For Windows, there is Users > username > AppData > Roaming > Affinity > Photo > 1.0 > Workspaces > Photo > Shortcuts.xml
I created a new shortcut for Open Folder in Explorer (Ctrl-Shift-Alt-X) and found this stanza was added to that file:
<Item type="Command" command="Serif.Affinity.Commands.OpenFolderInExplorerCommand, Serif.Affinity, Version=1.10.5.1342, Culture=neutral, PublicKeyToken=null" key="X" modifierKeys="Alt, Control, Shift" />
It's left as an exercise for the user to extract that into a more user friendly format.
 

I found a solution to this problem. Set black levels at 1% or white at 99% in the master level and after that the alt key will work in the RGB.

Hi @AlexDres
Welcome to the Affinity Forums
Many thanks for providing a workaround for this and for the bug report - this certainly shouldn't need to be changed first so I will log this with our developers now!

If Preview app says it is a TIFF image it probably is. So when you say you've "got" .jpg as the filetype, how did you get them all to show that? If you just renamed any of them in Finder by adding or changing the filetype extension, that won't work.

I can confirm that using the spacebar for panning while using the freehand selection tool is broken again.
 

Hi @Marcel Korth, both of these features are present in the Affinity apps. Alt-clicking (Windows) or Option-clicking (macOS) on a layer isolates it: https://affinity.help/photo/English.lproj/pages/LayerOperations/isolating.html — the only difference here is that you must click onto a different layer to exit isolation mode.
As regards alt-clicking layers to clip them, Affinity has a concept called child layers. You can click-drag a layer and offer it to another layer, but there are two distinct behaviours here:
Offering your source layer over the target layer's thumbnail makes the source layer act as a mask. Offering your source layer over the target layer's text/label will clip the source layer to the bounds of the target layer. Once a layer is inside another layer, it is referred to as a child layer, and the top layer is referred to as the parent layer. To replicate the example in your video, you would click-drag that image layer onto the text/label of the text layer and release the mouse button.
An alternative way to do this is to use the menu option Arrange>Move Inside. You can also create a shortcut for this—I use Shift+Alt+I—to speed up compositing workflows. You will also find an option in the shortcuts for Insert Inside—I like to shortcut this to Shift+I. Once it is toggled, the next layer created will automatically be placed inside the currently selected layer, so this is really useful for quickly clipping adjustments/live filters inside the current layer.
Hope the above helps!

I would think this should work for any running program:

Start Affinity Photo, then open Task Manager.
Click the ">" next to "Affinity Photo (2)"
Right click on sub-item "Affinity Photo"
Click on either context menu item "Open File Location" or "Properties"

Recoverd file is attached
Saving to NAS or external storage devices is a major factor in file corruption for Affinity files
Always work on a local drive and upload to external drives for backups or long-term storage of the file
Always make backups of the file as you work on it, saving to new file names (e.g. revisions) is highly recommended 
Today you were just lucky, most corrupt files are NOT recoverable
 
"01/11/22 Recovered file no longer needed so I have deleted it, as I need the upload space"
 
 
 

Many thanks for providing this!
It appears you have 'broken' the link between flowing frames from page 3 onwards, hence the 'red eye' icon shown here - 

If you link this to your frame after the TOC, you will find all of your text is still within the document.
We'd also recommend keeping regular backup versions of your files separately from the main file you are working on, just in case you experience any further crashing.
I hope this helps

I'm new to Affinity Photo (not quite so new to editing tools, but I thought I'd start over from scratch with a new application and actually take some time to learn things properly, rather than work it out myself, badly. So I also signed up to a Udemy course, which has yet to teach me much, but soon will I suspect...)

And I thought I'd check out all the other resources available, including this forum. And the SINGLE THING I felt it worth posting about is THIS TOPIC... but I see I'm not the only person to make the observation...
Really disappointing that this has been the case for so long.  My main monitor is a 23" running at 2560 x 1440 - not even 4K - and I really struggle to distinguish the icons in the toolbar.  This really, really needs addressing, it makes using the software PAINFUL

In that case, the message should be “Affinity Publisher 1.10.4 is currently the newest version available via auto update.”

The confusing part from a user standpoint is what 1.10.5 shows (like in my screenshot) when using "Check For Updates." Obviously, 1.10.4 is not newer than 1.10.5. Auto update needs to be fixed if it can't figure that out.

That is because changing the Fill of a Layer layer changes the Fill of the objects it contains. 
It is not only in theory. It is an important concept to understand, and makes a difference in practice. And it explains why it did not work as you expect.

Their OpenCL kernel compiler is much slower than it used to be. I have a sample repo demonstrating the problem here:
https://github.com/MarkIngramUK/ocl-compile-benchmark
Pinching the results from that repo:
AMD Radeon PRO W6800 (OpenCL 2.0 AMD-APP (3354.13)): 143ms
AMD Radeon RX 5700 XT (OpenCL 2.0 AMD-APP (3188.4)): 1400ms
AMD Radeon (TM) R9 390 Series (OpenCL 2.0 AMD-APP (3110.7)): 53ms
The top result is what I've just tried now, with the latest drivers. The middle result is what I originally filed the bug with AMD. The last result is a non RDNA GPU (i.e. unaffected by the slow compilation bug).
Driver 3354.13 appears to be 10X faster than 3188.4, but that's still 3X slower than it was originally.

I understand that, and that's why I stated
Not knowing what the whole scene is, since mulea posted that it was a crop, I wasn't going apply another background. There's other methods that can be used to remove/replace objects.

while I can confirm your observation, I would see this as feature on how filters and adjustment work (always affecting the complete layer)
Just rasterise & trim after cropping, before auto-levelling and you get what you want.
Filter and adjustments consistently affect the layers in total, it would introduce inconsistency if Affinity would change this.
 

I am attaching two recordings.  In the first I follow the Help instructions for Power Duplication:
Duplicate the layer
Activate the Move tool, drag the object away from the underlying arrow.
Duplicate the top layer (should still be selected)
A third layer is created, but the third arrow is in the same place as the second one, no transform is performed.
The second recording starts at the end of the first with three layers but no successful transform for the third.
I drag the third arrow some distance, then duplicate that layer.
A fourth layer is created which reflects the second transform.  Additional layer duplications also work correctly.
Power-dup-fail.mp4 Power-dup-extra-steps.mp4