Chris B

This is the most balanced take I've seen in this thread - thanks 👍

And indeed, this hasn't been fixed yet. I just checked again.

Very minor one but in the 2.4.2 (2356) beta build, the thumbnails for some of the HDR lessons/samples are rotated:
Circular flame is rotated 90 degrees counterclockwise and Blue Ballerina is upside down

Thank you! I will do some further testing with this information  

To followup on some of my comments yesterday, we are today enshrining our commitment to the Affinity community in 4 pledges made by the Affinity and Canva teams.
You can read about them here.

We do truly believe the coming together of Affinity and Canva is only going to be a good thing for our customers, staff and the development of our apps. We very much hope you will all continue to be with us on this journey.
All the best,
Ash

We are not, we are all very excited about what has been said and the future for Affinity. This thread is about your response not ours. As an employee of 24 years I am personally very pleased about what Ash has announced and the Affinity and Canva pledge.
https://affinity.serif.com/press/newsroom/affinity-and-canva-pledge/

This is the changes post. There are no changes appart from Lessons.
but
 

Chris, so sorry, I missed this response.

I am on the M1 Max Studio, so no. BTW, seeing this issue on 2.4.1 (just released). However, going to the Settings/Performance/Display, and clicking "Use only integrated GPU (requires restart)" seems to fix the issue.

However, I still have a 2019 MacBook Pro. I don't use that nearly as often with Affinity as I do on the M1, so right now don't know if the same issue resides on it.

Hey Frozen Death Knight
I assume Windows Photo Viewer doesn't support the view? The file outputs would normally be intended for something like Final Cut Pro or similar. Even Photoshop displays the HDR PNG washed out.
Have you seen James' video on this?
As for the Export Preview, It doesn't yet support a 32-bit preview. These are lossless outputs so you won't need to be zooming in looking for compression artifacts but I do think we should be showing an accurate 32-bit preview. There is probably already a log of this so I'll do some digging.

I think this might be relevant:
https://support.mozilla.org/en-US/questions/1256160

Apologies for the delayed response here!
I can confirm I've been able to replicate this issue here - it appears to be a Metal rendering bug as I cannot replicate this on macOS with Metal Acceleration disabled. Therefore I'm getting this logged with our development team now.
With the same file/workflow on Windows, ensuring Hardware Acceleration is enabled, the Levels Adjustment is not correctly applying the 0% white level value, so I am logging this with the team also - however the 'corruption' shown on macOS is not present on Windows at any time.
However, as I understand it, the OPs report is using Windows and not macOS, so I'm unsure exactly how the above bug is relevant to their selection issue.
 
@Grimlock, unfortunately I don't fully understand your exact workflow in Affinity currently - even with the file you've provided.
Out of interest, if you navigate to Edit > Settings > Performance and untick Hardware Acceleration, then restart the app as prompted and try creating/feathering your selection once again, does the same issue still occur?
If so, are you able to outline the exact steps you're taking, so that I can reproduce this here and log it with our team?  

Hey @Morten Lerager, you can indeed import FIT files into Affinity Photo and it will open them in a linear 32-bit pixel format. The data and compositing is actually linear, but there are a couple of things to note:
A gamma-corrected view transform is applied (but only to the view, not the actual document pixel values) so that the result on-screen looks consistent with a final export to a gamma-encoded format such as JPEG. Levels and Curves adjustment layers are added by default for basic tone stretching. You can hide or delete these. To go back to a linear format, Photo does offer the ability to save as a 32-bit TIFF. Alternatively, you can use JPEG-XL, OpenEXR or Radiance HDR (not sure if PixInsight supports these).
I'm not sure how inserting Affinity Photo into a PixInsight workflow pre-tone-stretch would be beneficial though—wouldn't you just tone stretch in PixInsight then export to Photo for further editing? It may be worth pointing out that you can achieve all manner of tone stretching methods in Photo, they're just not readily available as easy filters that you can apply. Some of them (e.g. colour preserving tone stretch, similar to Arcsinh) are implemented via macros which you can download.
Hope the above helps!

Welcome to the forums @JWales,
In the Develop persona I'd initially suggest opening the Develop assistant (on the toolbar the robot head icon in V2, the suit icon in V1) in both apps and comparing the settings you have enabled in V1 and V2, particularly take note of the 'Tone Curve' setting as if this is set to 'Take no action' in V2 then this will likely be the reason for the duller initial image, as no tonal correction is being applied to the RAW. If this is set to 'Take no action' set it to 'Apply Tone curve' and then close and re-open the RAW file again for this to take effect.

https://affinity.help/photo2/English.lproj/pages/Raw/raw.html
If it's already being applied, could you possibly provide a copy of the RAW file so we can take a look?

@DanAllen you need to be using a Metal view in order for EDR compositing to work (not to be confused with Metal Compute). Designer defaults to OpenGL, but you can change it by going to the title menu and Settings>Performance. Look under Display and it will be set to OpenGL. Change this to Metal and restart Designer, and you should then find that Enable EDR can be checked.
Here's a screenshot:

Hope that helps!

Hi @Chris B,
No problem, thanks for confirming you've been able to reproduce the issue on macOS and for logging...

Excellent catch @Hangman
I have reproduced this on macOS, though Windows seems fine. I will log this with the developers.
Thank you very much  

I'm unsure if this is already logged...
There have been several reports of lens profiles not being automatically recognised despite being supported and listed but I've noticed that the lens correction data isn't updated when switching between RAW Files in Affinity Photo.
The Lens Correction Profile for the last opened RAW file is used when switching between opened RAW files. If the Lens isn't supported and subsequently the Lens Profile remains unchecked, when switching to other open RAW files with supported profiles the Lens Profile is now checked but shows None...
The only way to force the lens profile to update appears to be to click the dropdown list and then deselect the list without making a new selection.

Lens Profiles.mp4  

I can confirm it is still an issue.

Hi Chris,
It is slightly bothersome that some bugs that were reported during the cycle were not fixed yet. I hope that they get fixed in the first build of 2.5 whenever it starts.

@Chris Bthis issue looks like af-1496.

Platforms: Mac and Windows
Version: Affinity Designer & Affinity Photo 2.4.0
Issue: In Export Persona, Path Components of a Slice are not recognized unless a document is closed and re-opened.
I’ve seen this issue on both Mac and Windows. I first noticed it when testing the new “Document Name” path component in Affinity 2.4.0, but maybe it existed earlier.
To reproduce (using Affinity Designer as an example):
Create a new document Save (ex: MyTest.afdesign) Go to Export Persona On Slices tab, expand “background” slice.  Add “Document Name” and/or “Document Filename” to Path Components:
Notice how it does not appear in the filename:

Close the document. Re-open it and go back to the Export Persona. Expand the slice.  Observe that the parameters are now there:
 
 
 
 
 

Hey @TrentL
Thanks for the excellent bug report. I have reproduced this and logged it with the developers

I have a 1920*1080 external monitor. I just opened Publisher on this monitor and pulled out the adapter to my computer. This is what I got on my mac.

If I've correctly understood your post - I would say that sounds as though you're trying to use the Affinity apps without a valid license, which is against our License Agreement.
Pirating applications is not acceptable, and certainly is not up for discussion here on the Affinity Forums.
If you wish, you can try a free trial of the Affinity V2 apps here, to see if they suit your workflow - https://store.serif.com/get/universal-licence-2/trial/
Alternatively you can purchase a license for Affinity here - https://affinity.serif.com/affinity-pricing/.
We even often run sales throughout the year, if the full price of the application is insurmountable for you currently, so I'd recommend keeping an eye out for these offers.