Keith Palmer

When I inquired of Affinity Support I was directed to an aflaunch.exe link, but the link was marked "not available" and so it proved. I gave feedback to that effect but heard no more, hence my feeling of being left to fend for myself. I have looked again at your prompt and see that the link is now active. I wasn't aware of the changed status, but will try it out now. Thank you. I am very grateful to the forum and its contributors, but not that happy with Serif's part in this problem.

We are a month on from the promise of legacy MSI v2 installers and as far as I know they are still not available. Does anyone have a timetable for this? (As a Windows 10 user I can't be alone in feeling left to fend for myself when it comes to launching affinity photo 2 from third party photo library and raw engine programmes. Without this forum's workarounds I would be totally stuck and disillusioned.)

I've discovered that if I use a keyboard shortcut for 'merge visible' it works normally, even if an adjustment layer is the active layer at the time. This seems to work also with 'rasterise and trim' (initiated after a crop and while on an adjustment layer).

Thanks. I'm afraid though this does not work for me on my Windows 10 PC. I have tried it (substituting my user name) in Adobe Bridge and am denied access permission. In DXO Photolab 5 I get a similar message. (I'm aware of the 'write a bat file' thread. This is simply to note that this particular file path does not transfer to AP v2 for everyone.)

Not an issue, thanks.I think I was wrong there - if I show the ruler, the ruler appears for the next image and again when I close and reopen a file; after engaging the move tool with the ruler visible I can drag out a guideline in these scenarios. So that seems OK in V2 after all. Apologies to Serif on ths one.

Sorry my mistake, I didn't change from automatic to basic mode. I agree a grid appears. But when I open a second file in the same session and click show grid, it doesn't show until I repeat the process. I note the discussion about making a preset or macro - thank you, I appreciate all the advice. I'm hoping Serif will fix this though, along with bigger issues that are making Photo V2 unusable in my workflow.

Oh I'm sorry, Photo.

Windows 10 version on a Desktop PC.

Show grid, guides and margins doesn't work for me either in V2. I have grid and axis manager mode set to automatic but it still doesn't work (Windows 10). This is the third bug I've stumbled across in brief use, I can't think how many more there are out there on these forum pages. The inability to launch V2 from my DAM in particular, is crippling. I know there are threads with workarounds for some of these problems, but I'm not IT confident enough to write bat files and don't want to make a preset for basic functions that worked fine in V1. So far, V2 has been a disaster for me. I really hope Serif gets its act together. V1 was so good that I didn't expect this.

Just to confirm that the problem highlighted in this thread exists in Windows 10.

I can't 'merge visible' by right clicking on an adjustment layer either. It is annoying and worse than version 1. I have to hunt for a pixel layer. to execute the option. The merged layer is then put above my pixel layer and below my adjustment layer, not at the top of the stack. Please correct this.

Thanks James, appreciated. I've yet to come to grips with the idea of compound masking, but will work on it!

The power of the hue range mask is very clear from the video. But I'm not clear how the luminosity blend range mask in v2 differs from an ordinary mask with the blend range cog employed in v1. Can you please advise me? Thank you.

Gosh thank you MEB. That was stupid of me. I'm not sure how this got incorrectly set, since I've used the tool extensively in the past, but that does sort my mistake out. I'm grateful.

Please see attached screenshot. The top (merge visible) pixel layer is active and the clone tool is chosen but is not working. Screenshot AP clone problem.tiff

Please can someone advise me? Having watched an official video on cloning from global sources I find that my clone tool no longer samples from "current layer". I believe I have deleted the global source in storage (global source pane); the problem persists despite restarting the programme. "Add Global Source" sometimes appears in bold as an option, clicking once on this greys it out, but does not restore the clone tool's functionality. I'm really not sure what to do to reset the tool (I tried preferences, brush rest, but that doesn't solve the problem). Any advice appreciated.

When I create a new document or open a new photo they are in sRGB (I think IEC61966-2.1). I 'm sure I've not changed the settings. I can attach a screenshot, but as I can no longer reproduce the problem, I'm not sure what would help you, if anything.

I also had another go at 'factory reset' accessed under 'edit' then 'defaults'. (This didn't work when I first tried it, so I attributed my workaround to changing the color format - in the absence of any other insight.)

The images I've been working with are all my own; simple jpegs from a modern EOS Canon camera, nothing special.

Hi Dan. Thank you for your offer of help. Ahead of that, please see my update, which may (for the informed expert) spell out where I've been going wrong. I think I've got the software working normally again, as place works fine (above) and pasting a photo as a layer also seems now not to darken the inserted copy (perhaps they are in the same colour format?). Keith

I can update this message. I have found that if the colour format of the new document' is reset from 8RGB to 16 RGB then the "place" function behaves normally and no longer darkens the inserted image. As a relative newcomer, I don't understand the principles behind my mistake but I seem to have stumbled on a solution.

I am using AP Photo 1.6.5. When I copy and paste a photo (to add it as a layer into another AP project), or paste it into a new blank document using the "place" option, the added item has suddenly, this morning, become very dark relative to the original. I am unclear what has gone wrong, why now (working fine previously) and how to correct it. I have found an option "return to factory default", but clicking it doesn't obviously make anything happen, and a PC reboot has not helped. Can anyone please advise me? Thank you.