Chris B

Thanks ltew, I've asked the developer who assisted me earlier if the older files would help. Just waiting to hear back Are the older exports JPEG or PNG?

Hey Timo, I must have been using the beta when you first posted. Just tried it in retail and got it on the first go. I then tried the beta again and it seems fine

Thanks for checking Greyfox. I cannot reproduce this even on the first go. I initially thought that it may be due to the filter not resetting its settings between documents... @denoving@gmail.com - does this happen with any other filters? Can I also recommend changing your username (you should not really display your email publicly as it may lead to an increase in spam if it gets crawled).

Yes if I hear anything I will update you. There are hopefully some improvements going into the next big update to help us either prevent or diagnose this. Occasionally we see corruption like this but it's so rare and nobody internally has ever been able to reproduce it.

Hey ltew, Thanks for the file. Unfortunately the file is not recoverable. One of the developers has attempted to debug it and we cannot find the corruption. If perhaps you have a slightly older backup of the file, it might help us further. I'm not entirely sure how this has happened either. I tried copy/pasting the layers to a new doc and got different results. See link: https://www.dropbox.com/s/8sv1yj0u2gqaxpr/ltew.afphoto?dl=0

Sorry Timo, I did see the video when you posted it and spent some time trying—you should have to remind me so apologies for that. It looks like the layer has been deselected which hides the path but I can see from the video that isn't happening in this instance. Are you using a mouse or tablet? Not sure if it matters. I can see how annoying this would be so I'm keen to figure it out.

I recorded it on Windows as it's where my recording software is but macOS behaves the exact same way for me. Are you working from a preset or re-opening the HSL dialog from an existing one?

Hey ltew, Thanks for uploading the files. I've just spent a bit of time deleting, exporting and generally poking this file but nothing is jumping out. It is broken on Windows and macOS with and without metal. I can't seen to find any NaN pixels so I'm not sure what has happened. I have escalated this to the development team to see if it can be fixed or at least find out what has happened.

Hey Cwtech, It looks like it may be hitting the macOS Sandbox file limit and then refusing to write any other files. It's normally fonts that are causing it to hit the upper limit. Are you using a font manager?

Thanks for the info Andrew. I don't know if I'm just not quick enough (and I sometimes miss the Home button) but I still can't get it. It's clear you're definitely having an issue here. We do have some reports logged with development regarding similar behaviour. I think the app should simply not let you open another project until the save has completed. On Desktop, if you try to close the document whilst it is saving, you are presented with a warning. I've asked a colleague to check this for me as well.

Hi ronnapier, welcome to the forums. Would you have a file that you could attach that is in this state? Could you also save the file with its history (Save History with Document) from the File menu.

Thanks for the feedback everyone. I think this is perhaps something to watch out for with the Adobe apps.

But you opened both PSD's in the exact same way?

I've broken this recipe down and gone over it countless times. The only time I encounter something odd is when I forget to hit the Apply button on the Perspective Tool. And the software does get internal QA. However, as Walt pointed out, workflow and user error can play an enormous role in the way we find bugs. For example, if you were also forgetting to hit Apply (as I was) and this is causing the bug, that's a prime example of user error (which caught me out following the recipe). We do not expect our customers to beta test the software. We give them a newer build that we often dub as a 'beta' but it's usually more stable and provides some customers a way out if they're stuck with a bug. If you weren't forgetting to hit Apply and you are still seeing glitches or odd behaviour, a file or video can help us. It might also be worth seeing if Metal compute from Preferences > Performance is causing an issue. Thanks for your time.

Hey bulim, They are sticking for me. What version of the app are you using? Also, what scaling are you using? I'm seeing some truncation with the buttons at the top and also the font doesn't fit nicely inside the slider fields. HSL.mp4

It is working absolutely fine for me. If you can retest with the Paint Brush Tool and let me know what happens I'd appreciate it.

We have seen similar issues to this before: Unable to import brushes if Sketch is installed Unable to import brushes if Artstudio is installed Now it seems unable to import PSD if Fresco is installed (potentially). Though this doesn't explain why DM1 cannot do it. I wonder if there's another app causing the conflict. Who is in the 'I get an error attempting to open PSD' camp and who is in the 'It is greyed out' camp?

A few things to check for those of you who haven't already: Develop Assistant (tuxedo icon) - Set this to 16 bit Windows Colour Management - Advanced tab - Set Device Profile to sRGB IEC61966-2.1 Affinity Preferences - Colour - Again, make sure you are using sRGB IEC61966-2.1 for the RGB Colour Profile and sRGB IEC61966-2.1 (Linear) for the 32 bit RGB Profile Make sure you are using the 1.8.4 beta Finally, try the reset. Go to %AppData%\Affinity\Photo and rename 1.0 (Beta) to 1.1 (Beta) and launch the app and load your raw. Ideally, we want to be all testing the same raw if possible so I propose we use the one I've attached to this post which is the one in the bug report and the one development worked with. If this raw works and your own raws do not, we can get around to it. I know some of you have tried the above but I'd like you to reply and confirm. Now you've done this, we should all be in a similar environment. KMS_0107.NEF

I can tell which profiles are being used so don't worry about the language. I think Windows Colour Management is going to be playing a role in this issue.

I'm working with the developer who originally made the fix in the beta. Development do occasionally post on the forums but it's up to the support staff 95% of the time. This is still actively being discussed with the developers.

Hey Cwtech, welcome to the Affinity Forums. I've had a go at reproducing it to no avail so I've asked dev to look at the log you attached. I'll get back once I hear, cheers

Hey ltew, welcome to the Affinity Forums. Sorry to hear this. I've made you a private Dropbox folder so you can send me the file so we can look into this for you. Only QA and Development can see the folder and will be removed once investigated. It might be worth you toggling Metal compute to see if anything changes (Preferences > Performance). Do the glitches move around at different zoom levels?

Hey riveryeti, I've read this post a couple of times now and thought about it and then I recalled you posted about the low CPU usage when loading the images into the batch dialog. I discussed the threadripper with development and suggested we really need to get hold of one and see what seems to be causing you issues. I would be more than happy to try your process with the exact same files if you wanted to supply them? It might help us figure out if the app is having an issue with the files you're using or indeed if it is a threadripper optimization issue.

Hey riveryeti, thanks for the feedback. I have heard other users speak mention similar improvements. I think this post is more suited to feedback, however I will get around to looking at the linked bug you reported Thanks!

Hey hexagon, welcome to the Affinity Forums. Ideally we would need to see your User Interface to see what brush settings you have set. Also, if you can display the Layers Panel so we can see what you're painting on that would be good too. The brush can be very subtle so at a glance you might not initially notice anything but it is working for me on a single pixel layer. Are you painting on the adjustment layer or the pixel layer?