Chris B

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.

This result could be that Windows 10 is tone mapping the HDR values to SDR, or it's falling back down the list of chunks in the metadata (the HDR signalling is contained in the cICP chunk, but if the decoder doesn't support the cICP or iCCN chunks it should use sRGB, iCCP, gAMA/cHRM in that order). I wonder if it's the latter, as the bright highlights on the shield don't look sufficiently tone mapped and are still slightly blown out.
Did you screenshot the Windows photo viewer to post it here? That could add another layer of colour management that prevents us from seeing the exact result you're describing. That said, if the PNG imports fine back into Affinity Photo then the HDR pixel values and chunks signalling the transfer function and colour space are in-tact. You might get the intended result if you import the PNG into something like an NLE that supports HDR display mapping (perhaps Davinci Resolve?)

Any updates on this? I see 2.4 just released, but I do not see any mention of any fixes to the OCIO issues. Thanks.

I watched the video very carefully to ascertain the sequence in which you are selecting objects...
5 secs - Donkey Selected | Not inside a Layer (Capital L)
8 secs - Rooster Selected | Not inside a Layer (Capital L)
9 secs - Lamb Selected | Not inside a Layer (Capital L)
11 secs - Honey Pot Selected | Not inside a Layer (Capital L) but inside a Group
14 secs - Frame Text Selected | Not inside a Layer (Capital L)
16 secs - Frame Text Selected | Inside Layer1 (Capital L)
From this point forward because 'Enable All Layers' is disabled you will only be able to select objects on page inside the same Layer (Capital L), Layer1, i.e., the two Curve Layers, the Picture Frame and the Frame Text layers (Small L).
This is why you are unable to select the Rooster, Donkey, Lamb, Honey Pot, Tree and Musical Note on page at this point...

32 secs - Donkey selected in the Layers Panel followed by the Rooster, Lamb and Honeypot | All, Not inside a Layer (Capital L)
38 secs - Music Note Selected | Inside Layer (Capital L) with the FX applied
From this point forward again because 'Enable All Layers' is disabled you will only be able to select objects on page inside the same Layer (Capital L), Layer, i.e., the Curve Layers that make up the musical note...

44 secs - Rooster selected in the Layers Panel (not on page) followed by the Donkey and Lamb | All Not inside a Layer (Capital L) so you can select any object again up until the point you next select an object on page contained inside a Layer (Capital L).

Because you have 'Enable All Layers' disabled which means that you can only make selections from within the selected Layer (Capital L)...
If you want to be able to select all items on the page regardless of whether they are contained within a Layer (Capital L) or not then just turn 'Enable All Layers' back on. The behaviour you're seeing is by design and allows the user to structure and isolate sections of their work so they can deliberately avoid selecting layers they don't want to select when working on complex projects where you may have many layers overlapping other layers...
The second purpose of Layers (Captial L) is that they can be exported to PDF allowing the individual Layers to be switched on and off in the PDF Reader which is helpful when you have e.g., a map with many layers that you may wish to show or hide, roads, train lines, rivers, location names, topography and so on.

@Sparafucile What camera model is this for, please? It sounds like a compression method that we do not support.
Are you able to attach a sample raw?

Hey Pyanepsion,
It sounds similar to this - 
 

@Chris B,

This strange behavior is happening in Publisher 2.4. Just created a new doc for each; seems OK so far in Designer and Photo, but I just updated.
Any ideas?ubP

@Chris B I was in a rush when I replied and didn't add a link to the previous thread on this topic. Here's that thread now and there's a video in it. Not a screen recording since starting one clears the issue. I believe this issue and the non-blinking cursor issue started at the same time during the 2.2 beta.
 

Ohh thats great i will update to new version andtry it oit again. Thank you
 
 

Hi @RobPS85,
Welcome to Affinity Forums
The Fuji X-T20 is already supported. Here's the list of supported cameras. Are you having issues opening its RAW files?

In the “Resources” section, I posted all of the vectorized pictograms that I used to create these visuals in the form of Assets…

Hey ME Brady, 
Welcome to the forums.
I have reproduced what you have described, however, I am also a little unsure if this is by design or not. I'd lean more towards it being an unexpected behaviour. Our crops are non-destructive meaning we can reveal the cropped area. If I do this after following your instructions, the revealed area is now clipped from the canvas - which again, I'd argue is not the desired behaviour from a user point of view, but programmatically, it probably is correct.
I will check with the developers. Thank you. 

As GarryP has said this is By Design because you have the View Tool selected. Dragging an image in won't change your selected Tool, and as Photo's default tool is the View Tool it unfortunately makes it seem as though the image is 'missing'.

As others have mentioned this isn't a beta issue and nor is it considered a bug, as the software is behaving as intended. If you don't like the default tool of Photo then please feel free to post your thoughts in the issue Return has linked to above. 
 

No, I mean 'bumped' - it means that we go ahead and update the bug report to reflect the fact that it is still an issue and we update the affected software version etc. 

Thanks loukash, that's what I figured so I went ahead and logged it.

We believe we know how to fix this but the change is unlikely to make it into the initial release of 2.4, which has reached release candidate stage. We do not think that the fix can be included in 2.4.0 as to do so would mean it would be released without sufficient time to check for any possible regressions it may cause to other camera formats, sorry.
Hopefully we will start another beta soon (2.4.1 or 2.5.0) and this fix will be included.

Didn't know that you can do that. But @Chris B It's all worth nothing till the redraw bug affecting the layers below in the stack for show/hide others commands will be fixed.
It's an open issue from may 2023 (AF-1445). Soon it will be a year past away and still not fixed. This is not acceptable.
Because of the redraw bug those commandsare totally useless for the user. 
https://forum.affinity.serif.com/index.php?/topic/186882-affinity-photo-is-show-others-menu-buggy/
 

Layer menu item "Hide/Show Others" is missing In Publisher, though it is available in Designer and Photo personas.

It's available on a right-click for the visibility icon but as you've pointed out, not in the Layer Menu. I have queried this with the developers - thank you.

We've been investigating this further internally and it's possible you are seeing the '8.3 filename' in this screenshot based on the length of the file path, where you are currently trying to open these PSD files from.
In order to test this, can you please move the .PSD files to a folder in the root of this drive (for example, I:\test folder\file.psd ) and try opening them again, then let me know the behaviour you experience?
It's hard to tell as you've marked out your screenshot, but if the folder path this file is contained in is longer than 260 characters, it may cause this error to appear.

hi @Hangman,
I've tried uploading the files.
Thnks.
DSC03931.zip

I've just grabbed the one from the original bug report and it also has the Tint at -100%
I will look into this.

I've just grabbed the one from the original bug report and it also has the Tint at -100%
I will look into this.

Hi @yomogida,
Are you able to Zip and upload one of the RAW files so we can take a closer look?