Alex_M

Thanks, @GabrielM I've just uploaded the files. By the way, I think I found where the problem is coming from. This issue happens when I've nested adjustment layers by dropping them in the layer's name instead of the layer's thumbnail. You'll notice this when you open and test the 2 files I sent. I generally like to drop adjustment layers in the layer's name because it's easier to select more than one nested layer. If I drop them in the thumnbnail, I can't easily select more than one nested layer at a time.

Unfortunately, I can't share the document publicly with everyone. I can share it with the developers only for the purpose of fixing the bug.

A strange thing is happening when I move or resize a layer with "Lock Children" turned on. Please see attached the video I recorded. This happens both with beta 1.7.0.258 and the latest official release. layer_flashing.mp4

A strange thing is happening when I move or resize a layer with "Lock Children" turned on. Please see attached the video I recorded. This happens both in the latest official release and the latest beta. layer_flashing.mp4

OMG, this made my day! Thank you!

Why not give the user the ability to chose the compression method and have a warning appear when choosing the new one as being potentially incompatible? Wouldn't that be better? The overwhelming majority of graphics software I've used gives you that ability.

TIFF files can't be read by Topaz Sharpen AI with Beta 1.7.0.250. I get an error - "ImageImport::Wrong input image". I tried with several different images. This doesn't happen with the latest official version of Photo (1.6.5.123).

I really like how the beta of Photo is going. Especially now that we can color code layers/groups and adjust the layer thumbnail size. Awesome stuff! One thing that would complete the layers panel makeover for me is to make the layer/group visibility icon take the full space of the layer bars the same way the thumbnails take up the full space of the layer bars. They don't have to be square. A rectangle would work too and will save some space for the layer names. One of the things I'm struggling the most with Affinity Photo and that I still can't get used to after 2 years of using it daily, is reliably hitting the visibility icon which is TINY. Literally 12x12 pixels (yes, I measured it). I have to really focus my attention in order to do the simple task of hiding/unhiding things as it's not easy to hit the tiny icons. I have nothing against minimizing icons and saving space on the interface. I say go for it. But when we are talking about icons that you click on multiple time a minute, wouldn't it be a good idea to make them a bit easier to use? If this can be addressed it would make Photo THAT much more fantastic and easier to work with in my opinion. What do you guys think? Full size visibility icons or the tiny ones work well for you? BTW, I was unsure where to submit this thread. Please feel free to move it to the appropriate forum section if its place is not here.

Ok, thanks for confirming! I used a very large brush and cloned a very big blob, making several strokes over the same area. So I'm positive it's not the brush hardness. Again, it's perfectly sharp once I enable Force pixel alignment.

Attached are a screenshot of the brush settings and a part of the image where you can do tests on. BTW, doesn't brush hardness control how hard the edges of the brush are, not how sharp the cloned stuff will come out? clone_blurry.afphoto

Sorry for being vague. It happens in Affinity Photo when I clone out stuff in a pixel layer. Please check the attached screenshot.

If I clone stuff with "Force pixel alignment" turned off I get very blurry results. Is this normal? I Just want to know if there's something wrong on my side or if it's supposed to work like that. Thanks in advance!

I've never had problems with other software. Affinity Photo is the only one that sometimes doesn't want to save even on Desktop. I think this issue needs to be fixed as it causes me to lose work. Ok, I'll try next time it happens and report the result.

I usually save on a mapped network drive when this happens. However, when this problem appears, Photo doesn't want to save the file even on my Desktop. BTW, I just got the same error with another document. And again, it wouldn't let me save to desktop.

I've just got this error again after a few months of trouble free saving. Now I lost a lot of time working on an image. Is this going to be fixed in the upcoming version of Photo?