undo brush acting like clone brush

[Paolucci]

I'm gong through the Affinity Photo Workbook, and familiarizing myself with the History Panel. I'm moving from being a 20 year Photoshop user to Affinity. I opened a PSD file (about 100 layers). I made a paintbrush tool change to a layer. I went to the previous history to set the undo brush source. Then using the undo brush, I tried to undo a part of the new paint. But it acts like a clone brush taking part of another area of the image and painting it there.

I copied the layer I'm trying to work on, and made it a new document from "new from clipboard." Next I modified the image and the undo brush too worked okay. The only difference I know between the two documents is the the first started as a PSD file. I saved it as an affinity file, and tried the brush again, but it did the same clone brush nature. So as of now, if I'm working in what was a previous PSD file, and want to do a history brush modification, there's not much I can do. Maybe you know of a workaround. I'm in Mac, El Capitan, 10.11.6. and downloaded the latest Affinity a few days ago: 1.6.11.  I'll be upgrading to Mojave soon.  Thanks. 

[Callum]

Hi Paolucci,

Welcome to the forums

If possible could you provide a screen recording of this issue?

Thanks

Callum

[Paolucci]

here is the recording:  https://drive.google.com/file/d/1mDb1mZpS7mAgGFtBPrnrR4OFijF2R8j1/view?usp=sharing

the original image is on my website, http://www.johnpaolucci.com/text.html  prep resolve sheet

 

[R C-R]

I am seeing what I think is the same issue. I have tested with several PSD files, like this very simple Folder BG.psd file with only two pixel layers:

[R C-R]

BTW, I am seeing the same behavior in the Affinity Photo 1.7.0.106 beta.

[Rheus]

This happens if you have cropped an image.

The mildly annoying bug is that even if you use history from after the crop, it still remembers the position of the image from before crop. And therefor it undos the wrong part of the image.

A workaround for me is to save as PSD and open again. This fixes it.